archive mirror
 help / color / mirror / Atom feed
To: Douglas J Hunley <>
Subject: Re: 2.6.0: Badness in pci_find_subsys!!
Date: Thu, 24 Jul 2003 23:45:29 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: Your message of "Thu, 24 Jul 2003 13:26:01 EDT." <>

[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]

On Thu, 24 Jul 2003 13:26:01 EDT, Douglas J Hunley <>  said:

> Just had my athlon box lock-up solid. needed SysRq to reboot the thing.. 
> kernel info follows:
> Jul 24 13:08:23 doug kernel: Badness in pci_find_subsys at 
> drivers/pci/search.c:132
> Jul 24 13:08:23 doug kernel: Call Trace:
> Jul 24 13:08:23 doug kernel:  [<c02064a1>] pci_find_subsys+0x111/0x120
> Jul 24 13:08:23 doug kernel:  [<c02064df>] pci_find_device+0x2f/0x40
> Jul 24 13:08:23 doug kernel:  [<c0206368>] pci_find_slot+0x28/0x50
> Jul 24 13:08:23 doug kernel:  [<f8a2ada4>] os_pci_init_handle+0x3a/0x67 

The 'badness in pci_find_subsys' may not be related to your hang. 

The NVidia msgs are basically caused by the fact that pci_find_slot() is
getting called in an interrupt, so we trigger the WARN_ON in pci_find_subsys().
The worry here is that we may be walking the PCI list on the interrupt side
while something else is hotplugging a new device into existence, causing it to
walk off the end of a inconsistent list.  Unless you actually crapped out right
at 13:08:23, it's probably unrelated.

(I was getting the same NVidia traceback on a regular basis (3-4 at every start
of the X server, and 1 at X server shutdown) under 2.5.72-mm3, they stopped
when I went to 2.5.73-mm1.  If you're still seeing them in 2.6.0-test1, I would
suspect something different in the -mm series is fixing them for me - first place
to look is what got added between 72-mm3 and 73-mm1.

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  parent reply	other threads:[~2003-07-25  3:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 17:26 2.6.0: Badness in pci_find_subsys!! Douglas J Hunley
2003-07-24 17:35 ` Greg KH
2003-07-24 17:47   ` Douglas J Hunley
2003-07-24 23:10     ` Kurt Wall
2003-07-25  2:06       ` Douglas J Hunley
2003-07-25  3:45 ` Valdis.Kletnieks [this message]
2003-07-25 15:15   ` Douglas J Hunley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).