[XU4] Hangs on Reboot, Only when device has idled?

This forum is for supported devices using an ARMv7 Samsung SoC.

[XU4] Hangs on Reboot, Only when device has idled?

Postby aphirst » Sun Sep 24, 2017 10:52 pm

Log when issuing reboot causes the device to stall (from UART via minicom on another device) - https://pastebin.com/tWyhpd9N

Log when booting from cold (unplugging the power supply is necessary to get the device to boot again) - https://pastebin.com/zbrVC9n6

Log when rebooting immediately after the cold boot - https://pastebin.com/g4HHAVtA

This is very frustrating. Currently the device is in an inconvenient location, and occasionally I want/need to issue a reboot. The device hanging at this stage necessitates physically going to the device (WoL support probably would not help here, even if it were supported by the NIC; and AFAIK there's no way to force a power cycle via minicom+UART).

The problem only seems to happen when the device has been on for a while. If you do it soon after a working boot, it reboots without issue.

The device currently has 2 USB disks plugged in (3.5", mains), and my fstab is:

Code: Select all
#
# /etc/fstab: static file system information
#
# <file system>   <dir>   <type>   <options>   <dump>   <pass>

UUID=252b4d70-32ae-44ca-9af8-87f31e583b5e /mnt/Opal xfs           defaults,nofail,relatime        0       2
UUID=21585bf3-020e-45ad-8fcd-89020868ae06 /mnt/Ruby xfs           defaults,nofail,relatime        0       2

/mnt/Opal    /srv/nfs/Opal    none    bind,nofail    0    2
/mnt/Ruby    /srv/nfs/Ruby    none    bind,nofail    0    2


I can't work out what's going on here, so I'd very much appreciate any and all help in working out what's going wrong. I'm not currently able to test the device much without the disks connected, so as much as I suspect that it's related to this, I'm kind of stuck to working it out from logs etc for now.
aphirst
 
Posts: 13
Joined: Wed Sep 06, 2017 10:09 am

Re: [XU4] Hangs on Reboot, Only when device has idled?

Postby aphirst » Mon Sep 25, 2017 10:28 am

On advice of Xogium and mk-fg on IRC I decided to enable the following two options in /etc/systemd/system.conf:

Code: Select all
RuntimeWatchdogSec=35s
ShutdownWatchdogSec=35s

I was actually enquiring last night on the channel about the watchdog functionality, since I saw this commit when investigating the changes which form the new kernel version 4.9.51-1-ARCH; a commit which seems to enable this very watchdog functionality.

If this turns out to resolve my issue, then that was remarkably good timing! Otherwise, I'd still appreciate someone to go over the logs I had and my fstab just in case there is something /else/ which I should have been doing.
aphirst
 
Posts: 13
Joined: Wed Sep 06, 2017 10:09 am


Return to Samsung

Who is online

Users browsing this forum: No registered users and 2 guests