Kernel bug: bad: scheduling from the idle thread!

[gimik]

klogd continuously reports the following (increasing CPU consumption to 100% on core-1)
see attached <htop> screenshot for details - no idea what generated this behavior. sorry.

[30556.723250] bad: scheduling from the idle thread!
[30556.723253] Pid: 0, comm: swapper Tainted: P 2.6.27-7-generic #1
[30556.723255] [<c037c406>] ? printk+0x1d/0x1f
[30556.723259] [<c0122b8a>] dequeue_task_idle+0x2a/0x40
[30556.723261] [<c012107f>] dequeue_task+0xcf/0x130
[30556.723265] [<c012112a>] deactivate_task+0x1a/0x30
[30556.723268] [<c037ca23>] schedule+0x4b3/0x790
[30556.723271] [<c0380ff5>] ? notifier_call_chain+0x35/0x70
[30556.723275] [<c0151b55>] ? clockevents_notify+0x35/0x80
[30556.723282] [<f885fa43>] ? ticks_elapsed_in_us+0xb/0x4d [processor]
[30556.723291] [<f88602d7>] ? acpi_state_timer_broadcast+0x36/0x39 [processor]
[30556.723297] [<c0153d82>] ? tick_nohz_stop_idle+0x12/0x70
[30556.723301] [<c0153e15>] ? tick_nohz_restart_sched_tick+0x35/0x180
[30556.723304] [<c01028cd>] cpu_idle+0xbd/0x140
[30556.723307] [<c037a661>] start_secondary+0x9d/0xcc
[30556.723310] =======================

[Anthony Noto (angusthefuzz)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!

[gimik (gimik-fr)]

Hi,
Here is the requested information (see attached log files).
uname -a -> Linux vaio-ncl 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20
UTC 2008 i686 GNU/Linux
My machine is a Sony VAIO laptop (ref. VGN-AW11M)
Regards,
Nicolas

Anthony Noto a écrit :
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Unfortunately we can't fix it without more information.
>
> Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
> 1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
> 2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
> 3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
>
> For your reference, the full description of procedures for kernel-
> related bug reports is available at
> https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance!
>
> ** Changed in: linux (Ubuntu)
> Sourcepackagename: None => linux
> Assignee: (unassigned) => Anthony Noto (angusthefuzz)
> Status: New => Incomplete
>
>

[Anthony Noto (angusthefuzz)]

The posted dmesg.log does not contain the error posted in the bug description. Would it be possible to post a dmesg that contains that error? Thanks in advance.

[gimik (gimik-fr)]

Sorry but the problem is not systematic. In fact it occurred only once
since I installed Ubuntu 8.10 and I don't know how to reproduce it.
Consequently, I can't provide more than the log I sent in my first mail
(i.e. when I entered the bug in the bug tracking system).
NL

Anthony Noto a écrit :
> The posted dmesg.log does not contain the error posted in the bug
> description. Would it be possible to post a dmesg that contains that
> error? Thanks in advance.
>
>

[Heiko (heiko-barg)]

I can confirm this bug. I attached dmesg.log file containing the requested output.

[Alex Jones (blenheimears)]

This bug is affecting me too. I have a Dell XPS m1330 laptop with Ubuntu 8.10 64-bit. This bug causes the entire disk (320 GB) to become filled with kernel message logs after just a few days. It does not affect my desktop computer (Dell XPS 700). Ubuntu should really consider using vanilla kernels like Slackware instead of screwing the kernel up with custom code. I've never had a single kernel problem with Slackware (which uses a vanilla kernel) and I've used it for 4 years. I've had about 5 kernel problems with Ubuntu after using it for 3 months!

[Jamie Bainbridge (superjamie)]

Same thing happened to me today. Dell Vostro 1200 laptop with Ubuntu 8.10, which I upgraded from Hardy.

At the time, GDM was running but my Gnome\Openbox session wasn't logged in. I did have rtorrent running inside a screen, which I'd started via ssh, detached and logged off the ssh session.

Here is the output requested above:

superjamie@zero:~$ uname -a
Linux zero 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 GNU/Linux

[Jamie Bainbridge (superjamie)]

dmesg while in error state

[Jamie Bainbridge (superjamie)]

dmesg from fresh reboot

[Jamie Bainbridge (superjamie)]

Happened again last night. I may be able to reproduce this one with ~12 hours wait.

Could importance be upgraded on this one?

[Jamie Bainbridge (superjamie)]

Looks like this may also be a duplicate bug report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285

(sorry for comment spam)

[Matthias Meier (matthias-j-meier)]

Happens to me as well since 2.6.27 (intrepid) in iregular intervals (once a day .. weeks).
Probably the 4965AGN WIFI Driver (iwlagn) ??

[Jamie Bainbridge (superjamie)]

@Matthias: Yes, please read the duplicate bug report. The patched module which fixes it is in intrepid-proposed, install kernel 2.6.27-10 and related packages

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.