Date: Thu, 20 Jul 2017 08:27:18 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 219399] System panics after several hours of 14-threads-compilation orgies using poudriere on AMD Ryzen... Message-ID: <bug-219399-8-ooF3r7T5XW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-219399-8@https.bugs.freebsd.org/bugzilla/> References: <bug-219399-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219399 --- Comment #75 from Nils Beyer <nbe@renzel.net> --- (In reply to Don Lewis from comment #71) Using the pin-to-core patch, the stress test doesn't use all cores any more= , so that the overall load is around 50%-60% only. With that I couldn't get any segfaults fast enough. FWIW, here's a GDB output of one of the core files: --------------------------------------------------------------------------- #gdb7121 ./ryzen_segv_test ryzen_segv_test.core GNU gdb (GDB) 7.12.1 [GDB v7.12.1 for FreeBSD] Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.htm= l> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-portbld-freebsd11.0". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./ryzen_segv_test...(no debugging symbols found)...don= e. [New LWP 100861] [New LWP 100711] [New LWP 100935] [New LWP 101000] Core was generated by `./ryzen_segv_test 2500000'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000000000400c06 in thread1 () [Current thread is 1 (LWP 100861)] (gdb) bt #0 0x0000000000400c06 in thread1 () #1 0x000000080082bbc5 in thread_start (curthread=3D0x801216500) at /usr/src/lib/libthr/thread/thr_create.c:289 #2 0x0000000000000000 in ?? () Backtrace stopped: Cannot access memory at address 0x7fffdfffe000 --------------------------------------------------------------------------- So the backtrace is corrupted and not usable, correct? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219399-8-ooF3r7T5XW>