BUG: scheduling while atomic: swapper/0/0x10000100

Bug #530435 reported by Martin
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

BUG: scheduling while atomic: swapper/0/0x10000100

Linux hpubu 2.6.32-14-generic #20-Ubuntu SMP Sat Feb 20 05:38:50 UTC 2010 i686 GNU/Linux

ProblemType: KernelOops
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: martin 1443 F.... pulseaudio
 /dev/snd/pcmC0D0p: martin 1443 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0x84000000 irq 16'
   Mixer name : 'Analog Devices AD1981'
   Components : 'HDA:11d41981,103c30c2,00100200 HDA:11c11040,103c1378,00100200'
   Controls : 12
   Simple ctrls : 10
Date: Mon Mar 1 17:21:18 2010
DistroRelease: Ubuntu 10.04
Failure: oops
Frequency: Once every few days.
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
MachineType: Hewlett-Packard HP Compaq 6715s (KE009ET#AK8)
Package: linux-image-2.6.32-14-generic 2.6.32-14.20
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-14-generic root=UUID=03f3f962-7783-4ca1-8aab-df6de3614d37 ro quiet quiet splash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
Regression: No
RelatedPackageVersions: linux-firmware 1.31
Reproducible: No
SourcePackage: linux
TestedUpstream: No
Title: BUG: scheduling while atomic: swapper/0/0x10000100
Uname: Linux 2.6.32-14-generic i686
dmi.bios.date: 11/25/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68YTT Ver. F.0E
dmi.board.name: 30C2
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.2D
dmi.chassis.asset.tag: CNU8200K7K
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68YTTVer.F.0E:bd11/25/2008:svnHewlett-Packard:pnHPCompaq6715s(KE009ET#AK8):pvrF.0E:rvnHewlett-Packard:rn30C2:rvrKBCVersion71.2D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6715s (KE009ET#AK8)
dmi.product.version: F.0E
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Martin (martinmartiini-deactivatedaccount) wrote :
Revision history for this message
Chase Douglas (chasedouglas) wrote :

If this issue comes up when you are using bluetooth, please test the kernel with version ending in ~lp534549 at http://people.canonical.com/~cndougla/534549/. Otherwise, if you can figure out how to trigger the issue please install the other kernel (the sched_trace one) and do the following:

# echo function >/sys/kernel/debug/tracing/current_tracer
# ech0 1 >/sys/kernel/debug/tracing/options/latency-format
# echo 1 >/sys/kernel/debug/tracing/tracing_enabled

Then do whatever you need to trigger the issue. Once the bug has been triggered, do:

# cat /sys/kernel/debug/tracing/trace | bzip2 >/tmp/trace.bz2

Finally, attach the trace.bz2 file to this bug so we can take a look.

If you can't figure out a reproduction scenario, try to run the commands anyways. When you get an apport notification of the bug, capture the trace output. I think this will still be safe, but I'm not 100% positive. If you've captured the trace file and it's exceedingly large, feel free to cut out all but the last few hundred lines.

Thanks

Changed in linux (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
importance: Low → Medium
Revision history for this message
MikeCamel (mike-hingston) wrote :

Seems to have happened on coming back from suspend or hibernate (I'm not sure which).

Revision history for this message
Miroslav Hadzhiev (xtigyro) wrote :

It happens often when I use my Bluetooth adapter or when I connect a flash memory adapter.

Revision history for this message
Martin (martinmartiini-deactivatedaccount) wrote :

I'm the reporter of this bug.
This error message may have happened when resuming from sleep or when using bluetooth.
Seems bugs have disappeared with subsequent Ubuntu 10.04 lucid updates

Revision history for this message
Miroslav Hadzhiev (xtigyro) wrote :

I can confirm that the bug occurs very often when the integrated Bluetooth adapter on my laptop is used.

Lucid Beta1 (fully "dist-upgraded").

Revision history for this message
Chase Douglas (chasedouglas) wrote :

Please see bug 534549. It was fixed in the 2.6.32-17 kernel, which did not make it into beta 1. I'm marking this bug as a duplicate because of the similarities. If anyone finds that they still have an issue on the -17 or later kernel, please unduplicate the bug and provide as much information as possible (a trace as requested above would be most helpful).

Revision history for this message
Chase Douglas (chasedouglas) wrote :

I should clarify: If you find that you have the same error message as the title of this bug, it may be the same issue or a completely different issue. It's not even possible to tell based on the oops message. The only definitive way is through a trace. The bug reporter (Martini) stated that it seemed related to bluetooth and was fixed just after the -17 kernel was released. If you find you have the same symptoms when using bluetooth on a -17 or later kernel, please reopen this bug. If you have a similar looking issue triggered by something else, please open a different bug and do try to get a trace log.

Revision history for this message
Adam Hallgat (hallgat) wrote :

Well this bug affect Natty Narvhal. Usually when using firefox.

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.