[Bug 235818] New: Kernel Bug in kernel-default-2.6.18.2-34 on x86-64 SMP machine
https://bugzilla.novell.com/show_bug.cgi?id=235818 Summary: Kernel Bug in kernel-default-2.6.18.2-34 on x86-64 SMP machine Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: asvetter@cip.physik.uni-wuerzburg.de QAContact: qa@suse.de Kernel Bug in kernel-default-2.6.18.2-34 on x86-64 SMP machine: Jan 12 16:13:55 wpyc009 kernel: BUG: warning at fs/inotify.c:171/set_dentry_child_flags() Jan 12 16:13:55 wpyc009 kernel: Jan 12 16:13:55 wpyc009 kernel: Call Trace: Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802d54dc>] set_dentry_child_flags+0x66/0x132 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802d560f>] remove_watch_no_event+0x67/0x76 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802d5a7d>] inotify_destroy+0x92/0xbf Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802d5b9a>] inotify_release+0x1a/0x73 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80210559>] __fput+0xae/0x182 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80221b2a>] filp_close+0x5c/0x64 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80236bdd>] put_files_struct+0x6c/0xc3 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802131c3>] do_exit+0x2b0/0x8fc Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802450b9>] cpuset_exit+0x0/0x6c Jan 12 16:13:55 wpyc009 kernel: [<ffffffff802295f6>] get_signal_to_deliver+0x46e/0x49d Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80227fdd>] do_signal+0x55/0x74a Jan 12 16:13:55 wpyc009 kernel: [<ffffffff8025c8e8>] thread_return+0x0/0xef Jan 12 16:13:55 wpyc009 kernel: [<ffffffff8029463d>] __remove_hrtimer+0x27/0x39 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80255f03>] hrtimer_cancel+0xc/0x16 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff8025d736>] do_nanosleep+0x47/0x70 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80255df0>] hrtimer_nanosleep+0x58/0x118 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80226034>] do_wait+0x9c1/0xa44 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80294821>] hrtimer_wakeup+0x0/0x22 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff80258097>] sysret_signal+0x1c/0x27 Jan 12 16:13:55 wpyc009 kernel: [<ffffffff8025831b>] ptregscall_common+0x67/0xac Jan 12 16:13:55 wpyc009 kernel: -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 ------- Comment #1 from asvetter@cip.physik.uni-wuerzburg.de 2007-01-17 08:53 MST ------- Created an attachment (id=113411) --> (https://bugzilla.novell.com/attachment.cgi?id=113411&action=view) hwinfo -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |asvetter@cip.physik.uni-wuerzburg.de ------- Comment #2 from gregkh@novell.com 2007-01-17 10:48 MST ------- This is just a "warning" that something bad might have happened, the kernel caught it and continued on. Did the system continue to work just fine, or did other things go wrong? Is it easy to trigger this warning? what were you doing at the time? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 asvetter@cip.physik.uni-wuerzburg.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|asvetter@cip.physik.uni- | |wuerzburg.de | ------- Comment #3 from asvetter@cip.physik.uni-wuerzburg.de 2007-01-18 02:05 MST ------- The machine works fine after that. I have no idea how to trigger it, since this is a machine in a pool for students and acct was not started by accident. The entry just before the bug is: Jan 12 16:13:53 wpyc009 sshd[23810]: Accepted publickey for ferfurth from 132.187.42.39 port 59835 ssh2 Since this seems to be filesystem dependent: The machine has / and /tmp on a reiserfs. Nobody can insert floppies, CDs, USB devices. It has /home and /usr/local on NFS, sometimes the NFS server responds very slowly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 ------- Comment #4 from asvetter@cip.physik.uni-wuerzburg.de 2007-01-19 08:56 MST ------- Hmm, we have several machines (same hardware) that freeze, when the X-server is killed with CTRL-ALT-Backspace. We have to powercycle them. Unfortunately, it is not reproducible. I hope the new Xorg update helps for this issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |asvetter@cip.physik.uni-wuerzburg.de ------- Comment #5 from gregkh@novell.com 2007-01-19 17:40 MST ------- Can you provide the output of 'hwinfo' attached to this bug? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 asvetter@cip.physik.uni-wuerzburg.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|asvetter@cip.physik.uni- | |wuerzburg.de | ------- Comment #6 from asvetter@cip.physik.uni-wuerzburg.de 2007-01-21 07:41 MST ------- (In reply to comment #1)
Created an attachment (id=113411) --> (https://bugzilla.novell.com/attachment.cgi?id=113411&action=view) [edit] hwinfo
already done -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 lmb@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |asvetter@cip.physik.uni-wuerzburg.de ------- Comment #7 from lmb@novell.com 2007-01-23 03:38 MST ------- Does the new Xorg update help as you hope in comment #4? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 asvetter@cip.physik.uni-wuerzburg.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|asvetter@cip.physik.uni- | |wuerzburg.de | ------- Comment #8 from asvetter@cip.physik.uni-wuerzburg.de 2007-01-23 05:08 MST ------- Looks good until now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 lmb@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Comment #9 from lmb@novell.com 2007-01-23 05:48 MST ------- Perfect! ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 asvetter@cip.physik.uni-wuerzburg.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Comment #10 from asvetter@cip.physik.uni-wuerzburg.de 2007-01-23 07:01 MST ------- Too early :-( One of the machines was completely frozen again. Nothing in the logs. User says they tried bzflag, and then it was frozen. Unfortunately I can't find it with "lastcomm". Obviously "lastcomm" only logs finished commands. How can I log all commands? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 ------- Comment #11 from asvetter@cip.physik.uni-wuerzburg.de 2007-02-05 06:06 MST ------- Different machine, similar Bug: Feb 1 10:24:29 wpyc007 kernel: BUG: warning at fs/inotify.c:171/set_dentry_child_flags() Feb 1 10:24:29 wpyc007 kernel: Feb 1 10:24:29 wpyc007 kernel: Call Trace: Feb 1 10:24:29 wpyc007 kernel: [<ffffffff802d54dc>] set_dentry_child_flags+0x66/0x132 Feb 1 10:24:29 wpyc007 kernel: [<ffffffff802d560f>] remove_watch_no_event+0x67/0x76 Feb 1 10:24:29 wpyc007 kernel: [<ffffffff88072fdd>] :reiserfs:reiserfs_delete_inode+0x0/0xf6 Feb 1 10:24:29 wpyc007 kernel: [<ffffffff802d5a7d>] inotify_destroy+0x92/0xbf Feb 1 10:24:29 wpyc007 kernel: [<ffffffff802d5b9a>] inotify_release+0x1a/0x73 Feb 1 10:24:29 wpyc007 kernel: [<ffffffff80210559>] __fput+0xae/0x182 Feb 1 10:24:29 wpyc007 kernel: [<ffffffff80221b2a>] filp_close+0x5c/0x64 Feb 1 10:24:29 wpyc007 kernel: [<ffffffff80236bdd>] put_files_struct+0x6c/0xc3 Feb 1 10:24:29 wpyc007 kernel: [<ffffffff802131c3>] do_exit+0x2b0/0x8fc Feb 1 10:24:29 wpyc007 kernel: [<ffffffff802450b9>] cpuset_exit+0x0/0x6c Feb 1 10:24:29 wpyc007 kernel: [<ffffffff802295f6>] get_signal_to_deliver+0x46e/0x49d Feb 1 10:24:29 wpyc007 kernel: [<ffffffff80227fdd>] do_signal+0x55/0x74a Feb 1 10:24:29 wpyc007 kernel: [<ffffffff80229cab>] sys_recvfrom+0x11d/0x137 Feb 1 10:24:29 wpyc007 kernel: [<ffffffff80258097>] sysret_signal+0x1c/0x27 Feb 1 10:24:29 wpyc007 kernel: [<ffffffff8025831b>] ptregscall_common+0x67/0xac Feb 1 10:24:29 wpyc007 kernel: -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 ------- Comment #12 from asvetter@cip.physik.uni-wuerzburg.de 2007-02-05 06:09 MST ------- Machine from comment #11 is still working correctly without reboot. Maybe the lockups and this bug are two different things. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 jack@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jack@novell.com |npiggin@novell.com ------- Comment #14 from jack@novell.com 2007-02-08 02:07 MST ------- I've been investigating the inotify problem - actually, it does not seem to be rare (I've found several bugreports with the similar warning). But no one else complains about the hang - so that one is probably unrelated. I'm reassigning to Nick who is trying to track down the inotify problem in the mainline. He may be glad for further debugging input ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818 npiggin@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #15 from npiggin@novell.com 2007-02-20 08:50 MST ------- Sorry, still working on this in the upstream kernel. Andreas: I'm pretty sure it is harmless. Actually the flag is only used to indicate whether there is an inotify watch on the parent directory without taking a lock. The warning just means we've found the flag set when it should not have been, so we'll just have been doing a bit of extra locking in that case. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=235818#c16
John McManaman
https://bugzilla.novell.com/show_bug.cgi?id=235818#c17
--- Comment #17 from Jan Kara
https://bugzilla.novell.com/show_bug.cgi?id=235818#c18
Jan Kara
https://bugzilla.novell.com/show_bug.cgi?id=235818#c19
--- Comment #19 from Nick Piggin
https://bugzilla.novell.com/show_bug.cgi?id=235818
User jeffm@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235818#c20
--- Comment #20 from Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=235818
User npiggin@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235818#c21
--- Comment #21 from Nick Piggin
https://bugzilla.novell.com/show_bug.cgi?id=235818
User aj@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235818#c22
--- Comment #22 from Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=235818
User npiggin@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=235818#c23
Nick Piggin
participants (1)
-
bugzilla_noreply＠novell.com