https://bugzilla.novell.com/show_bug.cgi?id=664105 https://bugzilla.novell.com/show_bug.cgi?id=664105#c2 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |richard.coe@med.ge.com, | |youquan.song@intel.com Summary|Kernel segfault in |Kernel segfault in |kernel/timer.c - comm: |kernel/timer.c - comm: |stapio (process) - may be |stapio (process) - related |related to preloadtrace.ko |to preloadtrace.ko --- Comment #2 from Thomas Renninger 2011-01-13 09:31:16 UTC --- Moving away preloadtrace.ko driver so that it does not get loaded works around the issue. There seem to be at least two machines affected: - HP Z600, a workstation (compare with bug #647029) - Boxboro-EX, a huge server both have Intel Nehalem CPUs. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=664105 https://bugzilla.novell.com/show_bug.cgi?id=664105#c4 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bjorn.helgaas@hp.com --- Comment #4 from Thomas Renninger 2011-01-14 11:07:48 UTC --- Thanks for the pointer Coolo. This sounds rather sane: commit 3fd1c490 switches to atomic_t flags to the timer callback functions to defeat mod_timer() calls that might overlap a del_timer_sync. commit f2b610b does likewise for the transport layer timers. And would explain that the race, triggered by the preloadtrace driver is only triggered on latest/fastest Nehalem machines. The problem is: which git tree are the commit ids referring to, it's not the Linus or x86/tip tree. I'll ask the guy and report back. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=664105 https://bugzilla.novell.com/show_bug.cgi?id=664105#c6 --- Comment #6 from Tony Jones 2011-01-14 18:36:09 UTC --- (In reply to comment #5)

I added the mentioned systemtap git commits from: http://sourceware.org/bugzilla/show_bug.cgi?id=10651 to the our systemtap devel:tools repo and did a submitrequest against openSUSE:Factory. Afaik, it's not verified whether these fix the issue.

Tony: I also cannot judge these patches at all, as they are in the mainline systemtap git I just added them, hope that's fine.

I'd rather you not do this in the future, especially if you "cannot judge the patches". The process I believe is, you branch devel:tools/systemtap, make a change and submit them as a change request back to devel:tools/systemtap Also, next time can you add me as a cc: to the bug before it's closed ;-) I'm confused as I just got this auto e-mail: Subject: [ci_new_pac] JFYI systemtap -> stable Package is "systemtap", Maintainer is "trenn@novell.com" -- 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.