8th March 2017, 7:23
Oh dear. Tower just suffered another complete freeze requiring hard-reset. First since i rebuilt it after the recent disaster, ie, first with Maui 17.03 Plasma 5.9.3, + with NO Nvidia GT610 gpu installed [only the integrated Intel GPU], + HWE. Unbelievable!!!
It occurred at 14:45, almost immediately that Update Manager had just completed some important updates, including kernel 4.8.0-39 to 4.8.0-41 [also 4.4.0-65 to 4.4.0-66], network-manager, & desktop-file-utils. I had just begun closing my open pgms to do the reboot, when it all froze.
Here's an excerpt from syslog spanning the critical time, but i cannot see anything overtly nasty; just a prominent time-gap at the important moment:
Note that I manually inserted the blank line here for emphasis; the original file is continuous.
Whilst it makes no sense to me that the updates should have triggered this bad reaction, i find the timing to be more than innocently coincidental [also the absence of "bad stuff" in the log], so for now i shall assume this was a once-off incident rather than yet another failure in the litany of this thread. However, if there is even one more repeat of this after now, i shall immediately reinstall the Nvidia gpu & abandon this experiment [ie, the working hypothesis that the Nvidia gpu was causing all these freezes would then be disproved].
This is all just so exasperating.
It occurred at 14:45, almost immediately that Update Manager had just completed some important updates, including kernel 4.8.0-39 to 4.8.0-41 [also 4.4.0-65 to 4.4.0-66], network-manager, & desktop-file-utils. I had just begun closing my open pgms to do the reboot, when it all froze.
Here's an excerpt from syslog spanning the critical time, but i cannot see anything overtly nasty; just a prominent time-gap at the important moment:
Code:
Mar 8 14:44:39 GA-Z97-HD3 systemd[1]: Started ACPI event daemon.
Mar 8 14:44:39 GA-Z97-HD3 systemd[1]: Reloading D-Bus System Message Bus.
Mar 8 14:44:39 GA-Z97-HD3 dbus-daemon[1112]: Unknown username "whoopsie" in message bus configuration file
Mar 8 14:44:39 GA-Z97-HD3 dbus[1112]: [system] Reloaded configuration
Mar 8 14:44:39 GA-Z97-HD3 dbus-send[21075]: method return time=1488944679.550282 sender=org.freedesktop.DBus -> destination=:1.378 serial=3 reply_serial=2
Mar 8 14:44:39 GA-Z97-HD3 systemd[1]: Reloaded D-Bus System Message Bus.
Mar 8 14:44:39 GA-Z97-HD3 systemd[1]: Reloading.
Mar 8 14:44:39 GA-Z97-HD3 systemd[1]: Configuration file /etc/systemd/system/vyprvpn.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Mar 8 14:44:39 GA-Z97-HD3 systemd[1]: [/etc/systemd/system/vyprvpn.service:9] Executable path is not absolute, ignoring: killall vyprvpn_service
Mar 8 14:44:39 GA-Z97-HD3 systemd[1]: apt-daily.timer: Adding 8h 39min 56.168679s random time.
Mar 8 14:44:39 GA-Z97-HD3 systemd[1]: snapd.refresh.timer: Adding 1h 58min 27.196036s random time.
Mar 8 14:44:39 GA-Z97-HD3 systemd[1]: Started CUPS Scheduler.
Mar 8 14:44:39 GA-Z97-HD3 systemd[1]: Started ACPI event daemon.
Mar 8 14:50:14 GA-Z97-HD3 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="1142" x-info="http://www.rsyslog.com"] start
Mar 8 14:50:14 GA-Z97-HD3 rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
Mar 8 14:50:14 GA-Z97-HD3 rsyslogd: rsyslogd's groupid changed to 108
Mar 8 14:50:14 GA-Z97-HD3 rsyslogd: rsyslogd's userid changed to 104
Mar 8 14:50:14 GA-Z97-HD3 systemd-modules-load[391]: Inserted module 'lp'
Mar 8 14:50:14 GA-Z97-HD3 systemd-modules-load[391]: Inserted module 'ppdev'
Mar 8 14:50:14 GA-Z97-HD3 loadkeys[390]: Loading /etc/console-setup/cached.kmap.gz
Mar 8 14:50:14 GA-Z97-HD3 resolvconf[414]: /etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf
Mar 8 14:50:14 GA-Z97-HD3 systemd[1]: Started udev Kernel Device Manager.Note that I manually inserted the blank line here for emphasis; the original file is continuous.
Whilst it makes no sense to me that the updates should have triggered this bad reaction, i find the timing to be more than innocently coincidental [also the absence of "bad stuff" in the log], so for now i shall assume this was a once-off incident rather than yet another failure in the litany of this thread. However, if there is even one more repeat of this after now, i shall immediately reinstall the Nvidia gpu & abandon this experiment [ie, the working hypothesis that the Nvidia gpu was causing all these freezes would then be disproved].
This is all just so exasperating.