From: "vishwas manral" <vishwas.manral@lycos.com>
To: "Robin Rosenberg" <robin.rosenberg.lists@dewire.com>,
"Prakash K. Cheemplavam" <PrakashKC@gmx.de>
Cc: "Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Badness in pci_find_subsys
Date: Mon, 23 Feb 2004 09:43:30 +0500 [thread overview]
Message-ID: <GEEGLONMDDKOLIAA@mailcity.com> (raw)
Hi Robin/Prakash,
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?
Thanks,
Vishwas
--------- Original Message ---------
DATE: Sun, 22 Feb 2004 18:52:11
From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
>Robin Rosenberg wrote:
>> There is a regular error (2.6.1,2.6.2) that locks up my X although I don't know if it has anything to
>> do with X per se other than that after every lockup i find an error in syslog.
>>
>> Feb 22 18:23:25 h6n2fls33o811 kernel: Badness in pci_find_subsys at drivers/pci/search.c:167
>> Feb 22 18:23:25 h6n2fls33o811 kernel: Call Trace:
>> Feb 22 18:23:25 h6n2fls33o811 kernel: [pci_find_subsys+215/224] pci_find_subsys+0xd7/0xe0
>>
>[snip]
>
>It is Nvidia binary driver doing some crap.
>
>Prakash
>
____________________________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
next reply other threads:[~2004-02-23 4:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 4:43 vishwas manral [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-23 23:12 Badness in pci_find_subsys Tobias Oed
2004-02-23 16:51 Tobias Oed
2004-02-23 21:09 ` Greg KH
2004-02-23 4:44 vishwas manral
2004-02-23 5:39 ` Robin Rosenberg
2004-02-23 7:30 ` Martin
2004-02-23 8:30 ` Robin Rosenberg
2004-02-23 21:08 ` Greg KH
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=GEEGLONMDDKOLIAA@mailcity.com \
--to=vishwas.manral@lycos.com \
--cc=PrakashKC@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.rosenberg.lists@dewire.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