linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kurt Wall <kwall@kurtwerks.com>
To: Douglas J Hunley <doug@hunley.homeip.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0: Badness in pci_find_subsys!!
Date: Thu, 24 Jul 2003 19:10:08 -0400	[thread overview]
Message-ID: <20030724231008.GB28205@kurtwerks.com> (raw)
In-Reply-To: <200307241347.08124.doug@hunley.homeip.net>

Quoth Douglas J Hunley:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Greg KH shocked and awed us all by speaking:
> > On Thu, Jul 24, 2003 at 01:26:01PM -0400, Douglas J Hunley wrote:
> > > 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
> > > [nvidia]
> >
> > You are using the nvidia driver.  Go complain to them as we can do
> > nothing about their code, sorry.
> 
> sure. I didn't know for sure that the fault was nvidia's.

Do you get the same lock up *sans* the nvidia binary-only module?

Kurt
-- 
I am so optimistic about beef prices that I've just leased a pot roast
with an option to buy.

  reply	other threads:[~2003-07-24 22:55 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 [this message]
2003-07-25  2:06       ` Douglas J Hunley
2003-07-25  3:45 ` Valdis.Kletnieks
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20030724231008.GB28205@kurtwerks.com \
    --to=kwall@kurtwerks.com \
    --cc=doug@hunley.homeip.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).