Comment 24 for bug 1680502

My apologies for going dark on you. I intend to try the upstream kernel, but I've been haviing trouble finding time. With luck, I'll get it installed this coming weekend.

Meanwhile, I've since had 2 or 3 standard recurrences, and one this morning involving significantly diferent behaviour. (Of course it could be a different bug, but the primary symptom is the same ... complete lack of response on the system console.

The difference this morning is that I was able to log in over the LAN and attempt a controlled shutdown - which failed.

Also notable - I've installed at least one batch of fixes since the first incident.

-- Snippets from window follow. Note the load average. Note also the hysterical compiz process --
arlie@ansuz$ uptime
 08:09:42 up 3 days, 11:19, 2 users, load average: 9.95, 6.86, 3.43
arlie@ansuz$ sudo shutdown -r now
[sudo] password for arlie:
Failed to start reboot.target: Connection timed out
See system logs and 'systemctl status reboot.target' for details.

arlie@ansuz$ systemctl status reboot.target
Failed to get properties: Connection timed out

top - 08:17:44 up 3 days, 11:27, 2 users, load average: 10.00, 9.39, 6.11
Tasks: 312 total, 5 running, 234 sleeping, 0 stopped, 73 zombie
%Cpu(s): 0.0 us, 25.1 sy, 0.0 ni, 74.9 id, 0.1 wa, 0.0 hi, 0.0 si, 0.0 st
KiB Mem : 8140712 total, 1111908 free, 288328 used, 6740476 buff/cache
KiB Swap: 7781712 total, 7495504 free, 286208 used. 7202464 avail Mem

  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
 2527 arlie 20 0 0 0 0 Z 99.7 0.0 44:05.00 compiz
24400 arlie 20 0 41936 3780 3048 R 0.3 0.0 0:00.02 top
    1 root 20 0 120072 3980 2132 D 0.0 0.0 0:06.37 systemd
    2 root 20 0 0 0 0 S 0.0 0.0 0:00.02 kthreadd
    3 root 20 0 0 0 0 R 0.0 0.0 0:00.46 ksoftirqd/0
    5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0H
    7 root 20 0 0 0 0 S 0.0 0.0 0:40.51 rcu_sched
    8 root 20 0 0 0 0 S 0.0 0.0 0:00.00 rcu_bh