From owner-freebsd-bugs@freebsd.org Tue Aug 22 17:52:36 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 20501DD826D for ; Tue, 22 Aug 2017 17:52:36 +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 045876DF63 for ; Tue, 22 Aug 2017 17:52:36 +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 v7MHqZ5c014642 for ; Tue, 22 Aug 2017 17:52:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 221029] AMD Ryzen: strange compilation failures using poudriere or plain buildkernel/buildworld Date: Tue, 22 Aug 2017 17:52:36 +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.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: markmi@dsl-only.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: Tue, 22 Aug 2017 17:52:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221029 --- Comment #91 from Mark Millard --- My first ever compelted attempt at anything like: pousriere bulk -w -a finished. (It started from a prior interrupted attempt from a prior boot so some things had already built and the prior failures were retried.) It reported "62 FAIL" overall, most for source code rejections based on a preliminary look. Few Signals. But when I went to look at dmesg -a there were lots of Signals there: FBSDx6411SL# dmesg -a | grep "^pid" | cut -d " " -f 3-100 | sort | uniq -c | less 1 (a.out), uid 0: exited on signal 11 (core dumped) 1 (bash), uid 0: exited on signal 11 (core dumped) 3 (cc), uid 0: exited on signal 11 (core dumped) 1 (clang), uid 0: exited on signal 11 (core dumped) 1 (cm3), uid 0: exited on signal 6 (core dumped) 1 (conftest) is attempting to use unsafe AIO requests - not logging anym= ore 1 (conftest), uid 0: exited on signal 10 (core dumped) 4 (conftest), uid 0: exited on signal 11 (core dumped) 4 (conftest), uid 0: exited on signal 6 (core dumped) 76 (fc-cache), uid 0: exited on signal 11 (core dumped) 4 (gcc), uid 0: exited on signal 11 (core dumped) 17 (gdk-pixbuf-query-lo), uid 0: exited on signal 11 (core dumped) 121 (gio-querymodules-64), uid 0: exited on signal 11 (core dumped) 1 (go), uid 0: exited on signal 5 (core dumped) 16 (gtk-query-immodules), uid 0: exited on signal 11 (core dumped) 1 (nm), uid 0: exited on signal 6 (core dumped) 17 (pango-querymodules-), uid 0: exited on signal 11 (core dumped) 24 (pctest), uid 0: exited on signal 11 (core dumped) 24 (pdtest), uid 0: exited on signal 11 (core dumped) 24 (pstest), uid 0: exited on signal 11 (core dumped) 24 (pztest), uid 0: exited on signal 11 (core dumped) 2 (readonly.exe), uid 0: exited on signal 11 1 (scm), uid 0: exited on signal 11 (core dumped) 1 (test_26349), uid 0: exited on signal 4 (core dumped) 15 (try), uid 0: exited on signal 11 How much of the Signal activity is abnormal I do not know. These are all from the kern.sched.steal_idle=3D0 type of test context. Some other odd items in FreeBSD's demsg -a output were: interrupt storm detected on "irq19:"; throttling interrupt source Failed to fully fault in a core file segment at VA 0x800641000 with size 0x= 1000 to be written at offset 0x25000 for process conftest Failed to fully fault in a core file segment at VA 0x800643000 with size 0x= 1000 to be written at offset 0x25000 for process a.out FYI: systat -vmstat indicates "le0" for irq19. --=20 You are receiving this mail because: You are the assignee for the bug.=