Comment 181 for bug 286285

Revision history for this message
In , Tom (tom-redhat-bugs) wrote :

Got this again with 4-69.fc10.x86_64:

[root@tlondon ~]# ls -l /var/log/messages
-rw------- 1 root root 5394885080 2008-11-01 17:36 /var/log/messages
[root@tlondon ~]#

Is there some additional information I can provide that would be helpful?

Nov 1 17:31:34 tlondon kernel: bad: scheduling from the idle thread!
Nov 1 17:31:34 tlondon kernel: Pid: 0, comm: swapper Not tainted 2.6.27.4-69.fc10.x86_64 #1
Nov 1 17:31:34 tlondon kernel:
Nov 1 17:31:34 tlondon kernel: Call Trace:
Nov 1 17:31:34 tlondon kernel: [<ffffffff81033770>] dequeue_task_idle+0x32/0x3f
Nov 1 17:31:34 tlondon kernel: [<ffffffff81031a62>] dequeue_task+0xbf/0xca
Nov 1 17:31:34 tlondon kernel: [<ffffffff81031ab9>] deactivate_task+0x22/0x2b
Nov 1 17:31:34 tlondon kernel: [<ffffffff81352dc0>] schedule+0x1f2/0x7c5
Nov 1 17:31:34 tlondon kernel: [<ffffffff810575aa>] ? enqueue_hrtimer+0xd3/0xe1
Nov 1 17:31:34 tlondon kernel: [<ffffffff8100f2cd>] cpu_idle+0x106/0x10b
Nov 1 17:31:34 tlondon kernel: [<ffffffff8134f7a6>] start_secondary+0x16e/0x173
Nov 1 17:31:34 tlondon kernel:
Nov 1 17:31:34 tlondon kernel: bad: scheduling from the idle thread!
Nov 1 17:31:34 tlondon kernel: Pid: 0, comm: swapper Not tainted 2.6.27.4-69.fc10.x86_64 #1
Nov 1 17:31:34 tlondon kernel:
Nov 1 17:31:34 tlondon kernel: Call Trace:
Nov 1 17:31:34 tlondon kernel: [<ffffffff81033770>] dequeue_task_idle+0x32/0x3f
Nov 1 17:31:34 tlondon kernel: [<ffffffff81031a62>] dequeue_task+0xbf/0xca
Nov 1 17:31:34 tlondon kernel: [<ffffffff81031ab9>] deactivate_task+0x22/0x2b
Nov 1 17:31:34 tlondon kernel: [<ffffffff81352dc0>] schedule+0x1f2/0x7c5
Nov 1 17:31:34 tlondon kernel: [<ffffffff810575aa>] ? enqueue_hrtimer+0xd3/0xe1
Nov 1 17:31:34 tlondon kernel: [<ffffffff8100f2cd>] cpu_idle+0x106/0x10b
Nov 1 17:31:34 tlondon kernel: [<ffffffff8134f7a6>] start_secondary+0x16e/0x173
Nov 1 17:31:34 tlondon kernel: