From owner-freebsd-bugs@FreeBSD.ORG Mon Oct 29 19:20: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 CCCB5C39 for ; Mon, 29 Oct 2012 19:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id B1DFF8FC0C for ; Mon, 29 Oct 2012 19:20: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 q9TJK1lO076320 for ; Mon, 29 Oct 2012 19:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q9TJK14e076319; Mon, 29 Oct 2012 19:20:01 GMT (envelope-from gnats) Date: Mon, 29 Oct 2012 19:20:01 GMT Message-Id: <201210291920.q9TJK14e076319@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Travis Mikalson 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: Travis Mikalson List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2012 19:20:01 -0000 The following reply was made to PR kern/172952; it has been noted by GNATS. From: Travis Mikalson To: bug-followup@FreeBSD.org, Andriy Gapon Cc: Subject: Re: kern/172952: 9.1 hangs on reboot after all buffers synced Date: Mon, 29 Oct 2012 15:17:03 -0400 After putting this pre-production system into its final configuration, (installing the base system to a compact flash) I have now been unable to reproduce this issue else I would have followed up earlier. 9.1-RC2 has soft rebooted successfully for me on this system without fail many times for days. This system is a ZFS storage server, but despite how much or how little I use ZFS, it is rebooting fine now. Andriy Gapon, I do still have one less convenient remote system left that consistently reproduces this issue. Can I get your WIP patch to try on that system to see if that system is experiencing the issue that you've been working on?