mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Bjoern Schmidt <lucky21@uni-paderborn.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Badness in pci_find_subsys at drivers/pci/search.c:167
Date: Sat, 6 Mar 2004 14:47:52 +0000	[thread overview]
Message-ID: <200403061447.53012.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <4049913E.8090600@uni-paderborn.de>

On Saturday 06 March 2004 08:52, you wrote:
> Roland Dreier schrieb:
> >     Bjoern> Is there a possibility to find out which device caused
> >     Bjoern> this error?  It's the first time that it has been
> >     Bjoern> arisen...  The kernels version is v2.6.3, do you need more
> >     Bjoern> "input"?
> >
> > This is caused by the closed source nvidia driver.  Only nvidia can
> > debug this problem.
> >
> >  - Roland
>
> Thank you for your answer. Is that a known bug? If not then i'll
> send a bug report to nvidia.

Generally, it's a good idea to search the LKML archives (via 
marc.theaimsgroup.com or google group search) for your problem before 
posting, to see if it has already been reported.

For future reference, oopsen containing the _nvXX symbols are NVIDIA driver 
specific problems and should not be reported to this list.

This problem is well known and is trivially fixed, I am confident NVIDIA are 
already aware of it and it will be repaired in the next revision of the 
driver.

-- 
Cheers,
Alistair.

personal:   alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student:    CS/AI Undergraduate
contact:    7/10 Darroch Court,
            University of Edinburgh.

      reply	other threads:[~2004-03-06 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-06  8:23 Bjoern Schmidt
2004-03-06  8:32 ` Roland Dreier
2004-03-06  8:52   ` Bjoern Schmidt
2004-03-06 14:47     ` Alistair John Strachan [this message]

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=200403061447.53012.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucky21@uni-paderborn.de \
    /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

all inboxes | Powered by JetHome®