[129256.520535] ------------[ cut here ]------------
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
automatically caught kernel oops
ProblemType: KernelOops
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: ALC861-VD Analog [ALC861-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd2400000 irq 22'
Mixer name : 'Realtek ALC861-VD'
Components : 'HDA:10ec0862,
Controls : 19
Simple ctrls : 12
Card1.Amixer.info:
Card hw:1 'U0x41e0x4058'
Mixer name : 'USB Mixer'
Components : 'USB041e:4058'
Controls : 3
Simple ctrls : 2
Date: Thu Oct 22 09:39:03 2009
DistroRelease: Ubuntu 9.10
Failure: oops
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate amd64 (20091019.2)
MachineType: LENOVO 0768FSG
NonfreeKernelMo
Package: linux-image-
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: [129256.520535] ------------[ cut here ]------------
Uname: Linux 2.6.31-14-generic x86_64
dmi.bios.date: 04/30/07
dmi.bios.vendor: LENOVO
dmi.bios.version: 63ET62WW
dmi.board.name: CAPELL VALLEY(NAPA) CRB
dmi.board.vendor: LENOVO
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 0768FSG
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 417842, 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. Please continue to report any other bugs you may find.