BUG: scheduling while atomic: swapper/0/0x10000100
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
This is related to bluetooth.
On a fresh, ubuntu-desktop Lucid Lynx install, trying to connect to my a2dp headphone generate this bug.
Can be reproduced: just boot, turn on bluetooth headphone and bang!
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: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] Nessun file o directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe8280000 irq 21'
Mixer name : 'Analog Devices AD1984A'
Components : 'HDA:11d4194a,
Controls : 10
Simple ctrls : 6
Date: Mon Mar 8 18:42:09 2010
DistroRelease: Ubuntu 10.04
Failure: oops
HibernationDevice: RESUME=
MachineType: Hewlett-Packard HP 2140
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
Regression: Yes
RelatedPackageV
Reproducible: Yes
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
TestedUpstream: Yes
Title: BUG: scheduling while atomic: swapper/
Uname: Linux 2.6.32-16-generic i686
dmi.bios.date: 06/18/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DGU Ver. F.04
dmi.board.name: 3056
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 20.0D
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP 2140
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Changed in linux (Ubuntu): | |
status: | Triaged → In Progress |
Changed in linux (Ubuntu): | |
assignee: | Chase Douglas (chasedouglas) → nobody |
The preempt_counter shows both PREEMPT_ACTIVE and in a softirq context. I *think* this likely means a process was in the middle of a softirq handler or a tasklet when a subroutine put it to sleep. I'm building a test kernel right now that will output extra debug information so we can see what the softirq stack was as it was put to scheduled out. I'll update this bug with a test kernel location when I get it uploaded.