Kernel Oops, maybe related to inotify on an NFS mount

[Steve McGrath]

Apport discovered a kernel oops after installing updates and rebooting. Kernel stuff is a little above me, but my rough analysis is that this was a problem with inotify on an NFS volume. I believe this because the oops mentions Rhythmbox, and my music folder is symlinked to an NFS mount.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: steve 2025 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd0340000 irq 22'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,10250000,00100002 HDA:11c13026,10250110,00100700'
   Controls : 26
   Simple ctrls : 16
Date: Wed Sep 23 11:07:39 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=446e16b1-471d-4074-92b5-5781d09769e9
MachineType: Acer, inc. Aspire 3680
Package: linux-image-2.6.31-10-generic 2.6.31-10.35
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=5b4cb4e3-be8a-4744-abd9-936a4cffdc9f ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-10-generic N/A
 linux-firmware 1.19
SourcePackage: linux
Tags: kernel-oops
Title: [151505.352953] ------------[ cut here ]------------
Uname: Linux 2.6.31-10-generic i686
WpaSupplicantLog:

dmi.bios.date: 04/10/07
dmi.bios.vendor: Acer
dmi.bios.version: v1.3505
dmi.board.name: Prespa1
dmi.board.vendor: Acer, Inc.
dmi.board.version: Not Applicable
dmi.chassis.type: 1
dmi.chassis.vendor: Acer, Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrv1.3505:bd04/10/07:svnAcer,inc.:pnAspire3680:pvrNotApplicable:rvnAcer,Inc.:rnPrespa1:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
dmi.product.name: Aspire 3680
dmi.product.version: Not Applicable
dmi.sys.vendor: Acer, inc.

[Leann Ogasawara (leannogasawara)]

Hi Steve,

Just curious if you can also comment on how often you see this kernel oops? From commit description which prints this warning, it notes:

" If an inotify watch is left in the idr when an fsnotify group is destroyed this will lead to a BUG. This is not a dangerous situation and really indicates a programming bug and leak of memory. This patch changes it to use a WARN and a printk rather than killing people's boxes."

[Steve McGrath (smcgrath23)]

So far this issue has not occurred again, though I don't think I've allowed
my laptop to suspend since then. I'll do some testing of suspend and resume
with and without NFS mounts and report results.

[Steve McGrath (smcgrath23)]

Ok, I cannot recreate this Oops again. I suspended and resumed my laptop a couple times, then did it again with my music share mounted via NFS and Rhythmbox running. I can only assume this was fixed with an update I installed. Or perhaps I had installed some major updates and not rebooted yet. I've no further ideas at this time.

[Steve McGrath (smcgrath23)]

Err... disregard the info about suspending and resuming, it seems I was getting mixed up with another Oops I reported. Having re-read my original report, I see that I got this one after a reboot. I've rebooted many times since, with NFS mounts and without. The issue does not reoccur.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Steve McGrath (smcgrath23)]

This problem hasn't occurred on my computer in quite some time now.

[Gabe Gorelick (gabegorelick)]

Looks like a duplicate of bug 442966, which is (supposedly) fixed, so that is probably why you no longer get this bug.