From: Andrew Morton <akpm@linux-foundation.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@ucw.cz>,
linux-pm@lists.linux-foundation.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: 2.6.21-mm1 hwsusp: BUG at workqueue.c:106
Date: Tue, 8 May 2007 02:11:31 -0700 [thread overview]
Message-ID: <20070508021131.438cee31.akpm@linux-foundation.org> (raw)
In-Reply-To: <46403B7F.1050009@gmail.com>
On Tue, 08 May 2007 10:57:35 +0200 Jiri Slaby <jirislaby@gmail.com> wrote:
>
> this occured in dmesg during resuming from hwsusp in 2.6.21-mm1 (captured
> through netconsole). Perfectly reproducible, it simply happens each time I
> try it.
Let's cc Oleg.
> usb_endpoint usbdev5.1_ep00: PM: resume from 0, parent usb5 still 2
> ------------[ cut here ]------------
> kernel BUG at /home/l/latest/xxx/kernel/workqueue.c:106!
> invalid opcode: 0000 [#1]
> SMP
> Modules linked in: ipv6 floppy ohci1394 ieee1394 parport_pc parport usbhid
> ehci_hcd pata_acpi ff_memless sr_mod cdrom
> CPU: 1
> EIP: 0060:[<c0132161>] Not tainted VLI
> EFLAGS: 00010046 (2.6.21-mm1 #272)
> EIP is at insert_work+0x6d/0x71
> eax: c1c3b3c0 ebx: c1814aa0 ecx: 00000001 edx: c1814aa0
> esi: c1c3b340 edi: 00000282 ebp: c04d2f68 esp: c04d2f50
> ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068
> Process swapper (pid: 0, ti=c04d2000 task=c1c26030 task.ti=c1c20000)
> Stack: c4685f54 c18148ac c04d2f98 c013816f c1c3b340 c1814aa0 c04d2f88 c013256c
> 00000066 c1814880 c1c5e000 c04d2fc4 c01325a1
> c1c5e000 00000100 c012ba35 00000000 c04d2fb8 c01333f4 Call Trace:
> [<c0104f27>] [<c0104fe2>] show_stack_log_lvl+0xa5/0xca
> show_registers+0x1e2/0x2da
> [<c01053f5>] [<c010559a>] do_trap+0x84/0xaa
> do_invalid_op+0x88/0x92
> [<c0378662>] [<c013256c>] __queue_work+0x22/0x33
> delayed_work_timer_fn+0x24/0x2a
> [<c012ba35>] [<c01288a9>] __do_softirq+0x75/0xe6
> do_softirq+0x63/0xac
> [<c0128713>] [<c0116d7e>] smp_apic_timer_interrupt+0x5c/0x88
> apic_timer_interrupt+0x28/0x30
> [<c010238d>] [<c0115ad0>] start_secondary+0x25e/0x37a
> 0x0
> =======================
> 00 00 ba 03 00 00 40 a3 ff 83 10 5b 5d c3 4e 04 56 04 43 04 42 04 53 04 48
> 04 46 04 c9 <0f> eb fe 89 e5 ec 0c
>
hm, how come it's so messy?
next prev parent reply other threads:[~2007-05-08 9:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 8:57 2.6.21-mm1 hwsusp: BUG at workqueue.c:106 Jiri Slaby
2007-05-08 9:11 ` Andrew Morton [this message]
2007-05-08 10:55 ` Oleg Nesterov
2007-05-08 11:09 ` Jiri Slaby
2007-05-08 12:00 ` Jiri Slaby
2007-05-08 13:48 ` Oleg Nesterov
2007-05-08 14:20 ` Oleg Nesterov
2007-05-08 14:30 ` [PATCH 1/1] vmstat-use-our-own-timer-events-fix Jiri Slaby
2007-05-08 14:42 ` Oleg Nesterov
2007-05-08 16:08 ` Christoph Lameter
2007-05-08 12:12 ` 2.6.21-mm1 hwsusp: BUG at workqueue.c:106 Jarek Poplawski
2007-05-08 12:40 ` Oleg Nesterov
2007-05-08 10:51 ` Jarek Poplawski
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=20070508021131.438cee31.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=oleg@tv-sign.ru \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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