From: Chuck Ebbert <cebbert@redhat.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Help! How do I debug oopsing kernel workqueue threads?
Date: Tue, 13 Feb 2007 19:37:23 -0500 [thread overview]
Message-ID: <45D259C3.6070109@redhat.com> (raw)
How the hell do I tell what kernel subsystem queued
a bogus work item?
BUG: unable to handle kernel paging request at virtual address 00002074
printing eip:
c04f3b55
*pde = 71bb1067
Oops: 0000 [#1]
SMP
last sysfs file: /class/scsi_host/host2/proc_name
Modules linked in: hwmon i2c_isa eeprom sunrpc ipv6 ip_nat_sip ip_nat_pptp
ip_nat_ftp ip_conntrack_sip ip_conntrack_pptp ip_conntrack_ftp xt_helper ipt_LOG
xt_state xt_tcpudp iptable_mangle iptable_nat ip_nat ip_conntrack nfnetlink
iptable_filter ip_tables x_tables dm_mirror dm_multipath dm_mod video sbs i2c_ec
button battery asus_acpi ac lp snd_hda_intel snd_hda_codec snd_seq_dummy
snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss
sg snd_pcm snd_timer ide_cd floppy snd serio_raw cdrom sky2 ohci1394 ieee1394
soundcore pcspkr iTCO_wdt skge i2c_i801 snd_page_alloc i2c_core parport_pc
parport ata_piix libata aacraid sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd
uhci_hcd
CPU: 0
EIP: 0060:[<c04f3b55>] Not tainted VLI
EFLAGS: 00010046 (2.6.19-1.2895.fc6 #1)
EIP is at list_del+0x2d/0x6c
eax: 00002070 ebx: f76f0f80 ecx: 00000001 edx: 00000000
esi: f7ff8dc0 edi: d6ca8000 ebp: f7e6f380 esp: f7fefef0
ds: 007b es: 007b ss: 0068
Process events/0 (pid: 8, ti=f7fef000 task=f7e205d0 task.ti=f7fef000)
Stack: f7e205d0 d7ade040 f7ff8d40 f76f0f80 c04717fc f703e0c0 c07a2fc8 f703e0c0
00000001 00000000 f7ff8e60 f7ff8e60 00000001 f7ff8e40 00000000 c04718ff
00000000 00000000 f7e6f380 f7ff8de4 f7ff8dc0 f7e6f380 f7e0bac0 00000282
Call Trace:
[<c04717fc>] free_block+0x77/0xf0
[<c04718ff>] drain_array+0x8a/0xb5
[<c0472e9c>] cache_reap+0x53/0x117
[<c04368c7>] run_workqueue+0x97/0xdd
[<c0437284>] worker_thread+0xd9/0x10d
[<c0439810>] kthread+0xc0/0xec
[<c0404c03>] kernel_thread_helper+0x7/0x10
next reply other threads:[~2007-02-14 0:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 0:37 Chuck Ebbert [this message]
2007-02-14 3:52 ` Help! How do I debug oopsing kernel workqueue threads? Nick Piggin
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=45D259C3.6070109@redhat.com \
--to=cebbert@redhat.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 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.