From owner-freebsd-stable@FreeBSD.ORG Wed Oct 29 03:21:10 2014 Return-Path: Delivered-To: freebsd-stable@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 662D9EA1 for ; Wed, 29 Oct 2014 03:21:10 +0000 (UTC) Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 29783215 for ; Wed, 29 Oct 2014 03:21:10 +0000 (UTC) Received: by mail-ie0-f178.google.com with SMTP id rl12so2180129iec.9 for ; Tue, 28 Oct 2014 20:21:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ZBJndOMGYP3EJg5XgTy6Sgu8zPu9Ncl/a3K+9Wdxp4o=; b=n+rF9c42QHTMcoNEyE41GueeVlWIpvODMjUY6V/QsMqFV75OlAEgb+AHK8S4XuhpQM hp4kxUcp5MhJBkzuy1bdQXjwdqAENjCf/ALPhk91cj814osk7uEcvQ6pvLfOe3/CEZfe wFnedZ27DA5nv2wQeNLz3Q2FiXgXxZaNg/AL33GtkvAECfYMV+mQ+IQ0wchceNQax3dr esKRR0tQFkO6OgRYgJkd9U+syv0TjTOk/Ijmq15XWTIZ3brpxGahvie1JO+dniTpOLyh HuQO73Ww43Tb2LKaUAKzEWM36b8Z6q4r+hH/pB4G0wirN04J3D6pjijRo/ML/15467RU pBTQ== MIME-Version: 1.0 X-Received: by 10.50.50.2 with SMTP id y2mr16601287ign.1.1414552868944; Tue, 28 Oct 2014 20:21:08 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.11.152 with HTTP; Tue, 28 Oct 2014 20:21:08 -0700 (PDT) In-Reply-To: <2B4EEDA7-C3D9-465A-B0C9-B5728D438077@spam.lifeforms.nl> References: <2B4EEDA7-C3D9-465A-B0C9-B5728D438077@spam.lifeforms.nl> Date: Tue, 28 Oct 2014 20:21:08 -0700 X-Google-Sender-Auth: mODA1C69_Fz1z773ExziVt83w2E Message-ID: Subject: Re: System hang on shutdown when running freebsd-update From: Kevin Oberman To: Walter Hop Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD-STABLE Mailing List 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: Wed, 29 Oct 2014 03:21:10 -0000 On Tue, Oct 28, 2014 at 3:09 PM, Walter Hop wrote: > [Apologies for not replying directly to the thread; I found it at > https://lists.freebsd.org/pipermail/freebsd-stable/2014-October/080595.ht= ml > ] > > 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 wa= s > 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 th= e > 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 h= ave any > experience with kernel debugging over VMware. > > Cheers, > WH > > -- > Walter Hop | PGP key: https://lifeforms.nl/pgp > > I am starting to suspect that some code that is needed to flush a resourc= e that is blocking the complete shutdown is no longer available so waiting is not going to work. I tried a simple "shutdown now" and waited in single user mode for a minute before "reboot". It worked fine. This is based on guesswork, but seems to fit the symptoms. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com