From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Badness in pci_find_subsys
Date: Sun, 22 Feb 2004 18:46:14 +0100 [thread overview]
Message-ID: <200402221846.15010.robin.rosenberg.lists@dewire.com> (raw)
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
Feb 22 18:23:25 h6n2fls33o811 kernel: [<c01c5897>] pci_find_subsys+0xd7/0xe0
Feb 22 18:23:25 h6n2fls33o811 kernel: [pci_find_device+24/32] pci_find_device+0x18/0x20
Feb 22 18:23:25 h6n2fls33o811 kernel: [<c01c58b8>] pci_find_device+0x18/0x20
Feb 22 18:23:25 h6n2fls33o811 kernel: [pci_find_slot+26/96] pci_find_slot+0x1a/0x60
Feb 22 18:23:25 h6n2fls33o811 kernel: [<c01c56fa>] pci_find_slot+0x1a/0x60
Feb 22 18:23:25 h6n2fls33o811 kernel: [__crc___lock_sock+2862576/4902775] 0xe1301876
:
:
Feb 22 18:23:25 h6n2fls33o811 kernel: [__crc___lock_sock+2854065/4902775] 0xe12ff737
Feb 22 18:23:25 h6n2fls33o811 kernel: [<e12ff737>] 0xe12ff737
Feb 22 18:23:25 h6n2fls33o811 kernel: [tasklet_action+57/112] tasklet_action+0x39/0x70
Feb 22 18:23:25 h6n2fls33o811 kernel: [<c0126559>] tasklet_action+0x39/0x70
Feb 22 18:23:25 h6n2fls33o811 kernel: [do_softirq+97/192] do_softirq+0x61/0xc0
Feb 22 18:23:25 h6n2fls33o811 kernel: [<c0126321>] do_softirq+0x61/0xc0
Feb 22 18:23:25 h6n2fls33o811 kernel: [do_IRQ+229/256] do_IRQ+0xe5/0x100
Feb 22 18:23:25 h6n2fls33o811 kernel: [<c010d855>] do_IRQ+0xe5/0x100
Feb 22 18:23:25 h6n2fls33o811 kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20
Feb 22 18:23:25 h6n2fls33o811 kernel: [<c010bf38>] common_interrupt+0x18/0x20
The stack dump comes out twice with the same time stamp (same in dmesg so I assume the
error occurs twice).
My hardware is a Dell Dimension XPS T700 and lspci
-[00]-+-00.0 Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
+-01.0-[01]----00.0 nVidia Corporation NV10 [GeForce 256 SDR]
+-07.0 Intel Corp. 82371AB/EB/MB PIIX4 ISA
+-07.1 Intel Corp. 82371AB/EB/MB PIIX4 IDE
+-07.2 Intel Corp. 82371AB/EB/MB PIIX4 USB
+-07.3 Intel Corp. 82371AB/EB/MB PIIX4 ACPI
+-0d.0 3Com Corporation 3c905C-TX/TX-M [Tornado]
+-0e.0 Brooktree Corporation Bt878 Video Capture
+-0e.1 Brooktree Corporation Bt878 Audio Capture
+-0f.0 Artop Electronic Corp AEC6712D SCSI
+-10.0 Creative Labs SB Live! EMU10k1
\-10.1 Creative Labs SB Live! MIDI/Game Port
More info @ http://qa.mandrakesoft.com/show_bug.cgi?id=6856
-- robin
next reply other threads:[~2004-02-22 17:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-22 17:46 Robin Rosenberg [this message]
2004-02-22 17:52 ` Badness in pci_find_subsys Prakash K. Cheemplavam
-- strict thread matches above, loose matches on Subject: below --
2004-02-23 4:43 vishwas manral
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-23 16:51 Tobias Oed
2004-02-23 21:09 ` Greg KH
2004-02-23 23:12 Tobias Oed
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=200402221846.15010.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--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