From owner-freebsd-bugs@FreeBSD.ORG Tue Oct 23 18:50:01 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 95AAE876 for ; Tue, 23 Oct 2012 18:50:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.FreeBSD.org [8.8.178.135]) by mx1.freebsd.org (Postfix) with ESMTP id 7DC368FC08 for ; Tue, 23 Oct 2012 18:50:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q9NIo1l3015559 for ; Tue, 23 Oct 2012 18:50:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q9NIo1vG015558; Tue, 23 Oct 2012 18:50:01 GMT (envelope-from gnats) Date: Tue, 23 Oct 2012 18:50:01 GMT Message-Id: <201210231850.q9NIo1vG015558@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Per olof Ljungmark Subject: Re: kern/172952: 9.1 hangs on reboot after all buffers synced X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Per olof Ljungmark List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Oct 2012 18:50:01 -0000 The following reply was made to PR kern/172952; it has been noted by GNATS. From: Per olof Ljungmark To: bug-followup@FreeBSD.org, bofh@terranova.net Cc: Subject: Re: kern/172952: 9.1 hangs on reboot after all buffers synced Date: Tue, 23 Oct 2012 20:48:00 +0200 Identical behavior found on the following hardware, all HP: DL360 G4 DL360 G5 XW6400 XW6600 All with 9-STABLE and ZFS-only filesystems and only after rebuilding system from source. For example, we have two 360 G4 installed 9th. of October, both were able to reboot after install. Rebuilt one two days ago and now it cannot reboot properly except when you issue a "shutdown -n -o -r now". Tried hw.usb.no_shutdown_wait=1 and hw.acpi.handle_reboot=1 no change. I think "Severity: non-critical" should be changed to critical because this could potentially get you into big trouble when you try to reboot a remote machine.