From owner-freebsd-stable@FreeBSD.ORG Sat Nov 29 12:27:29 2014 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B5F7B602 for ; Sat, 29 Nov 2014 12:27:29 +0000 (UTC) Received: from tau.lfms.nl (tau.lfms.nl [93.189.130.30]) (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 779C5AE for ; Sat, 29 Nov 2014 12:27:28 +0000 (UTC) Received: from sim.dt.lfms.nl (dt.lfms.nl [83.84.86.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by tau.lfms.nl (Postfix) with ESMTPS id 1D8B889283 for ; Sat, 29 Nov 2014 13:17:36 +0100 (CET) Received: from [192.168.130.112] (borax.dt.lfms.nl [192.168.130.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sim.dt.lfms.nl (Postfix) with ESMTPS id D20DA9C09084 for ; Sat, 29 Nov 2014 13:17:35 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: System hang on shutdown when running freebsd-update From: Walter Hop In-Reply-To: <2B4EEDA7-C3D9-465A-B0C9-B5728D438077@spam.lifeforms.nl> Date: Sat, 29 Nov 2014 13:17:35 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <5B600B90-9967-4031-AB9B-40ADDBE56CAF@spam.lifeforms.nl> References: <2B4EEDA7-C3D9-465A-B0C9-B5728D438077@spam.lifeforms.nl> To: freebsd-stable@FreeBSD.org X-Mailer: Apple Mail (2.1993) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Nov 2014 12:27:29 -0000 I=E2=80=99m revisiting this issue, since unfortunately I still have it = more often than not when upgrading to 10.1-RELEASE. As Kevin Oberman suspected earlier in the thread, the issue seems to lie = in unmounting. The same hang occurs when dropping to single user mode = and trying to re-mount root as readonly. I=E2=80=99ve also had another unmount issue after upgrading to = 10.1-RELEASE: All buffers synced. softdep_waitidle: Failed to flush worklist for 0xfffff800027b4330 unmount of / failed (BUSY) I=E2=80=99ve created a PR with the information I have: = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D195458 With the EOL date of FreeBSD 10.0 on the horizon, it=E2=80=99s making me = a little skittish. Any ideas of experiments I can do to get more info out of a problematic = box, or other options to take? Thanks! WH > On 28 Oct 2014, at 23:09, Walter Hop = wrote: >=20 > I noticed this same hang after upgrading from 10.0-RELEASE to 10.1-RC3 = in a VM running under VMware Fusion, so the problem appears still = present. >=20 > I could only make it happen in the single uptime just after the system = was freebsd-updated from FreeBSD 10.0 to 10.1-RC3. >=20 > Here is a screenshot: http://lf.ms/wait-for-reboot.png >=20 > It did not make any progress after 2 hours of waiting. When restarting = the VM, the disk was dirty. >=20 > Some interesting facts: > - Note "swapoff: /dev/da0p2: Cannot allocate memory" in the screenshot = which might pose a clue. I haven=E2=80=99t seen this normally. > - FreeBSD does respond to ping while it is busy, so it is not a = complete "freeze". > - The VM is at 100% CPU while this is going on. --=20 Walter Hop | PGP key: https://lifeforms.nl/pgp