From owner-freebsd-bugs@FreeBSD.ORG  Thu Mar 12 01:52:41 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 9AE74A92
 for <freebsd-bugs@FreeBSD.org>; Thu, 12 Mar 2015 01:52:41 +0000 (UTC)
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 8131BF2C
 for <freebsd-bugs@FreeBSD.org>; Thu, 12 Mar 2015 01:52:41 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t2C1qfx9028137
 for <freebsd-bugs@FreeBSD.org>; Thu, 12 Mar 2015 01:52:41 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 195458] Hang on shutdown/root unmount after FreeBSD 10.1R upgrade
Date: Thu, 12 Mar 2015 01:52:38 +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: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: gjb@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-195458-8-lf5PQ4frRC@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195458-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-195458-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Mar 2015 01:52:41 -0000

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

--- Comment #65 from Glen Barber <gjb@FreeBSD.org> ---
(In reply to Glen Barber from comment #59)
> (In reply to Glen Barber from comment #55)
> > The test machine now has INVARIANTS, INVARIANT_SUPPORT, WITNESS,
> > DEBUG_LOCKS, DEBUG_VFS_LOCKS, DIAGNOSTIC, and ALT_BREAK_TO_DEBUGGER. 
> > Unfortunately, it panics on boot now, so I cannot proceed to the
> > 'freebsd-update install; reboot' phase.
> > [...]
> > It looks like I will need to remove DIAGNOSTIC to get the system to boot.
> 
> It seems removing DIAGNOSTIC alone was not enough, since now the test
> machine panics on boot.

Just a note:

This particular issue (panic-on-boot with DIAGNOSTIC) will need to be
reinvestigated after the original issue discussed in this PR is identified and
resolved, as right now it is difficult to tell if this is an effect of a larger
issue.

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