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
Probably it's a duplicate of bugs #436786 and/or #434603 but when I clicked "yes, this is the bug I'm trying to report" button and a new little window opened I was not able to close it with a small tick button (regardless what I chose i the window). That's why I reportin a new bug.
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 0xfb000000 irq 22'
Mixer name : 'Realtek ALC889A'
Components : 'HDA:10ec0885,
Controls : 44
Simple ctrls : 25
Date: Sun Sep 27 23:16:28 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
vboxnet0 no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P35-DS3R
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-11-generic i686
dmi.bios.date: 06/19/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F13
dmi.board.name: P35-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: P35-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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 436263, 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.