Page 1 of 1

Freeze after 2 or more hours

Posted: 26 Apr 2016, 12:38
by gfkat
Hi all,
I have porteus kiosk 3.7. I have changed just the chrome configuration for add one extension (virtual keyboard). All work well but during the normal working of the kiosk, it freeze and the only way is to reboot it. I have tried to activate the zRAM and the SWAP but with no improments.
Could anyone help me to analyze the freeze?

I think the problem is the kernel but I don't know how to analyze it. I know there is a new versione of the Porteus Kiosk with an updated kernel (20160417). The PC is an ASUS All-in-one ET1620IUTT.
Could I download it from the internet?

We are currently testing the kiosk in an industrial plan for monitoring the productive lines in replacement to Ubuntu. So is possible, if the system became stable and reliable, make a good donation to the creator.

I tried the TOP command on ssh, but i can't found any information about the freeze.

The top result:

Code: Select all

Mem: 671356K used, 2021356K free, 182692K shrd, 60792K buff, 373260K cached
CPU:  3.3% usr  0.4% sys  0.9% nic 95.4% idle  0.0% io  0.0% irq  0.0% sirq
Load average: 1.57 0.77 0.33 2/165 1528
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
 1303  1267 guest    S     435m 16.5   2  3.4 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=*UM
 1291  1254 guest    S     229m  8.7   1  0.6 /opt/google/chrome/chrome --type=gpu-process --channel=1254.0.819980887 --user
 1254  1250 guest    S     429m 16.2   1  0.2 /opt/google/chrome/chrome --start-fullscreen --user-data-dir=/usr/chromedata -
  969   968 root     S <  72076  2.6   0  0.1 /usr/bin/X :0 -nolisten tcp vt7 -auth /root/.serverauth.919
 1197  1171 root     S    25364  0.9   2  0.0 x11vnc -rfbauth /root/.vnc/passwd -auth /root/.serverauth.919 -display :0 -for
 1528  1380 root     R      576  0.0   1  0.0 top
 1521     2 root     SW       0  0.0   3  0.0 [kworker/u8:1]
 1315  1267 guest    S     315m 11.9   2  0.0 /opt/google/chrome/chrome --type=renderer --lang=en-US --force-fieldtrials=*UM
 1267  1257 guest    S     184m  7.0   2  0.0 /opt/google/chrome/chrome --type=zygote --user-data-dir=/usr/chromedata
 1257  1254 guest    S     176m  6.7   0  0.0 /opt/google/chrome/chrome --type=zygote --user-data-dir=/usr/chromedata
 1295  1291 guest    S     171m  6.5   1  0.0 /opt/google/chrome/chrome --type=gpu-broker
 1137     1 root     S    53176  1.9   1  0.0 /usr/bin/dunst -config /usr/share/dunst/dunstrc
 1373  1261 root     S    40776  1.5   2  0.0 sshd: root@pts/0
  982   979 root     S    11688  0.4   3  0.0 /usr/bin/openbox --startup /usr/libexec/openbox-autostart OPENBOX
 1263  1257 guest    S     7360  0.2   2  0.0 /opt/google/chrome/nacl_helper
 1261     1 root     S     4744  0.1   2  0.0 /usr/sbin/sshd
  779     1 root     S     4288  0.1   1  0.0 /lib/systemd/systemd-udevd -d
  985     1 root     S     3252  0.1   3  0.0 dbus-launch --exit-with-session /usr/bin/openbox-session
  968   919 root     S     3244  0.1   3  0.0 xinit /etc/X11/xinit/xinitrc -- /usr/bin/X :0 -nolisten tcp vt7 -auth /root/.s
  986     1 root     S     2716  0.1   3  0.0 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
  860     1 messageb S     2716  0.1   3  0.0 /usr/bin/dbus-daemon --system
  955     1 root     S     1944  0.0   1  0.0 /usr/sbin/acpid -n
 1380  1373 root     S      580  0.0   0  0.0 -bash
  906   903 root     S      580  0.0   1  0.0 -bash -c /usr/bin/startx -- -nolisten tcp vt7 > /dev/null 2>&1
  919   906 root     S      576  0.0   1  0.0 {startx} /bin/sh /usr/bin/startx -- -nolisten tcp vt7
 1250  1249 guest    S      572  0.0   1  0.0 {chrome} /bin/sh /usr/bin/chrome
 1249  1242 guest    S      572  0.0   0  0.0 bash -c chrome
 1171     1 root     S      568  0.0   1  0.0 {rc.vncd} /bin/sh /etc/rc.d/rc.vncd
  979   968 root     S      568  0.0   1  0.0 {xinitrc} /bin/sh /etc/X11/xinit/xinitrc
  903     1 root     S      568  0.0   2  0.0 {xdm} /bin/sh /usr/bin/xdm
 1242     1 root     S      568  0.0   1  0.0 {gui-app} /bin/sh /opt/porteus-scripts/gui-app
    1     0 root     S      240  0.0   3  0.0 init [4]
    7     2 root     SW       0  0.0   0  0.0 [rcu_preempt]
  819     2 root     SW       0  0.0   1  0.0 [kworker/1:2]
   27     2 root     SWN      0  0.0   0  0.0 [khugepaged]
 1467     2 root     SW       0  0.0   1  0.0 [kworker/u8:0]
  137     2 root     SW<      0  0.0   1  0.0 [loop2]
 1517     2 root     SW       0  0.0   1  0.0 [kworker/u8:2]
   34     2 root     SW       0  0.0   3  0.0 [kworker/3:1]
  101     2 root     SW       0  0.0   0  0.0 [kworker/0:1]
   73     2 root     SW       0  0.0   2  0.0 [kworker/2:1]
  132     2 root     SW<      0  0.0   3  0.0 [loop1]
    3     2 root     SW       0  0.0   0  0.0 [ksoftirqd/0]
   66     2 root     SW       0  0.0   1  0.0 [kworker/1:1]
  127     2 root     SW<      0  0.0   0  0.0 [loop0]
   12     2 root     SW       0  0.0   1  0.0 [ksoftirqd/1]
  172     2 root     SW<      0  0.0   1  0.0 [kworker/1:1H]
   47     2 root     SW<      0  0.0   1  0.0 [bioset]
    2     0 root     SW       0  0.0   0  0.0 [kthreadd]
   46     2 root     SW<      0  0.0   2  0.0 [bioset]
   11     2 root     SW       0  0.0   1  0.0 [migration/1]
   38     2 root     SW<      0  0.0   2  0.0 [xfsalloc]
   15     2 root     SW       0  0.0   2  0.0 [migration/2]
   16     2 root     SW       0  0.0   2  0.0 [ksoftirqd/2]
   17     2 root     SW       0  0.0   2  0.0 [kworker/2:0]
   50     2 root     SW<      0  0.0   3  0.0 [bioset]
    4     2 root     SW       0  0.0   0  0.0 [kworker/0:0]
    5     2 root     SW<      0  0.0   0  0.0 [kworker/0:0H]
   37     2 root     SW       0  0.0   3  0.0 [fsnotify_mark]
Write failed: Broken pipe     0  0.0   3  0.0 [rcu_sched]
Thank you all for the help,
Regards,
Luciano.

Re: Freeze after 2 or more hours

Posted: 26 Apr 2016, 14:11
by fanthom
Hello Luciano,

"I know there is a new versione of the Porteus Kiosk with an updated kernel (20160417). The PC is an ASUS All-in-one ET1620IUTT.
Could I download it from the internet?"
Please enable debug mode and free trial of the 'automatic updates' service in the wizard, boot the kiosk and send generated debug report to support@porteus-kiosk.org.

Please mind that your PC must be 64bit in order to handle the update as we moved to 64bits only for kiosk:
http://porteus-kiosk.org/news.html#160411

Thank you.