BUG: scheduling while atomic: run-mozilla.sh/1767/0x10000001
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
happened twice I think when booting up...
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: No
ProcVersionSign
Uname: Linux 2.6.35-16-generic i686
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
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 0xfdff4000 irq 42'
Mixer name : 'Realtek ALC888'
Components : 'HDA:10ec0888,
Controls : 41
Simple ctrls : 23
Card1.Amixer.info:
Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
Mixer name : 'Nvidia GT21x HDMI'
Components : 'HDA:10de000b,
Controls : 16
Simple ctrls : 4
Date: Fri Aug 20 20:27:45 2010
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
MachineType: Dell Inc. Inspiron 530
ProcCmdLine: root=UUID=
RelatedPackageV
RfKill:
SourcePackage: linux
Title: BUG: scheduling while atomic: run-mozilla.
WpaSupplicantLog:
dmi.bios.date: 07/12/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.3
dmi.board.name: 0RY007
dmi.board.vendor: Dell Inc.
dmi.board.version: ���
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 530
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.