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:
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! 4-69.fc10. x86_64 #1 770>] dequeue_ task_idle+ 0x32/0x3f a62>] dequeue_ task+0xbf/ 0xca ab9>] deactivate_ task+0x22/ 0x2b dc0>] schedule+ 0x1f2/0x7c5 5aa>] ? enqueue_ hrtimer+ 0xd3/0xe1 2cd>] cpu_idle+ 0x106/0x10b 7a6>] start_secondary +0x16e/ 0x173 4-69.fc10. x86_64 #1 770>] dequeue_ task_idle+ 0x32/0x3f a62>] dequeue_ task+0xbf/ 0xca ab9>] deactivate_ task+0x22/ 0x2b dc0>] schedule+ 0x1f2/0x7c5 5aa>] ? enqueue_ hrtimer+ 0xd3/0xe1 2cd>] cpu_idle+ 0x106/0x10b 7a6>] start_secondary +0x16e/ 0x173
Nov 1 17:31:34 tlondon kernel: Pid: 0, comm: swapper Not tainted 2.6.27.
Nov 1 17:31:34 tlondon kernel:
Nov 1 17:31:34 tlondon kernel: Call Trace:
Nov 1 17:31:34 tlondon kernel: [<ffffffff81033
Nov 1 17:31:34 tlondon kernel: [<ffffffff81031
Nov 1 17:31:34 tlondon kernel: [<ffffffff81031
Nov 1 17:31:34 tlondon kernel: [<ffffffff81352
Nov 1 17:31:34 tlondon kernel: [<ffffffff81057
Nov 1 17:31:34 tlondon kernel: [<ffffffff8100f
Nov 1 17:31:34 tlondon kernel: [<ffffffff8134f
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.
Nov 1 17:31:34 tlondon kernel:
Nov 1 17:31:34 tlondon kernel: Call Trace:
Nov 1 17:31:34 tlondon kernel: [<ffffffff81033
Nov 1 17:31:34 tlondon kernel: [<ffffffff81031
Nov 1 17:31:34 tlondon kernel: [<ffffffff81031
Nov 1 17:31:34 tlondon kernel: [<ffffffff81352
Nov 1 17:31:34 tlondon kernel: [<ffffffff81057
Nov 1 17:31:34 tlondon kernel: [<ffffffff8100f
Nov 1 17:31:34 tlondon kernel: [<ffffffff8134f
Nov 1 17:31:34 tlondon kernel: