From: Martin <marogge@onlinehome.de>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: vishwas.manral@lycos.com,
"Prakash K. Cheemplavam" <PrakashKC@gmx.de>,
"Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Badness in pci_find_subsys
Date: Mon, 23 Feb 2004 08:30:44 +0100 [thread overview]
Message-ID: <200402230830.45003.marogge@onlinehome.de> (raw)
In-Reply-To: <200402230639.00737.robin.rosenberg.lists@dewire.com>
On Monday 23 February 2004 06:39, Robin Rosenberg wrote:
> > I was checking the pci documentation and it said under the heading
> > Obsolete function pci_find_subsys() - Superseded by pci_get_subsys() as
> > the former is not Hot plug safe. Could this be related to the problem
>
> You WHAT? Read the documentation! :-) I thought the ones calling the
> function should do that.
Reading the documentation (ie. source code) it appears the problem is
triggered by the line
WARN_ON(in_interrupt());
Looks like the driver calls pci_find_subsys() from inside an interrupt on
occasions which apparently it shouldn't. The problem seems to be on
nvidia's side, not kernel development. I have emailed nvidia about it some
time ago, so far no reaction...
I got the problem with nvidia modules 4496, 5328, 5336 and with kernels
2.6.0, 2.6.1, 2.6.2, never with 2.4.X. I have stopped using the nvidia
kernel module for now.
> I found some options to try out, but no conclusive info, at the nvidia
> linux discussion forum.
Is this www.nvnews.net you are talking about? I can't find any proper
contacts on the nvidia web site. I'll go over and add a comment right
now. ;-)
cu Martin
next prev parent reply other threads:[~2004-02-23 7:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 4:44 vishwas manral
2004-02-23 5:39 ` Robin Rosenberg
2004-02-23 7:30 ` Martin [this message]
2004-02-23 8:30 ` Robin Rosenberg
2004-02-23 21:08 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2004-02-23 23:12 Tobias Oed
2004-02-23 16:51 Tobias Oed
2004-02-23 21:09 ` Greg KH
2004-02-23 4:43 vishwas manral
2004-02-22 17:46 Robin Rosenberg
2004-02-22 17:52 ` Prakash K. Cheemplavam
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=200402230830.45003.marogge@onlinehome.de \
--to=marogge@onlinehome.de \
--cc=PrakashKC@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.com \
--cc=vishwas.manral@lycos.com \
/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®