From owner-freebsd-bugs@freebsd.org Mon Aug 12 11:38:30 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 438BBB0256 for ; Mon, 12 Aug 2019 11:38:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 466Ykt15bqz4F70 for ; Mon, 12 Aug 2019 11:38:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 239C8B0254; Mon, 12 Aug 2019 11:38:30 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 235BAB0253 for ; Mon, 12 Aug 2019 11:38:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 466Ykt080Fz4F6w for ; Mon, 12 Aug 2019 11:38:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id DC6E825F7D for ; Mon, 12 Aug 2019 11:38:29 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x7CBcTC5005887 for ; Mon, 12 Aug 2019 11:38:29 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x7CBcTgW005886 for bugs@FreeBSD.org; Mon, 12 Aug 2019 11:38:29 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 239245] r350074 will panic on ppc64 PowerMac G5 in vm_phys_enqueue_contig Date: Mon, 12 Aug 2019 11:38:29 +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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: alfredo.junior@eldorado.org.br X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Aug 2019 11:38:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D239245 Alfredo Dal'Ava J=C3=BAnior changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luporl@FreeBSD.org --- Comment #59 from Alfredo Dal'Ava J=C3=BAnior --- I can reproduce similar issue (same stack on panic) on QEMU using the follo= wing steps: 1 - take a clean-installed FreeBSD 12 RELEASE 2 - get src at r350672; 3 - buildkernel 4 - installkernel 5 - shutdown -r now It's not reproduced all the times, reproduce rate is bellow 20%. Looking at= my continuous integration logs, I see this panic first appearing on early June. For the record: - commenting out NUMA option on kernel config file will workaround it. - NUMA feature was introduced/made default in early April, two months before the first time my testbed hit the issue for the first time. So it doesn't appear like a bug in the original code. Something between April and June has changed it, or maybe triggered it. - Once panics, QEMU system_reset will hit the panic again. Closing QEMU and starting it again will make it boot. (power cycle?) - Once the panic, if I do QEMU system_reset and make loader boot the old (FreeBSD 12) kernel, it works fine. If I issue reboot and load the new kern= el (that was just built), the panic is hit again. (something like a bad persis= tent state affecting only the new kernel, that only disappears after closing QEM= U). --=20 You are receiving this mail because: You are the assignee for the bug.=