WARNING: at /build/buildd/linux-2.6.31/fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x4f/0x80()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
crash applet just comes out and report there is a kernel crash happens, not sure what happens really.
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: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'MID'/'HDA Intel MID at 0xd83a0000 irq 22'
Mixer name : 'Silicon Image SiI1392 HDMI'
Components : 'HDA:10ec0269,
Controls : 18
Simple ctrls : 10
Date: Mon Nov 2 09:29:52 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
pan0 no wireless extensions.
MachineType: Dell Inc. Inspiron 1010
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: [291214.693864] ------------[ cut here ]------------
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 02/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0G651M
dmi.board.vendor: Dell Inc.
dmi.board.version: A03
dmi.chassis.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 1010
dmi.product.
dmi.sys.vendor: Dell Inc.
summary: |
- not sure what happens + WARNING: at + /build/buildd/linux-2.6.31/fs/notify/inotify/inotify_fsnotify.c:129 + idr_callback+0x4f/0x80() |
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 442966, 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.