BUG: scheduling while atomic: mkinitramfs/13260/0x10000001
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This is one of several kernel errors that came up. I was compiling VirtualBox host drivers at the time, but I'm not sure to what extent that had an impact.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: No
Reproducible: No
ProcVersionSign
Uname: Linux 2.6.35-17-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: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: jcollins 1550 F...m pulseaudio
/dev/snd/seq: timidity 1312 F.... timidity
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf4a00000 irq 47'
Mixer name : 'Conexant CX20561 (Hermosa)'
Components : 'HDA:80862802,
Controls : 18
Simple ctrls : 8
Date: Sat Aug 21 09:22:22 2010
Failure: oops
Frequency: I don't know.
HibernationDevice: RESUME=
MachineType: LENOVO 444623U
ProcCmdLine: root=UUID=
RelatedPackageV
RfKill:
SourcePackage: linux
Title: BUG: scheduling while atomic: mkinitramfs/
WpaSupplicantLog:
dmi.bios.date: 04/01/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 6GET17WW(V1.08)
dmi.board.name: KIWDX
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 444623U
dmi.product.
dmi.sys.vendor: LENOVO
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.