unexpected shutdown

David Hunt · February 2017

Hi all,
My UP Board is shutting down every couple of days. It goes into halt, blue led switches off.
I've the BIOS set so that when power is pulled, it comes back up.
Also, when I reboot, it comes back up.
I can't seee anything relevant in dmesg, syslog, kern.log. Below is a snippet from kern.log, I came home at 17:48 and powered the board up (power button).
Any ideas how I might debug this? I'm thinking of a serial connection to a Pi and have the console output there.
Regards,
Dave.

Feb 14 12:38:38 lazarus kernel: [82597.830098] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
Feb 14 13:03:13 lazarus kernel: [84072.004244] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
Feb 14 13:23:32 lazarus kernel: [85291.645364] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
Feb 14 13:26:25 lazarus kernel: [85464.714092] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
Feb 14 13:30:38 lazarus kernel: [85717.187058] sdhci: Timeout waiting for Buffer Read Ready interrupt during tuning procedure, falling back to fixed sampling clock
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Feb 14 17:48:00 lazarus kernel: [ 0.000000] Initializing c
group subsys cpuset
Feb 14 17:48:00 lazarus kernel: [ 0.000000] Initializing cgroup subsys cpu
Feb 14 17:48:00 lazarus kernel: [ 0.000000] Initializing cgroup subsys cpuacct
Feb 14 17:48:00 lazarus kernel: [ 0.000000] Linux version 4.4.0-2-upboard (buildd@lcy01-36) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #12-Ubuntu SMP Thu Dec 1 15:01:52 UTC
2016 (Ubuntu 4.4.0-2.12-upboard 4.4.30)
Feb 14 17:48:00 lazarus kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-upboard root=UUID=8cd72820-4980-4671-a742-5f37bef4322a ro quiet splash vt.handoff=7

Dan O'Donovan · February 2017

Hi Dave

This one is puzzling. I don't think I've seen it myself on any other UP boards.

That said, there was one thing that came up before, with a particular BIOS version. There was some incorrect DPTF settings in the BIOS which were configuring a critical thermal trip point setting too low (60 degrees, iirc). When used in conjunction with Ubuntu (which was running stuff like thermald and possibly using a different configuration of thermal-related kernel drivers by default), it would cause the board to shut down abruptly if the core temperature rose above that trip point. I think this was resolved, at least in the later BIOS releases, but it might be something to check out (just a long-shot really).

I don't think there's many things that will cause your board to physically shut down, but that would be one. Other issues I've seen in the past, such as a dodgy wifi driver leaking memory, crashes in kernel modules, etc. would typically cause the board to end up in a hung state (and typically with some clues left in syslog) but not a full shutdown.

An abrupt shutdown might perhaps explain why the end of the previous syslog looks corrupted. I don't suppose journalctl shows anything different?

Cheers,
-Dan

David Hunt · February 2017

I've disabled thermald, still same issue. Don't worry about it, I caused some damage on that board before, and my (temporary) repairs have probably destabilised the board. I'll get myself a replacement.
Thanks Dan.
Regards,
Dave.

unexpected shutdown

Comments

Categories