scheduling while atomic: swapper

Bug #71519 reported by Torsten Schönfeld
2
Affects Status Importance Assigned to Milestone
linux-meta (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Without any apparent reason, my CPU load is 100% and the kernel log contains lots and lots of these:

Nov 12 18:17:11 localhost kernel: [17195061.884000] BUG: scheduling while atomic: swapper/0x029cd03f/0
Nov 12 18:17:11 localhost kernel: [17195061.884000] <c02c570a> schedule+0x43a/0x5d0 <c01056fe> do_IRQ+0x1e/0x30
Nov 12 18:17:11 localhost kernel: [17195061.884000] <c0103e8a> common_interrupt+0x1a/0x20 <c010200f> cpu_idle+0x4f/0x60
Nov 12 18:17:11 localhost kernel: [17195061.884000] <c03d067b> start_kernel+0x1fb/0x2d0 <c03d0210> unknown_bootoption+0x0/0x270

There about 60 of these per second.

Tags: kernel-bug
description: updated
Revision history for this message
Chuck Short (zulcss) wrote :

Which kernel is this with?

chuck

Changed in linux-meta:
status: Unconfirmed → Needs Info
Revision history for this message
Torsten Schönfeld (kaffeetisch) wrote :

It's linux-image-2.6.17-10-386.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :

 Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the following additional information, if you have not already done so (please 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" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "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 here: <http://wiki.ubuntu.com/DebuggingKernelProblems> Thanks!

Revision history for this message
Torsten Schönfeld (kaffeetisch) wrote :

I haven't seen that bug again after I reported it, so I don't know if it still exists. But here's the info you requested anyway:

uname -a:
Linux kaffeetisch 2.6.17-11-386 #2 Thu Feb 1 19:50:13 UTC 2007 i686 GNU/Linux

Revision history for this message
Torsten Schönfeld (kaffeetisch) wrote :
Revision history for this message
Torsten Schönfeld (kaffeetisch) wrote :

Looks like lspci needs superuser privileges to access some information.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux-meta (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.