From: Bjoern Schmidt <lucky21@uni-paderborn.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Badness in pci_find_subsys at drivers/pci/search.c:167
Date: Sat, 06 Mar 2004 09:23:27 +0100 [thread overview]
Message-ID: <40498A7F.5070306@uni-paderborn.de> (raw)
Is there a possibility to find out which device caused this error?
It's the first time that it has been arisen...
The kernels version is v2.6.3, do you need more "input"?
Mar 6 08:58:21 gigabyte kernel: Badness in pci_find_subsys at
drivers/pci/search.c:167
Mar 6 08:58:21 gigabyte kernel: Call Trace:
Mar 6 08:58:21 gigabyte kernel: [<c02385c9>] pci_find_subsys+0xf9/0x110
Mar 6 08:58:21 gigabyte kernel: [<c0238611>] pci_find_device+0x31/0x40
Mar 6 08:58:21 gigabyte kernel: [<c02383e9>] pci_find_slot+0x29/0x50
Mar 6 08:58:21 gigabyte kernel: [<c046220d>] os_pci_init_handle+0x39/0x68
Mar 6 08:58:21 gigabyte kernel: [<c02f6f5f>] _nv001243rm+0x1f/0x24
Mar 6 08:58:21 gigabyte kernel: [<c043d815>] _nv000816rm+0x2f5/0x384
Mar 6 08:58:21 gigabyte kernel: [<c03a602c>] _nv003801rm+0xd8/0x100
Mar 6 08:58:21 gigabyte kernel: [<c043d34f>] _nv000809rm+0x2f/0x34
Mar 6 08:58:21 gigabyte kernel: [<c03a6e50>] _nv003816rm+0xf0/0x104
Mar 6 08:58:21 gigabyte kernel: [<c03a570e>] _nv003795rm+0x6ea/0xaec
Mar 6 08:58:21 gigabyte kernel: [<c030f967>] _nv004046rm+0x3a3/0x3b0
Mar 6 08:58:21 gigabyte kernel: [<c04112a7>] _nv001476rm+0x277/0x45c
Mar 6 08:58:21 gigabyte kernel: [<c02f9a9a>] _nv000896rm+0x4a/0x64
Mar 6 08:58:21 gigabyte kernel: [<c02fb2b4>] rm_isr_bh+0xc/0x10
Mar 6 08:58:21 gigabyte kernel: [<c04601bd>] nv_kern_isr_bh+0xf/0x13
Mar 6 08:58:21 gigabyte kernel: [<c01245e6>] tasklet_action+0x46/0x70
Mar 6 08:58:21 gigabyte kernel: [<c01243f5>] do_softirq+0x95/0xa0
Mar 6 08:58:21 gigabyte kernel: [<c010bb0b>] do_IRQ+0xfb/0x130
Mar 6 08:58:21 gigabyte kernel: [<c0109de0>] common_interrupt+0x18/0x20
Mar 6 08:58:21 gigabyte kernel: [<c011428a>] speedstep_set_state+0xfa/0x160
Mar 6 08:58:21 gigabyte kernel: [<c0114514>] speedstep_target+0x54/0x60
Mar 6 08:58:21 gigabyte kernel: [<c04979a2>] __cpufreq_driver_target+0x22/0x30
Mar 6 08:58:21 gigabyte kernel: [<c0498418>] cpufreq_governor_performance+0x38/0x40
Mar 6 08:58:21 gigabyte kernel: [<c0497a92>] __cpufreq_governor+0x62/0x120
Mar 6 08:58:21 gigabyte kernel: [<c0497e73>] __cpufreq_set_policy+0x113/0x180
Mar 6 08:58:21 gigabyte kernel: [<c0497f2b>] cpufreq_set_policy+0x4b/0x90
Mar 6 08:58:21 gigabyte kernel: [<c0497234>] store_scaling_governor+0xa4/0xc0
Mar 6 08:58:21 gigabyte kernel: [<c04973fd>] store+0x5d/0x70
Mar 6 08:58:21 gigabyte kernel: [<c018b45b>] flush_write_buffer+0x3b/0x50
Mar 6 08:58:21 gigabyte kernel: [<c018b4d0>] sysfs_write_file+0x60/0x70
Mar 6 08:58:21 gigabyte kernel: [<c0153c98>] vfs_write+0xb8/0x130
Mar 6 08:58:21 gigabyte kernel: [<c0153dc2>] sys_write+0x42/0x70
Mar 6 08:58:21 gigabyte kernel: [<c01093fb>] syscall_call+0x7/0xb
Mar 6 08:58:21 gigabyte kernel:
Mar 6 08:58:21 gigabyte kernel: Badness in pci_find_subsys at
drivers/pci/search.c:167
Mar 6 08:58:21 gigabyte kernel: Call Trace:
Mar 6 08:58:21 gigabyte kernel: [<c02385c9>] pci_find_subsys+0xf9/0x110
Mar 6 08:58:21 gigabyte kernel: [<c0238611>] pci_find_device+0x31/0x40
Mar 6 08:58:21 gigabyte kernel: [<c02383e9>] pci_find_slot+0x29/0x50
Mar 6 08:58:21 gigabyte kernel: [<c046220d>] os_pci_init_handle+0x39/0x68
Mar 6 08:58:21 gigabyte kernel: [<c02f6f5f>] _nv001243rm+0x1f/0x24
Mar 6 08:58:21 gigabyte kernel: [<c03a815d>] _nv003797rm+0xa9/0x128
Mar 6 08:58:21 gigabyte kernel: [<c0414ba1>] _nv001490rm+0x55/0xe4
Mar 6 08:58:21 gigabyte kernel: [<c043d854>] _nv000816rm+0x334/0x384
Mar 6 08:58:21 gigabyte kernel: [<c03a602c>] _nv003801rm+0xd8/0x100
Mar 6 08:58:21 gigabyte kernel: [<c043d34f>] _nv000809rm+0x2f/0x34
Mar 6 08:58:21 gigabyte kernel: [<c03a6e50>] _nv003816rm+0xf0/0x104
Mar 6 08:58:21 gigabyte kernel: [<c03a570e>] _nv003795rm+0x6ea/0xaec
Mar 6 08:58:21 gigabyte kernel: [<c030f967>] _nv004046rm+0x3a3/0x3b0
Mar 6 08:58:21 gigabyte kernel: [<c04112a7>] _nv001476rm+0x277/0x45c
Mar 6 08:58:21 gigabyte kernel: [<c02f9a9a>] _nv000896rm+0x4a/0x64
Mar 6 08:58:21 gigabyte kernel: [<c02fb2b4>] rm_isr_bh+0xc/0x10
Mar 6 08:58:21 gigabyte kernel: [<c04601bd>] nv_kern_isr_bh+0xf/0x13
Mar 6 08:58:21 gigabyte kernel: [<c01245e6>] tasklet_action+0x46/0x70
Mar 6 08:58:21 gigabyte kernel: [<c01243f5>] do_softirq+0x95/0xa0
Mar 6 08:58:21 gigabyte kernel: [<c010bb0b>] do_IRQ+0xfb/0x130
Mar 6 08:58:21 gigabyte kernel: [<c0109de0>] common_interrupt+0x18/0x20
Mar 6 08:58:21 gigabyte kernel: [<c011428a>] speedstep_set_state+0xfa/0x160
Mar 6 08:58:21 gigabyte kernel: [<c0114514>] speedstep_target+0x54/0x60
Mar 6 08:58:21 gigabyte kernel: [<c04979a2>] __cpufreq_driver_target+0x22/0x30
Mar 6 08:58:21 gigabyte kernel: [<c0498418>] cpufreq_governor_performance+0x38/0x40
Mar 6 08:58:21 gigabyte kernel: [<c0497a92>] __cpufreq_governor+0x62/0x120
Mar 6 08:58:21 gigabyte kernel: [<c0497e73>] __cpufreq_set_policy+0x113/0x180
Mar 6 08:58:21 gigabyte kernel: [<c0497f2b>] cpufreq_set_policy+0x4b/0x90
Mar 6 08:58:21 gigabyte kernel: [<c0497234>] store_scaling_governor+0xa4/0xc0
Mar 6 08:58:21 gigabyte kernel: [<c04973fd>] store+0x5d/0x70
Mar 6 08:58:21 gigabyte kernel: [<c018b45b>] flush_write_buffer+0x3b/0x50
Mar 6 08:58:21 gigabyte kernel: [<c018b4d0>] sysfs_write_file+0x60/0x70
Mar 6 08:58:21 gigabyte kernel: [<c0153c98>] vfs_write+0xb8/0x130
Mar 6 08:58:21 gigabyte kernel: [<c0153dc2>] sys_write+0x42/0x70
Mar 6 08:58:21 gigabyte kernel: [<c01093fb>] syscall_call+0x7/0xb
--
Greetings
Bjoern Schmidt
next reply other threads:[~2004-03-06 8:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-06 8:23 Bjoern Schmidt [this message]
2004-03-06 8:32 ` Badness in pci_find_subsys at drivers/pci/search.c:167 Roland Dreier
2004-03-06 8:52 ` Bjoern Schmidt
2004-03-06 14:47 ` Alistair John Strachan
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=40498A7F.5070306@uni-paderborn.de \
--to=lucky21@uni-paderborn.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.