System hang on shutdown when running freebsd-update
Kevin Oberman
rkoberman at gmail.com
Tue Oct 14 18:53:14 UTC 2014
On Tue, Oct 14, 2014 at 10:16 AM, Steven Hartland <killing at multiplay.co.uk>
wrote:
>
> ----- Original Message ----- From: "Kevin Oberman" <rkoberman at gmail.com>
> To: "FreeBSD-STABLE Mailing List" <freebsd-stable at freebsd.org>
> 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<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,
>> APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,
>> MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
>>
>> Features2=0xdbae3bf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,
>> VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,
>> x2APIC,POPCNT,TSCDLT,XSAVE,OSXSAVE>
>> AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
>> AMD Features2=0x1<LAHF>
>> Structured Extended Features=0x281<FSGSBASE,SMEP,ERMS>
>> 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 at gmail.com
More information about the freebsd-stable
mailing list