BUG: scheduling while atomic: mkinitramfs/8432/0x10000001
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Description: Ubuntu maverick (development branch)
Release: 10.10
Crashed on upgrade.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: No
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.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/seq: timidity 1763 F.... timidity
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x98400000 irq 46'
Mixer name : 'Realtek ALC268'
Components : 'HDA:10ec0268,
Controls : 12
Simple ctrls : 9
Date: Sat Aug 21 16:28:15 2010
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Acer Aspire 7720Z
ProcCmdLine: BOOT_IMAGE=
RelatedPackageV
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: BUG: scheduling while atomic: mkinitramfs/
dmi.bios.date: 11/10/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.45
dmi.board.
dmi.board.name: Poyang
dmi.board.vendor: Acer
dmi.board.version: V1.45
dmi.chassis.type: 1
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: Aspire 7720Z
dmi.product.
dmi.sys.vendor: Acer
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.