From owner-freebsd-stable@FreeBSD.ORG Tue Oct 28 22:09:17 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 262E07A3 for ; Tue, 28 Oct 2014 22:09:17 +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 B7A60E17 for ; Tue, 28 Oct 2014 22:09:16 +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 A753D89299 for ; Tue, 28 Oct 2014 23:09:12 +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 7DDF29C09084 for ; Tue, 28 Oct 2014 23:09:12 +0100 (CET) From: Walter Hop Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: System hang on shutdown when running freebsd-update Message-Id: <2B4EEDA7-C3D9-465A-B0C9-B5728D438077@spam.lifeforms.nl> Date: Tue, 28 Oct 2014 23:09:12 +0100 To: freebsd-stable@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) X-Mailer: Apple Mail (2.1990.1) 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: Tue, 28 Oct 2014 22:09:17 -0000 [Apologies for not replying directly to the thread; I found it at = https://lists.freebsd.org/pipermail/freebsd-stable/2014-October/080595.htm= l ] 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. 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. Here is a screenshot: http://lf.ms/wait-for-reboot.png It did not make any progress after 2 hours of waiting. When restarting = the VM, the disk was dirty. 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. I have created a snapshot of the VM in the failed state, so maybe some = useful information could be retrieved from it, although I don=E2=80=99t = have any experience with kernel debugging over VMware. Cheers, WH --=20 Walter Hop | PGP key: https://lifeforms.nl/pgp