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) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I'm a newbie, the notification indicated a error and asked me if I want to send a bug report. So here it's.
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] 没有该文件或目录
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfea74000 irq 22'
Mixer name : 'Realtek ALC888'
Components : 'HDA:10ec0888,
Controls : 36
Simple ctrls : 21
Date: Tue Nov 3 10:36:28 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
IwConfig:
lo no wireless extensions.
eth0 no wireless extensions.
vboxnet0 no wireless extensions.
MachineType: Foxconn G33M03
Package: linux-image-
ProcCmdLine: root=UUID=
ProcVersionSign
RelatedPackageV
linux-
linux-firmware 1.24
RfKill:
SourcePackage: linux
Tags: kernel-oops
Title: [318817.672531] ------------[ cut here ]------------
Uname: Linux 2.6.31-14-generic i686
WpaSupplicantLog:
dmi.bios.date: 09/18/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080014
dmi.board.name: G33M03
dmi.board.vendor: FOXCONN
dmi.board.version: 1.0
dmi.chassis.type: 6
dmi.chassis.vendor: FOXCONN
dmi.modalias: dmi:bvnAmerican
dmi.product.name: G33M03
dmi.product.
dmi.sys.vendor: Foxconn
summary: |
- kernel problem + WARNING: at + /build/buildd/linux-2.6.31/fs/notify/inotify/inotify_fsnotify.c:129 + idr_callback+0x4f/0x80() |
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 442966, 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.