WARNING: at /build/buildd/linux-2.6.31/fs/notify/inotify/inotify_user.c:398 inotify_remove_from_idr+0x7e/0x90()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Orange notification of a crash report, but no functionality lost as far as I could tell.
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 'Intel'/'HDA Intel at 0xdfffc000 irq 21'
Mixer name : 'SigmaTel STAC9200'
Components : 'HDA:83847690,
Controls : 13
Simple ctrls : 8
Card1.Amixer.info:
Card hw:1 'Xmod'/'Creative Technology Ltd Creative Xmod at usb-0000:00:1d.3-1, full speed'
Mixer name : 'USB Mixer'
Components : 'USB041e:30d0'
Controls : 7
Simple ctrls : 5
Date: Sat Oct 31 18:32:37 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
MachineType: Dell Inc. Latitude D820
NonfreeKernelMo
Package: linux-image-
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdLine: root=UUID=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-14-generic i686
WpaSupplicantLog:
dmi.bios.date: 03/23/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0JF240
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude D820
dmi.sys.vendor: Dell Inc.
summary: |
- Didn't actually notice a change, just saw a crash report + WARNING: at + /build/buildd/linux-2.6.31/fs/notify/inotify/inotify_user.c:398 + inotify_remove_from_idr+0x7e/0x90() |
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 432860, 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.