BUG: scheduling while atomic: swapper/0/0x10010000
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
some serious kernel problem is there.
ProblemType: KernelOops
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: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfc500000 irq 22'
Mixer name : 'IDT 92HD73C1X5'
Components : 'HDA:111d7675,
Controls : 23
Simple ctrls : 14
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfc010000 irq 17'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,
Controls : 4
Simple ctrls : 1
Card1.Amixer.
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [off]
Date: Tue Feb 23 23:28:22 2010
DistroRelease: Ubuntu 9.10
Failure: oops
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Dell Inc. Studio 1555
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: BUG: scheduling while atomic: swapper/
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 11/07/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0C234M
dmi.board.vendor: Dell Inc.
dmi.board.version: A08
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Studio 1555
dmi.product.
dmi.sys.vendor: Dell Inc.
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.