Quote:
Originally Posted by ekwus
Hey I've now checked and it happens every 40 odd minutes. When starting the VNC Viewer via telnet from the Pi (via SSH from the PC) this is what I get back after the Kindle reboots
login as: pi
pi@172.22.1.102's password:
Linux raspberrypi 3.6.11+ #474 PREEMPT Thu Jun 13 17:14:42 BST 2013 armv6l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Aug 2 12:01:16 2013 from pharlap.home
pi@raspberrypi ~ $ telnet 192.168.2.2
Trying 192.168.2.2...
Connected to 192.168.2.2.
Escape character is '^]'.
Welcome to Kindle!
#################################################
# N O T I C E * N O T I C E * N O T I C E #
#################################################
Rootfs is mounted read-only. Invoke mntroot rw to
switch back to a writable rootfs.
#################################################
[root@kindle root]# /etc/init.d/netwatchd stop
system: I netwatchd:def:stopping Netwatch Daemon
[root@kindle root]# /etc/init.d/powerd stop
Stopping Power Management Daemon: [root@kindle root]#
[root@kindle root]# /mnt/us/kindlevncviewer/kvncviewer.sh -password kindle 192.168.2.1:1
com.lab126.powerd failed to open lipc for preventScreenSaver event
02/08/2013 13:16:15 VNC server supports protocol version 3.8 (viewer 3.8)
02/08/2013 13:16:15 We have 2 security types to read
02/08/2013 13:16:15 0) Received security type 2
02/08/2013 13:16:15 Selecting security type 2 (0/2 in the list)
02/08/2013 13:16:15 1) Received security type 16
02/08/2013 13:16:15 Selected Security Scheme 2
02/08/2013 13:16:15 VNC authentication succeeded
02/08/2013 13:16:15 Desktop name "pi's X desktop (raspberrypi:1)"
02/08/2013 13:16:15 Connected to VNC server, using protocol version 3.8
02/08/2013 13:16:15 VNC server default format:
02/08/2013 13:16:15 32 bits per pixel.
02/08/2013 13:16:15 Least significant byte first in each pixel.
02/08/2013 13:16:15 TRUE colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
partially updating eink display (0,0)-(822,823)
Broadcast message from root (Fri Aug 2 14:00:37 2013):
The system is going down for reboot NOW!
Broadcast message from root (console) (Fri Aug 2 14:00:39 2013):
We're switching back to USB MS, so if you're wondering why your terminal is frozen, go read the docs!
|
Hmm...
That listing shows that powerd was stopped before lipc could process the 'prevent screen saver' event.
Try it the other way around, I.E: Doing the 'prevent screen saver' prior to stopping any of the system services.
But 40 minutes?
That sounds more like something is running out of memory, triggering the OOM Killer, that leads to a forced re-boot.
(^ ^ ^ ^ BFG)