BUG: scheduling while atomic: swapper/0/0x10010000
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
Chase Douglas |
Bug Description
What was expected:
When the RF killswitch is turned on Bluetooth is supposed to turn on.
What happened:
When the RF killswtich is turned on Bluetooth turns on but also I get a crash reported in dmesg and Apport.
I will try different kernel tomorrow and report back the results.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebfc000 irq 21'
Mixer name : 'SigmaTel STAC9228'
Components : 'HDA:83847616,
Controls : 28
Simple ctrls : 18
Date: Sun Apr 4 13:25:24 2010
Failure: oops
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
MachineType: Dell Inc. Vostro 1400
ProcCmdLine: BOOT_IMAGE=
RelatedPackageV
SourcePackage: linux
Title: BUG: scheduling while atomic: swapper/
dmi.bios.date: 07/10/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0TT361
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Vostro 1400
dmi.sys.vendor: Dell Inc.
CVE References
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Committed |
@lightrush:
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