Weird shutdown occurs randomly (low priority topic)

Support for the UPS PIco HV3.0A, UPS PIco HV3.0 A Plus, UPS PIco HV3.0A Terminal Block products

Weird shutdown occurs randomly (low priority topic)

Postby tater » Thu Mar 02, 2017 6:44 am

Hi all,
So I came home today to find my pi in an interesting state, and I'm trying to reconstruct the chain of events.
All pico LEDs were off, and main (usb) power was still connected (the rpi red led was lit and not blinking).
But I could not ssh into it, and my script displaying the clock and some other things on a tft display was 'frozen' (another sign mains weren't lost. The TFT didn't go blank.)
.
So I yanked the main power (red led went out) and plugged it back in.
Rpi didn't boot (red led lit constantly, but no activity from the green), and the pico didn't boot.
So I unplugged the power, hit the pico reset button, then plugged power back in. Everything booted up as normal, and the battery shows a full charge.

Analysis shows:
The tft frozen clock stopped at feb 28, 13:46:21.
Syslog shows six seconds later the a normal dhclient message.
But the next line is a bootup (my successful 'reset pico and plug main power back in' boot from above). So there was no graceful shutdown...
Here is the log:
Code: Select all
Feb 28 13:41:29 raspberrypi2 dhclient: No DHCPOFFERS received.
Feb 28 13:41:29 raspberrypi2 dhclient: No working leases in persistent database - sleeping.
Feb 28 13:45:26 raspberrypi2 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
Feb 28 13:45:32 raspberrypi2 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Feb 28 13:45:41 raspberrypi2 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Feb 28 13:45:50 raspberrypi2 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
Feb 28 13:46:05 raspberrypi2 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
Feb 28 13:46:13 raspberrypi2 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Feb 28 13:46:27 raspberrypi2 dhclient: No DHCPOFFERS received.
Feb 28 13:46:27 raspberrypi2 dhclient: No working leases in persistent database - sleeping.
Dec 31 19:00:13 raspberrypi2 kernel: imklog 5.8.11, log source = /proc/kmsg started.
Dec 31 19:00:13 raspberrypi2 rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="2132" x-info="http://www.rsyslog.com"] start


As part of trying to figure out what happened, I naturally ask myself "How could I make this happen?"
But after an evening of thinking, I can't come up with a way, besides maybe someone touched it and gave it a good ESD zap.
I even have the Rpi's hardware watchdog enabled, and it didn't seem to catch this weird condition.

Anyone out there want to fathom a guess?
It's a low priority topic for me, but it is a fun one to debug :)

PS: I'm using firmware 0x24

Thanks!
tater
 
Posts: 16
Joined: Wed Feb 08, 2017 6:49 am

Return to UPS PIco HV3.0A

Who is online

Users browsing this forum: No registered users and 2 guests