Messages in this thread | | | Date | Thu, 2 Nov 2006 19:25:01 +0100 | From | Paolo Ornati <> | Subject | BUG: scheduling while atomic: events/0/0x00000001/4, etc.. |
| |
kernel: 2.6.19-rc4-g4b1c46a3
Today I've got these 2 type of messages in kernel log:
1)
BUG: scheduling while atomic: events/0/0x00000001/4
Call Trace: [<ffffffff8049fafb>] __sched_text_start+0x5b/0x4cc [<ffffffff802f34b6>] list_add+0xc/0xe [<ffffffff80236519>] worker_thread+0x0/0x11b [<ffffffff802365ce>] worker_thread+0xb5/0x11b [<ffffffff802233e2>] default_wake_function+0x0/0xf [<ffffffff80236519>] worker_thread+0x0/0x11b [<ffffffff80239269>] kthread+0xce/0x101 [<ffffffff802234b1>] schedule_tail+0x30/0xa2 [<ffffffff8020a238>] child_rip+0xa/0x12 [<ffffffff8023919b>] kthread+0x0/0x101 [<ffffffff8020a22e>] child_rip+0x0/0x12
2)
BUG: sleeping function called from invalid context at include/asm/semaphore.h:105 in_atomic():1, irqs_disabled():0
Call Trace: [<ffffffff8049ff6c>] thread_return+0x0/0xf9 [<ffffffff802226ae>] __might_sleep+0xb2/0xb4 [<ffffffff8022749a>] acquire_console_sem+0x66/0x90 [<ffffffff80358086>] console_callback+0xe/0xde [<ffffffff80235fce>] run_workqueue+0xb6/0x126 [<ffffffff80236519>] worker_thread+0x0/0x11b [<ffffffff802365ff>] worker_thread+0xe6/0x11b [<ffffffff802233e2>] default_wake_function+0x0/0xf [<ffffffff80236519>] worker_thread+0x0/0x11b [<ffffffff80239269>] kthread+0xce/0x101 [<ffffffff802234b1>] schedule_tail+0x30/0xa2 [<ffffffff8020a238>] child_rip+0xa/0x12 [<ffffffff8023919b>] kthread+0x0/0x101 [<ffffffff8020a22e>] child_rip+0x0/0x12
---------------------------------------
They repeated themself every few senconds and when I noticed I was unable to get the full log because of log rotation...
Attached: config normal dmesg first 1000 lines of log
-- Paolo Ornati Linux 2.6.19-rc4-g4b1c46a3 on x86_64 [unhandled content-type:application/x-gzip][unhandled content-type:application/x-gzip][unhandled content-type:application/x-gzip] | |