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
Oops during apt-get upgrade
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xd4540000 irq 21'
Mixer name : 'Realtek ALC861-VD'
Components : 'HDA:10ec0862,
Controls : 19
Simple ctrls : 13
Date: Wed Oct 21 01:30:29 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
MachineType: FUJITSU SIEMENS AMILO Pro Edition V3505
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: [290676.415139] ------------[ cut here ]------------
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 04/27/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R01-B0G
dmi.board.name: AMILO Pro Edition V3505
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: AMILO Pro Edition V3505
dmi.product.
dmi.sys.vendor: FUJITSU SIEMENS
summary: |
- [290676.415139] ------------[ cut here ]------------ + 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.