From owner-freebsd-stable@freebsd.org  Tue Aug  9 20:09:57 2016
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@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 C957FBB4557
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Tue,  9 Aug 2016 20:09:57 +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 B8F8917F8
 for <freebsd-stable@FreeBSD.org>; Tue,  9 Aug 2016 20:09:57 +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 u79K9vMN073993
 for <freebsd-stable@FreeBSD.org>; Tue, 9 Aug 2016 20:09:57 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-stable@FreeBSD.org
Subject: [Bug 211491] System hangs after "Uptime" on reboot
Date: Tue, 09 Aug 2016 20:09:57 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-BETA3
X-Bugzilla-Keywords: needs-qa
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: vangyzen@freebsd.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: mfc-stable10? mfc-stable11?
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-211491-8075-9pc4RPxrCU@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211491-8075@https.bugs.freebsd.org/bugzilla/>
References: <bug-211491-8075@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-stable@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 20:09:57 -0000

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

--- Comment #7 from Eric van Gyzen <vangyzen@freebsd.org> ---
So far, I've been importing the volume using the iSCSI initiator in a bhyve
guest.  To determine whether iSCSI is really involved, I reconfigured to im=
port
the volume onto the bhyve host and pass it to the VM as a virtio block devi=
ce.=20
I failed to reproduce the hang.  (I'm still importing with altroot.)

Also, I have only reproduced the hang on systems with debugging kernel opti=
ons
such as INVARIANTS and WITNESS.  To determine whether they're really involv=
ed,
I'm rebuilding my VM's kernel without these options.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=