From owner-freebsd-bugs@freebsd.org Fri Jul 14 13:24:01 2017 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0519EDA1AD4 for ; Fri, 14 Jul 2017 13:24:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DAEC9658E6 for ; Fri, 14 Jul 2017 13:24:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v6EDO0bt041977 for ; Fri, 14 Jul 2017 13:24:00 GMT (envelope-from bugzilla-noreply@freebsd.org) 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... Date: Fri, 14 Jul 2017 13:24:00 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: nbe@renzel.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2017 13:24:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219399 --- Comment #67 from Nils Beyer --- Perhaps interesting to you - here is another Ryzen stress test: https://github.com/hayamdk/ryzen_segv_test I had to patch it with: ----------------------------- SNIP ------------------------------------- diff --git a/ryzen_segv_test.c b/ryzen_segv_test.c index 8d64215..74d8530 100644 --- a/ryzen_segv_test.c +++ b/ryzen_segv_test.c @@ -323,11 +323,6 @@ int main(int argc, const char *argv[]) { int64_t loops; pthread_t t1, t2, t3; -#ifdef _MSC_VER -#else - cpu_set_t cpuset; - int cpu; -#endif pid_t pid =3D getpid(); if(argc > 1) { @@ -352,15 +347,6 @@ int main(int argc, const char *argv[]) pthread_create(&t2, NULL, (void*)threadx, (void*)1); pthread_create(&t3, NULL, (void*)threadx, NULL); -#ifdef _MSC_VER -#else - cpu =3D random() % n_cpus; - CPU_ZERO(&cpuset); - CPU_SET(cpu, &cpuset); - sched_setaffinity(pid, sizeof(cpu_set_t), &cpuset); - fprintf(stderr, "PID:%d CPU:%d\n", (int)pid, cpu); -#endif -=20=20=20=20=20=20=20 pthread_join(t1, NULL); pthread_join(t2, NULL); pthread_join(t3, NULL); ----------------------------- SNIP ------------------------------------- compiled it and executed: ./run.sh 16 2500000 It generates segmentation faults rather quickly (< 1 min). As a side note: on my Intel E3-1220v3 system there are no segfaults at all (using the same command line)... --=20 You are receiving this mail because: You are the assignee for the bug.=