Comment 82 for bug 286285

Revision history for this message
Dylan McCall (dylanmccall) wrote :

Wow, here is something super weird that has just cropped up on my system. (I also do not have the patch applied since I'm on amd64).

[11545.731478] bad: scheduling from the idle thread!
[11545.731482] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
[11545.731484]
[11545.731485] Call Trace:
[11545.731489] [<ffffffff8023e06d>] dequeue_task_idle+0x2d/0x40
[11545.731491] [<ffffffff8023c436>] dequeue_task+0x96/0xe0
[11545.731493] [<ffffffff8023c4d3>] deactivate_task+0x23/0x30
[11545.731496] [<ffffffff80500685>] thread_return+0x108/0x3c3
[11545.731499] [<ffffffff8026d12e>] ? sched_clock_idle_wakeup_event+0xe/0x10
[11545.731502] [<ffffffff80210ecd>] cpu_idle+0xad/0x110
[11545.731505] [<ffffffff804f0446>] rest_init+0x66/0x70
[11545.731507]
[11545.731538] bad: scheduling from the idle thread!
[11545.731540] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
[11545.731542]
[11545.731542] Call Trace:
[11545.731544] [<ffffffff8023e06d>] dequeue_task_idle+0x2d/0x40
[11545.731547] [<ffffffff8023c436>] dequeue_task+0x96/0xe0
[11545.731549] [<ffffffff8023c4d3>] deactivate_task+0x23/0x30
[11545.731551] [<ffffffff80500685>] thread_return+0x108/0x3c3
[11545.731554] [<ffffffff8026d12e>] ? sched_clock_idle_wakeup_event+0xe/0x10
[11545.731556] [<ffffffff80210ecd>] cpu_idle+0xad/0x110
[11545.731558] [<ffffffff804f0446>] rest_init+0x66/0x70
[11545.731560]

...and so on for infinity. That mesage is repeating itself CONSTANTLY. In fact, it is happening to the point that my system log has consumed the entire / partition (/var/log is over 4 GB). Ran an apt cleanup to avoid disaster and the freed 250 MB was consumed in less than an hour. (Someone really needs to fix that issue with log files dominating space). The problem is causing incredible slowdowns and instability, and it probably isn't just the log at fault considering the horribly ugly looking error message. Lots of stuff in it, though, so I hope it's useful!
My only proprietary driver is for the video card, so I'll try resurrecting some space and switching to the free driver.

System Log viewer hangs and ultimately is force killed; I got that stuff via dmesg.

Curiously, this did not happen before. Was there a stable kernel update recently? (I wasn't watching the updates very closely).