From owner-freebsd-bugs@freebsd.org  Sun Sep 17 03:01:15 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
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 50DCDE1DA93
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sun, 17 Sep 2017 03:01:15 +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 3CE3E6E9C0
 for <freebsd-bugs@FreeBSD.org>; Sun, 17 Sep 2017 03:01:15 +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 v8H31FuA074184
 for <freebsd-bugs@FreeBSD.org>; Sun, 17 Sep 2017 03:01:15 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 222234] head -r323246 aarch64 (Pine64+ 2GB) boot time context,
 sometimes: acquiring blockable sleep lock with spinlock or critical section
 held
Date: Sun, 17 Sep 2017 03:01:15 +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 Only Me
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: attachments.created
Message-ID: <bug-222234-8-yS1kmHJ8RI@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-222234-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-222234-8@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Sep 2017 03:01:15 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222234

--- Comment #2 from Mark Millard <markmi@dsl-only.net> ---
Created attachment 186443
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D186443&action=
=3Dedit
patch to allow non-debug kernel booting

The patch contents derives from running into
ARMv8-A material that said:

ARM recommends that software includes a DSB instruction before any SEV
instruction.

This was because of a lack of ordering relative
to completion of memory access instructions
prior to the SEV instruction.

This does not appear to be architecturally
specific to the A64: the quote is not from
material about the A64.

But the observation is that A64 does not
seem to guarantee more. I'm not aware of
reports for other contexts.

I'll note that debug kernel builds (with at
least invariants) tends to sometimes fail
but usually boot. By contrast I've not had
a non-debug kernel boot yet.

--=20
You are receiving this mail because:
You are the assignee for the bug.=