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
i dont know maybe this is a some inotify problem.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC660-VD Analog [ALC660-VD Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC660-VD Analog [ALC660-VD 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 'Intel'/'HDA Intel at 0xfeaf8000 irq 22'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,
Controls : 13
Simple ctrls : 8
Date: Thu Nov 5 23:03:26 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
MachineType: TOSHIBA Satellite L40
Package: linux-image-
ProcCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 05/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.00
dmi.board.
dmi.board.name: Satellite L40
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.modalias: dmi:bvnAmerican
dmi.product.name: Satellite L40
dmi.product.
dmi.sys.vendor: TOSHIBA
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.