BUG: scheduling while atomic: bash/2343/0x10000001
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have installed the latest version of the kernel and restart and this bug start to appear.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: No
ProcVersionSign
Uname: Linux 2.6.35-16-generic i686
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf6afc000 irq 47'
Mixer name : 'IDT 92HD71B7X'
Components : 'HDA:111d76b2,
Controls : 25
Simple ctrls : 16
Date: Sat Aug 21 01:21:53 2010
Failure: oops
Frequency: Once every few days.
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Dell Inc. Inspiron 1545
ProcCmdLine: BOOT_IMAGE=
RelatedPackageV
SourcePackage: linux
Title: BUG: scheduling while atomic: bash/2343/
dmi.bios.date: 02/25/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0G848F
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 1545
dmi.sys.vendor: Dell Inc.
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 620810, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.