From owner-freebsd-stable@FreeBSD.ORG Tue Oct 14 18:53:13 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 D6C58FD6 for ; Tue, 14 Oct 2014 18:53:13 +0000 (UTC) Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (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 A25C576D for ; Tue, 14 Oct 2014 18:53:13 +0000 (UTC) Received: by mail-ig0-f177.google.com with SMTP id a13so15862178igq.10 for ; Tue, 14 Oct 2014 11:53:13 -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=7HzjvJTjE6LX6+W3i6PMPmLnMzL7ZM4IOjVyNx2jb0E=; b=M08yV0m33kAjEWFOgRWutd2egmEthqF4JF5EvcrUKzj//N5002zHK+Gs2S1wdNLhlh ve4EBotDP4YoarrgZ9zG7uGyK3/JvTGZoYnFTnTptFVKyeNSg85XvyNW42HOwKbs4pIL 1Rs8FxrgvrLwZrvekD8ORCvo/i4wtY7edhna2YcmvdSRWycEhg5Wa3CipaDVS3lbizdc hq8hpe1xSolpvuFJOzZfiCsgWDgzmA9iXgQE4Plcxtl/mJ5ojrgTacL1SzBCYI6Jn829 1BptDf39k1s5/5/qLngfu18GD6F+6U4qqPKMvmxkU5TDiWonPdA3X3z1Zi1nUJ0hoFHQ Rl6g== MIME-Version: 1.0 X-Received: by 10.50.122.106 with SMTP id lr10mr8872291igb.32.1413312792998; Tue, 14 Oct 2014 11:53:12 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.107.11.141 with HTTP; Tue, 14 Oct 2014 11:53:12 -0700 (PDT) In-Reply-To: <9950D9D780BD4975ACEF9FA5D0F71CCC@multiplay.co.uk> References: <9950D9D780BD4975ACEF9FA5D0F71CCC@multiplay.co.uk> Date: Tue, 14 Oct 2014 11:53:12 -0700 X-Google-Sender-Auth: TZncQrJct8dkmCJTt8GKWktkuWg Message-ID: Subject: Re: System hang on shutdown when running freebsd-update From: Kevin Oberman To: Steven Hartland Content-Type: text/plain; charset=UTF-8 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: Tue, 14 Oct 2014 18:53:14 -0000 On Tue, Oct 14, 2014 at 10:16 AM, Steven Hartland wrote: > > ----- Original Message ----- From: "Kevin Oberman" > To: "FreeBSD-STABLE Mailing List" > Sent: Tuesday, October 14, 2014 6:09 PM > Subject: System hang on shutdown when running freebsd-update > > > > I thought that this was just a fluke, but it has now happened three times, >> so I guess it's now out of the "fluke" class. >> >> I have upgraded several times recently to each 10.1 BETA and RC. After the >> first install pass t install the kernel and modules, the system shutdown >> freezes at the very end. I see the buffers synced to the disks and get the >> "All buffers synced" message. Then it just hangs. The disks are not marked >> as clean and are fscked after a reset and boot. >> >> There is not much between the "All buffers synced" message and the call to >> vfs_unmountall(), so I suspect it is hanging in that call. I admit that I >> am pretty much lost whenever I look at the VFS code and I have not put a >> lot of effort going further. Just hoping that someone familiar with it >> might have an idea. >> >> I have tried several reboots and all run normally. The problem only seems >> to appear when upgrading the OS. It happened repeatedly when I tried to >> reboot before doing the second "install" pass of freebsd-update, but not >> after, so the kernel and world are not in sync. I am baffled as to what >> could be going on, but it means I need to be at the system (a baby server) >> when I upgrade, but not every time I upgrade. I know it happened on the >> 10.0-RELEAASE to 10.1-BETA1 and 10.1-RC1 to 10.1-RC2 upgrades. >> >> Has anyone else seen this? >> >> The system is an Asus VivoPC VM40B-2. >> CPU: Intel(R) Celeron(R) CPU 1007U @ 1.50GHz (1496.63-MHz K8-class CPU) >> Origin = "GenuineIntel" Id = 0x306a9 Family = 0x6 Model = 0x3a >> Stepping =9 >> >> Features=0xbfebfbff> APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI, >> MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> >> >> Features2=0xdbae3bf> VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2, >> x2APIC,POPCNT,TSCDLT,XSAVE,OSXSAVE> >> AMD Features=0x28100800 >> AMD Features2=0x1 >> Structured Extended Features=0x281 >> VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID >> TSC: P-state invariant, performance statistics >> real memory = 4294967296 (4096 MB) >> avail memory = 4014346240 (3828 MB) >> > > My usual question for this is does the following help especially if you > have IPMI loaded at the time. > sysctl hw.usb.no_shutdown_wait=1 > > Regards > Steve > No IPMI. No USB disks. It's a little tiny Celeron system in a box with a 500GB disk that I use as a low-power server at home. It does use a USB keyboard and mouse, so, even though it seems unlikely, the sysctl might solve the issue and, since I don't have any other USB devices, I think I'll set the sysctl. Won't know if it's resolved until at least the next RC or maybe 10.1-RELEASE. I should have mentioned that the system is on a single UFS GPT partition originally installed from the 10.0-RELEASE memstick distro. I did need to update the re driver to the one is stable to get my network running, but it is now running straight 10.1-RC2 with no modifications. Thanks for the suggestion, Steve! -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com