WARNING: at /build/buildd/linux-2.6.31/fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x4f/0x80()

Bug #437579 reported by Giacomo Gabriele
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
In Progress
Undecided
Unassigned

Bug Description

i don't know what is it

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
CRDA: Error: [Errno 2] Nessun file o directory
Card0.Amixer.info:
 Card hw:0 'Audigy'/'SB Audigy 1 [SB0090] (rev.3, serial:0x511102) at 0x9000, irq 17'
   Mixer name : 'TriTech TR28602'
   Components : 'AC97a:54524123'
   Controls : 194
   Simple ctrls : 30
Card1.Amixer.info:
 Card hw:1 'U0x46d0x8da'/'USB Device 0x46d:0x8da at usb-0000:00:02.1-3, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:08da'
   Controls : 3
   Simple ctrls : 2
Date: Sun Sep 27 11:59:01 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=6f830dac-7fc3-414a-9102-763032115058
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-10-generic 2.6.31-10.35
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=1d2ba24b-98f5-4896-bebc-2500778a4448 ro root=UUID=1d2ba24b-98f5-4896-bebc-2500778a4448 ro quiet splash resume=/dev/sdb1 nmi_watchdog=0
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-10-generic 2.6.31-10.12
 linux-firmware 1.19
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x4f/0x80()
Uname: Linux 2.6.31-10-generic i686
WpaSupplicantLog:

dmi.bios.date: 12/29/2005
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: nForce
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd12/29/2005:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnnForce:rvr:cvn:ct3:cvr:

Revision history for this message
Giacomo Gabriele (giacomo-gabriele-gmail) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Giacomo,

Can you comment how often you see this issue? Do you notice any other ill effects because of it? Can you narrow down any steps to reproduce? Thanks.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Geoff123 (gsking1) wrote :

I had a similar oops just happen. I was trying to get sound on my M2496 (ice1712) card working as it was only at low volume on the right channel. Sound was playing through qjackctl and the only other active program was mhwaveedit. I had just clicked on the kmix task bar and this happened. This is the first time for me seeing this, but I just went through the upgrade from jaunty yesterday so not many opportunities yet. The apport could not send other info due to to something about the report being corrupted. I'm going to reboot as it suggested.

I see it refernces the mother board as the hardware name, but I have the audio features disabled in the bios and only use the Maudio audiphile 2496 now.

[17243.904508] ------------[ cut here ]------------
[17243.904524] WARNING: at /build/buildd/linux-2.6.31/fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x4f/0x80()
[17243.904529] Hardware name: 945GZM-S2
[17243.904533] inotify closing but id=0 for entry=f57b4c80 in group=f0067a80 still in idr. Probably leaking memory
[17243.904537] Modules linked in: binfmt_misc ppdev nfsd exportfs nfs lockd nfs_acl auth_rpcgss sunrpc snd_ice1712 snd_ice17xx_ak4xxx snd_ak4xxx_adda snd_cs8427 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc ac97_bus snd_i2c snd_mpu401_uart snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device video1394 dv1394 raw1394 sbp2 iptable_filter snd ip_tables x_tables soundcore lp parport psmouse nvidia(P) serio_raw intel_agp agpgart usbhid dm_raid45 r8169 mii ohci1394 ieee1394 xor
[17243.904616] Pid: 4304, comm: digikam Tainted: P 2.6.31-11-generic #38-Ubuntu
[17243.904621] Call Trace:
[17243.904631] [<c014080d>] warn_slowpath_common+0x6d/0xa0
[17243.904637] [<c021137f>] ? idr_callback+0x4f/0x80
[17243.904642] [<c021137f>] ? idr_callback+0x4f/0x80
[17243.904648] [<c0140886>] warn_slowpath_fmt+0x26/0x30
[17243.904653] [<c021137f>] idr_callback+0x4f/0x80
[17243.904659] [<c030c136>] idr_for_each+0x76/0xd0
[17243.904663] [<c0211330>] ? idr_callback+0x0/0x80
[17243.904669] [<c020f4c7>] ? fsnotify_put_event+0x37/0x50
[17243.904675] [<c020f571>] ? fsnotify_flush_notify+0x91/0xa0
[17243.904683] [<c056b2f8>] ? _spin_lock+0x8/0x10
[17243.904688] [<c0211315>] inotify_free_group_priv+0x15/0x30
[17243.904694] [<c020f5e9>] fsnotify_final_destroy_group+0x19/0x30
[17243.904699] [<c020f6d7>] fsnotify_put_group+0x77/0x80
[17243.904704] [<c0211571>] inotify_release+0x21/0x40
[17243.904710] [<c01e432a>] __fput+0xda/0x1f0
[17243.904715] [<c01e4455>] fput+0x15/0x20
[17243.904721] [<c01e0a47>] filp_close+0x47/0x70
[17243.904727] [<c01e0ae3>] sys_close+0x73/0xb0
[17243.904732] [<c010334c>] syscall_call+0x7/0xb
[17243.904737] ---[ end trace c30214ae80aab6b9 ]---
[17243.904741] entry->group=(null) inode=(null) wd=1024

Revision history for this message
Geoff123 (gsking1) wrote :

I notice in the report that it mentions digikam. I did close digikam shortly before this oops. Maybe 30 seconds before.

Revision history for this message
Geoff123 (gsking1) wrote :

Please ignore the sound volume part of my description - this was due to a bad audio cable connection.

Revision history for this message
Malte Cornils (malte) wrote :

This happened to me, too, after closing digikam. I had sorted some pictures and imported some files from a USB disk (from a somewhat broken SD card - see dmesg snippet). Otherwise, a normal session on a recently upgraded system.
--snip--
[12644.638644] end_request: I/O error, dev sdb, sector 6221232
[12651.084789] sd 2:0:0:0: [sdb] Unhandled sense code
[12651.084797] sd 2:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[12651.084803] sd 2:0:0:0: [sdb] Sense Key : Medium Error [current]
[12651.084809] sd 2:0:0:0: [sdb] Add. Sense: Unrecovered read error
[12651.084817] end_request: I/O error, dev sdb, sector 6234672
[12720.192058] sd 2:0:0:0: [sdb] Unhandled sense code
[12720.192066] sd 2:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[12720.192072] sd 2:0:0:0: [sdb] Sense Key : Medium Error [current]
[12720.192078] sd 2:0:0:0: [sdb] Add. Sense: Unrecovered read error
[12720.192086] end_request: I/O error, dev sdb, sector 6392496
[12995.160191] sd 2:0:0:0: [sdb] Unhandled sense code
[12995.160198] sd 2:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[12995.160204] sd 2:0:0:0: [sdb] Sense Key : Medium Error [current]
[12995.160210] sd 2:0:0:0: [sdb] Add. Sense: Unrecovered read error
[12995.160218] end_request: I/O error, dev sdb, sector 6940536
[15095.895706] usb 1-1: USB disconnect, address 3
[15104.212932] ------------[ cut here ]------------
[15104.212958] WARNING: at /build/buildd/linux-2.6.31/fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x4f/0x80()
[15104.212968] Hardware name: M6N
--snip--

Revision history for this message
Malte Cornils (malte) wrote :

Forgot too add: not easily reproducible, no other ill effects, happened only once (so far) - I've tried using digikam in a similar way, but it did not crash again. I will report if it does in the future, though.

Changed in linux (Ubuntu):
status: Incomplete → In Progress
Revision history for this message
Erik Karlsson (pilo) wrote :

This might be the upstream bug: http://bugzilla.kernel.org/show_bug.cgi?id=14090

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.