From owner-freebsd-bugs@freebsd.org Fri May 3 00:23:40 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE52315A5397 for ; Fri, 3 May 2019 00:23:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5066177C9A for ; Fri, 3 May 2019 00:23:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0D76E15A5396; Fri, 3 May 2019 00:23:39 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DF71115A5395 for ; Fri, 3 May 2019 00:23:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::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.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 739D477C97 for ; Fri, 3 May 2019 00:23:38 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 947EF7FA0 for ; Fri, 3 May 2019 00:23:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x430Nb1h094220 for ; Fri, 3 May 2019 00:23:37 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x430NbOm094212 for bugs@FreeBSD.org; Fri, 3 May 2019 00:23:37 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 237718] head -r346588 (and later) for powerpc64 on PowerMac G5 exposes: mtx_lock of spin mutex WWV @ .../sys/powerpc/aim/mmu_oea64.c Date: Fri, 03 May 2019 00:23:37 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new 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 Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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: Fri, 03 May 2019 00:23:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237718 Bug ID: 237718 Summary: head -r346588 (and later) for powerpc64 on PowerMac G5 exposes: mtx_lock of spin mutex WWV @ .../sys/powerpc/aim/mmu_oea64.c Product: Base System Version: CURRENT Hardware: powerpc OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: marklmi26-fbsd@yahoo.com head -r346588 accidentally added use of cmpb that is not supported on old PPC970's, such as on old PowerMac G5s. This turns out to provide a good test case for the handling of such invalid instruction encodings and it exposed a locking problem reported by the debug kernel. I used https://artifact.ci.freebsd.org/snapshot/head/r346589/powerpc/powerp= c64/ and some later ones in testing something else and ran into the issue below. (-r346588 was not present for powerpc64.) The below is from a later one: panic: mtx_lock of spin mutex WWV @ /mnt/usr/src/sys/powerpc/aim/mmu_oea64.c:2812 For reference, line 2812 is: PMAP_LOCK(pm); panic is reached via the following call chain, shown as part of a backtrace (typed from screen pictures): .__mtx_lock_flags+0xd4 .moea64_sync_icache+0x48 .pmap_sync_icache+0x90 .ppc_instr_emulate+0x1b4 .trap+0x10fc .powerpc_interrupt+0x2cc user PGM trap by 0x810053bb4: srr1=3D0x900000000008d032 r1=3D0x3ffffffffffffcc00 cr=3D0x20002024 xer=3D0 ctr=3D0x1 r2=3D0x81007bdd0 frame=3D0xe000000070ca9810 It was thread pid 28 tid 100097 Actually r346589 was at line :2811 and had the following differences: .ppc_intr_emulate+0x19c .trap+0x1004 frame=3D0xe000000070ca9848 I will note that -r346670 has notes on the lists for running into: mtx_lock of spin mutex(null) in .../kern/subr_bus.c:620 and being isolated by a bisect for being the first exposure in that context. This was not a powerpc64 context and may be completely unrelated. But folks seemed confused about how -r346670 might lead to such a panic. --=20 You are receiving this mail because: You are the assignee for the bug.=