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

[Matt Hancock]

Not quite sure what happened. Started watching Hulu, hit "pause" and then "crash report detected" went on on the top panel.

ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-19-generic 2.6.32-19.28
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelModules: wl
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: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: matt 1592 F.... pulseaudio
 /dev/snd/pcmC0D0p: matt 1592 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf8500000 irq 22'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,10280273,00100003'
   Controls : 13
   Simple ctrls : 8
Date: Sun Apr 4 22:34:08 2010
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=UUID=42f078e4-1d92-443f-8cd7-4ec90aaf51c7
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Dell Inc. Vostro1510
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=3b697d48-37fb-4f37-b950-d09abaa626e0 ro quiet splash
RelatedPackageVersions: linux-firmware 1.33
RfKill:
 0: dell-wifi: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: BUG: scheduling while atomic: swapper/0/0x10010000
dmi.bios.date: 07/31/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0M277C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd07/31/2008:svnDellInc.:pnVostro1510:pvrNull:rvnDellInc.:rn0M277C:rvr:cvnDellInc.:ct8:cvrN/A:
dmi.product.name: Vostro1510
dmi.product.version: Null
dmi.sys.vendor: Dell Inc.

[Chase Douglas (chasedouglas)]

@Matt:

The oops text normally contains data we need to debug the issue. However, for these bugs the data is useless. To get the data we need, please do the following:

$ sudo sh -c "echo function > /sys/kernel/debug/tracing/current_tracer"

Trigger the bug, then capture the trace output:

$ cat /sys/kernel/debug/tracing/trace | bzip2 -c > trace.bz2

Then upload trace.bz2 to this bug report.

Thanks

[Chase Douglas (chasedouglas)]

My initial instructions were a little wrong. Please see the instructions at https://wiki.ubuntu.com/KernelTeam/DebuggingSchedulingWhileAtomic

Thanks

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]