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) |
New
|
Undecided
|
Unassigned |
Bug Description
Unfortunately I'm never attending the system when this crash report appears, so I do not know how to reproduce.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xfe7f4000 irq 16'
Mixer name : 'VIA VT1708S'
Components : 'HDA:11060397,
Controls : 31
Simple ctrls : 17
Card1.Amixer.info:
Card hw:1 'U0x46d0x8d7'/'USB Device 0x46d:0x8d7 at usb-0000:00:12.0-1, full speed'
Mixer name : 'USB Mixer'
Components : 'USB046d:08d7'
Controls : 3
Simple ctrls : 2
Date: Mon Oct 26 16:38:05 2009
DistroRelease: Ubuntu 9.10
Failure: oops
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: root=/dev/md0 ro quiet splash
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-
WpaSupplicantLog:
dmi.bios.date: 04/09/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.20
dmi.board.name: A780GMH/128M
dmi.board.vendor: ASRock
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
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 #468015, 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.