https://bugzilla.novell.com/show_bug.cgi?id=831629 https://bugzilla.novell.com/show_bug.cgi?id=831629#c FeiXiang Zhang changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |jmatejek@suse.com |ovo.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.

https://bugzilla.novell.com/show_bug.cgi?id=831629 https://bugzilla.novell.com/show_bug.cgi?id=831629#c2 --- Comment #2 from Dinar Valeev 2013-08-06 08:43:20 UTC --- Created an attachment (id=551340) --> (http://bugzilla.novell.com/attachment.cgi?id=551340) reproducer This reproducer segfaults on 3.10 defconfig -- 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=831629 https://bugzilla.novell.com/show_bug.cgi?id=831629#c4 --- Comment #4 from Dinar Valeev 2013-08-07 08:42:43 UTC --- bad guess. with Fedora's 3.10.5 test passes. 3.11rc4 fails too with opensuse's config -- 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=831629 https://bugzilla.novell.com/show_bug.cgi?id=831629#c6 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@suse.com --- Comment #6 from Jeff Mahoney 2013-08-07 13:06:17 EDT --- Can you reproduce it with CONFIG_RCU_USER_QS=n? -- 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=831629 https://bugzilla.novell.com/show_bug.cgi?id=831629#c8 --- Comment #8 from Jeff Mahoney 2013-08-08 15:26:41 EDT --- Hrm, then I suspect CONFIG_HAVE_CONTEXT_TRACKING is unrelated to the issue. RCU_USER_QS depends on it, and is now disabled. VIRT_CPU_ACCOUNTING_GEN depends on it, and was already disabled. NO_HZ_FULL depends on it and was already disabled. But now I realize that's probably what you meant 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.

https://bugzilla.novell.com/show_bug.cgi?id=831629 https://bugzilla.novell.com/show_bug.cgi?id=831629#c11 Jeff Mahoney changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |dvaleev@suse.com --- Comment #11 from Jeff Mahoney 2013-08-09 01:24:24 EDT --- It looks like python itself is crashing: python[25204]: unhandled signal 11 at e92100a0e9010140 nip 00001fffffdf2838 lr 00001fffffdbd2d0 code 30001 and since it's a case for which we're testing signal handling, it's seeing it as a failed signal 11 test, which is SIGSEGV. The test is using SIGUSR1. I'd like to see the cause of the python crash before further diagnosing this as a kernel 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.

https://bugzilla.novell.com/show_bug.cgi?id=831629 https://bugzilla.novell.com/show_bug.cgi?id=831629#c13 --- Comment #13 from Dinar Valeev 2013-08-15 18:59:29 UTC --- I just hit another, similar issue like this. ghc enters a loop. I suspect the root of the issue is the same. http://ghc.haskell.org/trac/ghc/ticket/8134 -- 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=831629 https://bugzilla.novell.com/show_bug.cgi?id=831629#c15 --- Comment #15 from Jan Matejek 2013-10-03 18:01:31 UTC --- python's memory gets corrupted somehow in this test. So far I was unable to track down what exactly happens, but valgrind reports that python starts to step over unitialized memory in its finalizer, and that crashes it in the end. (btw, Don't Try This At Home, you need to have a special build of python to get meaningful results from valgrind [1]) The problematic sequence is this: 1. install a signal handler for SIGUSR1 2. install a different signal handler for SIGUSR1, storing the original one for later use 3. when you get SIGUSR1, restore the original signal handler with `sigaction` and call it with `raise` (that is pretty much the only thing that the override handler needs to do to trigger the problem - i commented out everything but this restore and it still segfaulted.) The original signal handler is executed correctly, AFAICT, and so far I did not find any difference between its behavior in the crashing and non-crashing case. (if you have any good tips on doing "core diffs", i could use some) But something obviously ends up different ;) if you guys have any idea what could be different between this kernel and the previous one regarding these operations, i'd love to hear it. [1] http://svn.python.org/projects/python/trunk/Misc/README.valgrind -- 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=831629 https://bugzilla.novell.com/show_bug.cgi?id=831629#c Ihno Krumreich changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=831629 http://bugzilla.novell.com/show_bug.cgi?id=831629#c17 Jan Matejek changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #17 from Jan Matejek --- no reaction for several years and IIRC python testsuite now passes just fine on ppc64, so closing. -- You are receiving this mail because: You are on the CC list for the bug.