All of lore.kernel.org
 help / color / mirror / Atom feed
* Fwd: coretemp seems to reset immediately
       [not found] <CAO299FuK1yX2JRE6E5a4G-8dcJ-RbOjZj_TPyCUJ+tZtM2NWgA@mail.gmail.com>
@ 2017-02-15 10:00 ` Chris Tillman
  2017-02-15 10:48   ` Guenter Roeck
  0 siblings, 1 reply; 4+ messages in thread
From: Chris Tillman @ 2017-02-15 10:00 UTC (permalink / raw)
  To: linux-hwmon

[-- Attachment #1: Type: text/plain, Size: 2912 bytes --]

Hi,

I had the awful experience of having my computer fry before my eyes
the other day. It was running quite hot (building llvm), and it
stopped accepting mouse inputs. I tried to regain control, and after
20 seconds or so it switched me to virtual console 1. But very shortly
after that it died, and now it won't even start to boot.

Anyway, the reason I'm writing: I retrieved the disk out of it, and on
another machine, looked through the syslog. I saw that coretemp was
reporting over temps every five minutes, and claiming the cpu was
being throttled. But then the very next message in the log says the
temperature is normal. I'm wondering, does this mean the throttling
was also being cancelled immediately? If so it could explain how the
machine got so hot that it died on the spot.

I've attached the log. Here's the final refrain of what was occurring
every 5 minutes for the fifty minutes previous:

Feb 12 19:27:25 ctillman kernel: [137082.856603] CPU3: Core
temperature above threshold, cpu clock throttled (total events =
804180)
Feb 12 19:27:25 ctillman kernel: [137082.856604] CPU2: Core
temperature above threshold, cpu clock throttled (total events =
804180)
Feb 12 19:27:25 ctillman kernel: [137082.856607] CPU1: Package
temperature above threshold, cpu clock throttled (total events =
862662)
Feb 12 19:27:25 ctillman kernel: [137082.856608] CPU0: Package
temperature above threshold, cpu clock throttled (total events =
862662)
Feb 12 19:27:25 ctillman kernel: [137082.856610] CPU2: Package
temperature above threshold, cpu clock throttled (total events =
862662)
Feb 12 19:27:25 ctillman kernel: [137082.856621] CPU3: Package
temperature above threshold, cpu clock throttled (total events =
862662)
Feb 12 19:27:25 ctillman kernel: [137082.857603] CPU3: Core
temperature/speed normal
Feb 12 19:27:25 ctillman kernel: [137082.857604] CPU2: Core
temperature/speed normal
Feb 12 19:27:25 ctillman kernel: [137082.857606] CPU0: Package
temperature/speed normal
Feb 12 19:27:25 ctillman kernel: [137082.857608] CPU1: Package
temperature/speed normal
Feb 12 19:27:25 ctillman kernel: [137082.857609] CPU2: Package
temperature/speed normal
Feb 12 19:27:25 ctillman kernel: [137082.857612] CPU3: Package
temperature/speed normal

Notice how each core gets flagged, and then in the same millisecond
gets cleared. For example

[137082.856603] CPU3: Core temperature above threshold, cpu clock
throttled (total events = 804180)
[137082.857603] CPU3: Core temperature/speed normal

The machine is an HP Probook 4530s, which I just bought second hand a
couple weeks ago. I'd really been enjoying its speed! compared to the
older computer I'm writing on now.

I'd already had a run-in with overheating, and filed a bug against the
gpu because it apparently crashed during the previous event:

[Bug 99611] GPU hang after over temperature

That log also showed the same pattern.

--
Chris Tillman
Developer

[-- Attachment #2: syslog-20170211 --]
[-- Type: application/octet-stream, Size: 61963 bytes --]

Feb 12 16:30:51 ctillman liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="497" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Feb 12 16:30:52 ctillman liblogging-stdlog:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="497" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
Feb 12 16:30:52 ctillman anacron[8724]: Job `cron.daily' terminated
Feb 12 16:35:50 ctillman anacron[8724]: Job `cron.weekly' started
Feb 12 16:35:50 ctillman anacron[9167]: Updated timestamp for job `cron.weekly' to 2017-02-12
Feb 12 16:35:55 ctillman anacron[8724]: Job `cron.weekly' terminated
Feb 12 16:35:55 ctillman anacron[8724]: Normal exit (2 jobs run)
Feb 12 16:45:29 ctillman systemd[1711]: Time has been changed
Feb 12 16:45:29 ctillman systemd[1]: Time has been changed
Feb 12 16:45:29 ctillman systemd[1]: apt-daily.timer: Adding 4h 22min 34.737999s random time.
Feb 12 16:45:33 ctillman ntpd[713]: Soliciting pool server 103.242.68.68
Feb 12 16:53:06 ctillman ntpd[713]: 222.154.231.239 local addr 192.168.1.69 -> <null>
Feb 12 17:17:01 ctillman CRON[9641]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 12 17:25:58 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.*.
Feb 12 17:26:00 ctillman ntpd[713]: Listen normally on 105 wlo1 [fd64:a651:689c:e600:9002:5357:1d24:e14a]:123
Feb 12 17:26:00 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.
Feb 12 17:27:25 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.*.
Feb 12 17:27:25 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.
Feb 12 17:36:24 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.*.
Feb 12 17:36:24 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.
Feb 12 17:41:47 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.*.
Feb 12 17:41:47 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.
Feb 12 17:49:12 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.*.
Feb 12 17:49:12 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.
Feb 12 17:58:09 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.*.
Feb 12 17:58:09 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.
Feb 12 18:06:57 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.*.
Feb 12 18:06:57 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.
Feb 12 18:11:34 ctillman dbus-daemon[1739]: Activating service name='org.freedesktop.thumbnails.Cache1'
Feb 12 18:11:34 ctillman dbus-daemon[1739]: Successfully activated service 'org.freedesktop.thumbnails.Cache1'
Feb 12 18:12:51 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.*.
Feb 12 18:12:51 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.
Feb 12 18:17:01 ctillman CRON[10449]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 12 18:21:50 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.
Feb 12 18:21:50 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:34d1:31b9:e8f2:3a27 on wlo1.*.
Feb 12 18:21:51 ctillman ntpd[713]: Listen normally on 106 wlo1 [fd64:a651:689c:e600:34d1:31b9:e8f2:3a27]:123
Feb 12 18:22:21 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.*.
Feb 12 18:22:21 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.*.
Feb 12 18:22:21 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.
Feb 12 18:22:21 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:b1cc:443a:7946:5273 on wlo1.
Feb 12 18:26:02 ctillman ntpd[713]: Deleting interface #103 wlo1, fd64:a651:689c:e600:b1cc:443a:7946:5273#123, interface stats: received=0, sent=0, dropped=0, active_time=7199 secs
Feb 12 18:29:47 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.*.
Feb 12 18:29:47 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.
Feb 12 18:31:01 ctillman kernel: [133698.548622] usb 1-1.3: new full-speed USB device number 8 using ehci-pci
Feb 12 18:31:01 ctillman kernel: [133698.661588] usb 1-1.3: New USB device found, idVendor=046d, idProduct=c52b
Feb 12 18:31:01 ctillman kernel: [133698.661594] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 12 18:31:01 ctillman kernel: [133698.661597] usb 1-1.3: Product: USB Receiver
Feb 12 18:31:01 ctillman kernel: [133698.661600] usb 1-1.3: Manufacturer: Logitech
Feb 12 18:31:01 ctillman kernel: [133698.674101] logitech-djreceiver 0003:046D:C52B.002B: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1a.0-1.3/input2
Feb 12 18:31:01 ctillman mtp-probe: checking bus 1, device 8: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3"
Feb 12 18:31:01 ctillman kernel: [133698.800467] input: Logitech M215 2nd Gen as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.2/0003:046D:C52B.002B/0003:046D:401B.002C/input/input104
Feb 12 18:31:01 ctillman mtp-probe: bus: 1, device: 8 was not an MTP device
Feb 12 18:31:01 ctillman kernel: [133698.800979] logitech-hidpp-device 0003:046D:401B.002C: input,hidraw1: USB HID v1.11 Mouse [Logitech M215 2nd Gen] on usb-0000:00:1a.0-1.3:1
Feb 12 18:37:25 ctillman kernel: [134083.088299] CPU2: Core temperature above threshold, cpu clock throttled (total events = 214319)
Feb 12 18:37:25 ctillman kernel: [134083.088301] CPU3: Core temperature above threshold, cpu clock throttled (total events = 214319)
Feb 12 18:37:25 ctillman kernel: [134083.088303] CPU1: Package temperature above threshold, cpu clock throttled (total events = 244719)
Feb 12 18:37:25 ctillman kernel: [134083.088304] CPU0: Package temperature above threshold, cpu clock throttled (total events = 244719)
Feb 12 18:37:25 ctillman kernel: [134083.088305] CPU3: Package temperature above threshold, cpu clock throttled (total events = 244719)
Feb 12 18:37:25 ctillman kernel: [134083.088315] CPU2: Package temperature above threshold, cpu clock throttled (total events = 244719)
Feb 12 18:37:25 ctillman kernel: [134083.089309] CPU2: Core temperature/speed normal
Feb 12 18:37:25 ctillman kernel: [134083.089310] CPU3: Core temperature/speed normal
Feb 12 18:37:25 ctillman kernel: [134083.089311] CPU0: Package temperature/speed normal
Feb 12 18:37:25 ctillman kernel: [134083.089312] CPU1: Package temperature/speed normal
Feb 12 18:37:25 ctillman kernel: [134083.089313] CPU3: Package temperature/speed normal
Feb 12 18:37:25 ctillman kernel: [134083.089316] CPU2: Package temperature/speed normal
Feb 12 18:38:42 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.*.
Feb 12 18:38:42 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.
Feb 12 18:40:37 ctillman dbus-daemon[1739]: Activating service name='org.freedesktop.thumbnails.Thumbnailer1'
Feb 12 18:40:40 ctillman dbus-daemon[1739]: Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Feb 12 18:40:58 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.*.
Feb 12 18:40:58 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.
Feb 12 18:41:02 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.*.
Feb 12 18:41:02 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.
Feb 12 18:41:06 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.*.
Feb 12 18:41:06 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.
Feb 12 18:41:17 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.*.
Feb 12 18:41:17 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.
Feb 12 18:42:25 ctillman kernel: [134383.065025] CPU3: Core temperature/speed normal
Feb 12 18:42:25 ctillman kernel: [134383.065027] CPU2: Core temperature/speed normal
Feb 12 18:42:25 ctillman kernel: [134383.065029] CPU1: Package temperature/speed normal
Feb 12 18:42:25 ctillman kernel: [134383.065031] CPU0: Package temperature/speed normal
Feb 12 18:42:25 ctillman kernel: [134383.065033] CPU2: Package temperature/speed normal
Feb 12 18:42:25 ctillman kernel: [134383.065035] CPU3: Package temperature/speed normal
Feb 12 18:43:00 ctillman upowerd[1824]: energy 40.338000 bigger than full 40.327200
Feb 12 18:43:00 ctillman dbus-daemon[1739]: Activating via systemd: service name='org.freedesktop.Notifications' unit='xfce4-notifyd.service'
Feb 12 18:43:00 ctillman systemd[1711]: Starting XFCE notifications service...
Feb 12 18:43:01 ctillman dbus-daemon[1739]: Successfully activated service 'org.freedesktop.Notifications'
Feb 12 18:43:01 ctillman systemd[1711]: Started XFCE notifications service.
Feb 12 18:46:22 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.*.
Feb 12 18:46:22 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.
Feb 12 18:47:25 ctillman kernel: [134683.037757] CPU2: Core temperature/speed normal
Feb 12 18:47:25 ctillman kernel: [134683.037758] CPU3: Core temperature/speed normal
Feb 12 18:47:25 ctillman kernel: [134683.037760] CPU0: Package temperature/speed normal
Feb 12 18:47:25 ctillman kernel: [134683.037761] CPU1: Package temperature/speed normal
Feb 12 18:47:25 ctillman kernel: [134683.037763] CPU3: Package temperature/speed normal
Feb 12 18:47:25 ctillman kernel: [134683.037765] CPU2: Package temperature/speed normal
Feb 12 18:48:40 ctillman kernel: [134758.101611] usb 1-1.3: USB disconnect, device number 8
Feb 12 18:52:25 ctillman kernel: [134983.012454] CPU2: Core temperature above threshold, cpu clock throttled (total events = 387036)
Feb 12 18:52:25 ctillman kernel: [134983.012455] CPU3: Core temperature above threshold, cpu clock throttled (total events = 387036)
Feb 12 18:52:25 ctillman kernel: [134983.012458] CPU1: Package temperature above threshold, cpu clock throttled (total events = 424124)
Feb 12 18:52:25 ctillman kernel: [134983.012460] CPU0: Package temperature above threshold, cpu clock throttled (total events = 424124)
Feb 12 18:52:25 ctillman kernel: [134983.012461] CPU3: Package temperature above threshold, cpu clock throttled (total events = 424124)
Feb 12 18:52:25 ctillman kernel: [134983.012471] CPU2: Package temperature above threshold, cpu clock throttled (total events = 424124)
Feb 12 18:52:25 ctillman kernel: [134983.013462] CPU2: Core temperature/speed normal
Feb 12 18:52:25 ctillman kernel: [134983.013463] CPU3: Core temperature/speed normal
Feb 12 18:52:25 ctillman kernel: [134983.013465] CPU0: Package temperature/speed normal
Feb 12 18:52:25 ctillman kernel: [134983.013466] CPU1: Package temperature/speed normal
Feb 12 18:52:25 ctillman kernel: [134983.013468] CPU3: Package temperature/speed normal
Feb 12 18:52:25 ctillman kernel: [134983.013470] CPU2: Package temperature/speed normal
Feb 12 18:54:35 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.*.
Feb 12 18:54:35 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.
Feb 12 18:57:25 ctillman kernel: [135282.991184] CPU2: Core temperature above threshold, cpu clock throttled (total events = 447115)
Feb 12 18:57:25 ctillman kernel: [135282.991185] CPU3: Core temperature above threshold, cpu clock throttled (total events = 447115)
Feb 12 18:57:25 ctillman kernel: [135282.991188] CPU0: Package temperature above threshold, cpu clock throttled (total events = 486575)
Feb 12 18:57:25 ctillman kernel: [135282.991190] CPU1: Package temperature above threshold, cpu clock throttled (total events = 486575)
Feb 12 18:57:25 ctillman kernel: [135282.991192] CPU3: Package temperature above threshold, cpu clock throttled (total events = 486575)
Feb 12 18:57:25 ctillman kernel: [135282.991202] CPU2: Package temperature above threshold, cpu clock throttled (total events = 486575)
Feb 12 18:57:25 ctillman kernel: [135282.993214] CPU2: Core temperature/speed normal
Feb 12 18:57:25 ctillman kernel: [135282.993215] CPU3: Core temperature/speed normal
Feb 12 18:57:25 ctillman kernel: [135282.993217] CPU0: Package temperature/speed normal
Feb 12 18:57:25 ctillman kernel: [135282.993219] CPU1: Package temperature/speed normal
Feb 12 18:57:25 ctillman kernel: [135282.993220] CPU3: Package temperature/speed normal
Feb 12 18:57:25 ctillman kernel: [135282.993223] CPU2: Package temperature/speed normal
Feb 12 19:02:25 ctillman kernel: [135582.966943] CPU3: Core temperature above threshold, cpu clock throttled (total events = 507698)
Feb 12 19:02:25 ctillman kernel: [135582.966944] CPU2: Core temperature above threshold, cpu clock throttled (total events = 507698)
Feb 12 19:02:25 ctillman kernel: [135582.966947] CPU0: Package temperature above threshold, cpu clock throttled (total events = 550309)
Feb 12 19:02:25 ctillman kernel: [135582.966948] CPU1: Package temperature above threshold, cpu clock throttled (total events = 550309)
Feb 12 19:02:25 ctillman kernel: [135582.966950] CPU2: Package temperature above threshold, cpu clock throttled (total events = 550309)
Feb 12 19:02:25 ctillman kernel: [135582.966961] CPU3: Package temperature above threshold, cpu clock throttled (total events = 550309)
Feb 12 19:02:25 ctillman kernel: [135582.969922] CPU2: Core temperature/speed normal
Feb 12 19:02:25 ctillman kernel: [135582.969923] CPU3: Core temperature/speed normal
Feb 12 19:02:25 ctillman kernel: [135582.969926] CPU1: Package temperature/speed normal
Feb 12 19:02:25 ctillman kernel: [135582.969927] CPU0: Package temperature/speed normal
Feb 12 19:02:25 ctillman kernel: [135582.969929] CPU3: Package temperature/speed normal
Feb 12 19:02:25 ctillman kernel: [135582.969931] CPU2: Package temperature/speed normal
Feb 12 19:03:21 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.*.
Feb 12 19:03:21 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.
Feb 12 19:07:25 ctillman kernel: [135882.941668] CPU3: Core temperature above threshold, cpu clock throttled (total events = 567791)
Feb 12 19:07:25 ctillman kernel: [135882.941670] CPU2: Core temperature above threshold, cpu clock throttled (total events = 567791)
Feb 12 19:07:25 ctillman kernel: [135882.941673] CPU1: Package temperature above threshold, cpu clock throttled (total events = 614460)
Feb 12 19:07:25 ctillman kernel: [135882.941675] CPU0: Package temperature above threshold, cpu clock throttled (total events = 614460)
Feb 12 19:07:25 ctillman kernel: [135882.941677] CPU2: Package temperature above threshold, cpu clock throttled (total events = 614460)
Feb 12 19:07:25 ctillman kernel: [135882.941690] CPU3: Package temperature above threshold, cpu clock throttled (total events = 614460)
Feb 12 19:07:25 ctillman kernel: [135882.942644] CPU3: Core temperature/speed normal
Feb 12 19:07:25 ctillman kernel: [135882.942645] CPU2: Core temperature/speed normal
Feb 12 19:07:25 ctillman kernel: [135882.942647] CPU0: Package temperature/speed normal
Feb 12 19:07:25 ctillman kernel: [135882.942649] CPU1: Package temperature/speed normal
Feb 12 19:07:25 ctillman kernel: [135882.942650] CPU2: Package temperature/speed normal
Feb 12 19:07:25 ctillman kernel: [135882.942654] CPU3: Package temperature/speed normal
Feb 12 19:11:01 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.*.
Feb 12 19:11:01 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.
Feb 12 19:12:25 ctillman kernel: [136182.917404] CPU3: Core temperature/speed normal
Feb 12 19:12:25 ctillman kernel: [136182.917405] CPU2: Core temperature/speed normal
Feb 12 19:12:25 ctillman kernel: [136182.917407] CPU1: Package temperature/speed normal
Feb 12 19:12:25 ctillman kernel: [136182.917409] CPU0: Package temperature/speed normal
Feb 12 19:12:25 ctillman kernel: [136182.917410] CPU2: Package temperature/speed normal
Feb 12 19:12:25 ctillman kernel: [136182.917413] CPU3: Package temperature/speed normal
Feb 12 19:12:50 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:5053:35f2:9efd:9b88 on wlo1.*.
Feb 12 19:12:51 ctillman ntpd[713]: Listen normally on 107 wlo1 [fd64:a651:689c:e600:5053:35f2:9efd:9b88]:123
Feb 12 19:12:52 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:34d1:31b9:e8f2:3a27 on wlo1.
Feb 12 19:17:01 ctillman CRON[3122]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 12 19:17:25 ctillman kernel: [136482.894120] CPU3: Core temperature/speed normal
Feb 12 19:17:25 ctillman kernel: [136482.894121] CPU2: Core temperature/speed normal
Feb 12 19:17:25 ctillman kernel: [136482.894124] CPU1: Package temperature/speed normal
Feb 12 19:17:25 ctillman kernel: [136482.894125] CPU0: Package temperature/speed normal
Feb 12 19:17:25 ctillman kernel: [136482.894126] CPU2: Package temperature/speed normal
Feb 12 19:17:25 ctillman kernel: [136482.894128] CPU3: Package temperature/speed normal
Feb 12 19:20:36 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:34d1:31b9:e8f2:3a27 on wlo1.*.
Feb 12 19:20:36 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.*.
Feb 12 19:20:36 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:34d1:31b9:e8f2:3a27 on wlo1.
Feb 12 19:20:36 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:9002:5357:1d24:e14a on wlo1.
Feb 12 19:21:52 ctillman ntpd[713]: Deleting interface #105 wlo1, fd64:a651:689c:e600:9002:5357:1d24:e14a#123, interface stats: received=0, sent=0, dropped=0, active_time=6952 secs
Feb 12 19:22:25 ctillman kernel: [136782.867865] CPU3: Core temperature above threshold, cpu clock throttled (total events = 743943)
Feb 12 19:22:25 ctillman kernel: [136782.867867] CPU2: Core temperature above threshold, cpu clock throttled (total events = 743943)
Feb 12 19:22:25 ctillman kernel: [136782.867870] CPU1: Package temperature above threshold, cpu clock throttled (total events = 798184)
Feb 12 19:22:25 ctillman kernel: [136782.867872] CPU0: Package temperature above threshold, cpu clock throttled (total events = 798184)
Feb 12 19:22:25 ctillman kernel: [136782.867873] CPU2: Package temperature above threshold, cpu clock throttled (total events = 798184)
Feb 12 19:22:25 ctillman kernel: [136782.867885] CPU3: Package temperature above threshold, cpu clock throttled (total events = 798184)
Feb 12 19:22:25 ctillman kernel: [136782.869828] CPU3: Core temperature/speed normal
Feb 12 19:22:25 ctillman kernel: [136782.869829] CPU1: Package temperature/speed normal
Feb 12 19:22:25 ctillman kernel: [136782.869831] CPU0: Package temperature/speed normal
Feb 12 19:22:25 ctillman kernel: [136782.869832] CPU2: Core temperature/speed normal
Feb 12 19:22:25 ctillman kernel: [136782.869838] CPU2: Package temperature/speed normal
Feb 12 19:22:25 ctillman kernel: [136782.869839] CPU3: Package temperature/speed normal
Feb 12 19:22:47 ctillman dbus-daemon[1739]: Activating via systemd: service name='org.freedesktop.Notifications' unit='xfce4-notifyd.service'
Feb 12 19:22:47 ctillman systemd[1711]: Starting XFCE notifications service...
Feb 12 19:22:48 ctillman dbus-daemon[1739]: Successfully activated service 'org.freedesktop.Notifications'
Feb 12 19:22:48 ctillman systemd[1711]: Started XFCE notifications service.
Feb 12 19:25:17 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:34d1:31b9:e8f2:3a27 on wlo1.*.
Feb 12 19:25:17 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:34d1:31b9:e8f2:3a27 on wlo1.
Feb 12 19:27:25 ctillman kernel: [137082.856603] CPU3: Core temperature above threshold, cpu clock throttled (total events = 804180)
Feb 12 19:27:25 ctillman kernel: [137082.856604] CPU2: Core temperature above threshold, cpu clock throttled (total events = 804180)
Feb 12 19:27:25 ctillman kernel: [137082.856607] CPU1: Package temperature above threshold, cpu clock throttled (total events = 862662)
Feb 12 19:27:25 ctillman kernel: [137082.856608] CPU0: Package temperature above threshold, cpu clock throttled (total events = 862662)
Feb 12 19:27:25 ctillman kernel: [137082.856610] CPU2: Package temperature above threshold, cpu clock throttled (total events = 862662)
Feb 12 19:27:25 ctillman kernel: [137082.856621] CPU3: Package temperature above threshold, cpu clock throttled (total events = 862662)
Feb 12 19:27:25 ctillman kernel: [137082.857603] CPU3: Core temperature/speed normal
Feb 12 19:27:25 ctillman kernel: [137082.857604] CPU2: Core temperature/speed normal
Feb 12 19:27:25 ctillman kernel: [137082.857606] CPU0: Package temperature/speed normal
Feb 12 19:27:25 ctillman kernel: [137082.857608] CPU1: Package temperature/speed normal
Feb 12 19:27:25 ctillman kernel: [137082.857609] CPU2: Package temperature/speed normal
Feb 12 19:27:25 ctillman kernel: [137082.857612] CPU3: Package temperature/speed normal
Feb 12 19:28:55 ctillman NetworkManager[535]: <info>  [1486880935.6148] manager: sleep requested (sleeping: no  enabled: yes)
Feb 12 19:28:55 ctillman NetworkManager[535]: <info>  [1486880935.6148] manager: sleeping...
Feb 12 19:28:55 ctillman NetworkManager[535]: <info>  [1486880935.6150] manager: NetworkManager state is now ASLEEP
Feb 12 19:28:55 ctillman NetworkManager[535]: <info>  [1486880935.6155] device (wlo1): state change: activated -> deactivating (reason 'sleeping') [100 110 37]
Feb 12 19:28:55 ctillman NetworkManager[535]: <info>  [1486880935.7938] device (wlo1): state change: deactivating -> disconnected (reason 'sleeping') [110 30 37]
Feb 12 19:28:55 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:5053:35f2:9efd:9b88 on wlo1.
Feb 12 19:28:55 ctillman avahi-daemon[512]: Withdrawing address record for fd64:a651:689c:e600:6aa3:c4ff:fea6:b300 on wlo1.
Feb 12 19:28:55 ctillman avahi-daemon[512]: Leaving mDNS multicast group on interface wlo1.IPv6 with address fd64:a651:689c:e600:6aa3:c4ff:fea6:b300.
Feb 12 19:28:55 ctillman avahi-daemon[512]: Joining mDNS multicast group on interface wlo1.IPv6 with address fe80::6aa3:c4ff:fea6:b300.
Feb 12 19:28:55 ctillman avahi-daemon[512]: Registering new address record for fe80::6aa3:c4ff:fea6:b300 on wlo1.*.
Feb 12 19:28:55 ctillman avahi-daemon[512]: Withdrawing address record for fe80::6aa3:c4ff:fea6:b300 on wlo1.
Feb 12 19:28:55 ctillman avahi-daemon[512]: Leaving mDNS multicast group on interface wlo1.IPv6 with address fe80::6aa3:c4ff:fea6:b300.
Feb 12 19:28:55 ctillman avahi-daemon[512]: Interface wlo1.IPv6 no longer relevant for mDNS.
Feb 12 19:28:55 ctillman NetworkManager[535]: <info>  [1486880935.8611] dhcp4 (wlo1): canceled DHCP transaction, DHCP client pid 8739
Feb 12 19:28:55 ctillman NetworkManager[535]: <info>  [1486880935.8612] dhcp4 (wlo1): state changed bound -> done
Feb 12 19:28:55 ctillman avahi-daemon[512]: Withdrawing address record for 192.168.1.69 on wlo1.
Feb 12 19:28:55 ctillman avahi-daemon[512]: Leaving mDNS multicast group on interface wlo1.IPv4 with address 192.168.1.69.
Feb 12 19:28:55 ctillman kernel: [137172.841230] wlo1: deauthenticating from 64:a6:51:68:9c:ec by local choice (Reason: 3=DEAUTH_LEAVING)
Feb 12 19:28:55 ctillman dbus[515]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Feb 12 19:28:55 ctillman wpa_supplicant[625]: wlo1: CTRL-EVENT-DISCONNECTED bssid=64:a6:51:68:9c:ec reason=3 locally_generated=1
Feb 12 19:28:55 ctillman avahi-daemon[512]: Interface wlo1.IPv4 no longer relevant for mDNS.
Feb 12 19:28:55 ctillman NetworkManager[535]: <info>  [1486880935.9420] device (wlo1): set-hw-addr: set MAC address to A6:3E:6D:F1:C5:6E (scanning)
Feb 12 19:28:55 ctillman systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 12 19:28:56 ctillman kernel: [137173.057640] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
Feb 12 19:28:56 ctillman NetworkManager[535]: <warn>  [1486880936.1269] sup-iface[0x55cbe24976e0,wlo1]: connection disconnected (reason -3)
Feb 12 19:28:56 ctillman NetworkManager[535]: <info>  [1486880936.1300] device (wlo1): supplicant interface state: completed -> scanning
Feb 12 19:28:56 ctillman NetworkManager[535]: <info>  [1486880936.1326] device (wlo1): state change: disconnected -> unmanaged (reason 'sleeping') [30 10 37]
Feb 12 19:28:56 ctillman NetworkManager[535]: <info>  [1486880936.1340] device (wlo1): set-hw-addr: reset MAC address to 68:A3:C4:A6:B3:00 (unmanage)
Feb 12 19:28:56 ctillman dbus[515]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 12 19:28:56 ctillman nm-dispatcher: req:1 'connectivity-change': new request (2 scripts)
Feb 12 19:28:56 ctillman nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
Feb 12 19:28:56 ctillman systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 12 19:28:56 ctillman systemd[1]: Reached target Sleep.
Feb 12 19:28:56 ctillman systemd[1]: Starting Hybrid Suspend+Hibernate...
Feb 12 19:28:56 ctillman nm-dispatcher: req:2 'down' [wlo1]: new request (2 scripts)
Feb 12 19:28:56 ctillman wpa_supplicant[625]: nl80211: deinit ifname=wlo1 disabled_11b_rates=0
Feb 12 19:28:56 ctillman kernel: [137173.577370] PM: Hibernation mode set to 'suspend'
Feb 12 19:28:56 ctillman nm-dispatcher: req:2 'down' [wlo1]: start running ordered scripts...
Feb 12 19:28:56 ctillman systemd-sleep[5686]: Suspending system...
Feb 12 19:28:57 ctillman ntpd[713]: Deleting interface #98 wlo1, 192.168.1.69#123, interface stats: received=317, sent=333, dropped=0, active_time=10978 secs
Feb 12 19:28:57 ctillman ntpd[713]: 103.242.68.68 local addr 192.168.1.69 -> <null>
Feb 12 19:28:57 ctillman ntpd[713]: 203.99.128.34 local addr 192.168.1.69 -> <null>
Feb 12 19:28:57 ctillman ntpd[713]: 103.239.8.22 local addr 192.168.1.69 -> <null>
Feb 12 19:28:57 ctillman ntpd[713]: 203.99.128.48 local addr 192.168.1.69 -> <null>
Feb 12 19:28:57 ctillman ntpd[713]: 202.78.240.38 local addr 192.168.1.69 -> <null>
Feb 12 19:28:57 ctillman ntpd[713]: 130.217.226.49 local addr 192.168.1.69 -> <null>
Feb 12 19:28:57 ctillman ntpd[713]: 202.36.220.71 local addr 192.168.1.69 -> <null>
Feb 12 19:28:57 ctillman ntpd[713]: 122.252.184.186 local addr 192.168.1.69 -> <null>
Feb 12 19:28:57 ctillman ntpd[713]: 122.252.188.99 local addr 192.168.1.69 -> <null>
Feb 12 19:28:57 ctillman ntpd[713]: 130.217.226.51 local addr 192.168.1.69 -> <null>
Feb 12 19:28:57 ctillman ntpd[713]: 202.6.116.123 local addr 192.168.1.69 -> <null>
Feb 12 19:28:57 ctillman ntpd[713]: 130.217.226.50 local addr 192.168.1.69 -> <null>
Feb 12 19:28:57 ctillman ntpd[713]: 203.118.151.32 local addr 192.168.1.69 -> <null>
Feb 12 19:28:57 ctillman ntpd[713]: Deleting interface #102 wlo1, fe80::6aa3:c4ff:fea6:b300%3#123, interface stats: received=0, sent=0, dropped=0, active_time=10976 secs
Feb 12 19:28:57 ctillman ntpd[713]: Deleting interface #104 wlo1, fd64:a651:689c:e600:6aa3:c4ff:fea6:b300#123, interface stats: received=0, sent=0, dropped=0, active_time=10974 secs
Feb 12 19:28:57 ctillman ntpd[713]: Deleting interface #106 wlo1, fd64:a651:689c:e600:34d1:31b9:e8f2:3a27#123, interface stats: received=0, sent=0, dropped=0, active_time=4026 secs
Feb 12 19:28:57 ctillman ntpd[713]: Deleting interface #107 wlo1, fd64:a651:689c:e600:5053:35f2:9efd:9b88#123, interface stats: received=0, sent=0, dropped=0, active_time=966 secs
Feb 12 19:29:24 ctillman kernel: [137173.735800] PM: Syncing filesystems ... 
Feb 12 19:29:24 ctillman kernel: [137175.522199] done.
Feb 12 19:29:25 ctillman kernel: [137175.522202] Freezing user space processes ... (elapsed 0.079 seconds) done.
Feb 12 19:29:25 ctillman kernel: [137175.601434] PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
Feb 12 19:29:25 ctillman kernel: [137175.601437] PM: Marking nosave pages: [mem 0x0009e000-0x000fffff]
Feb 12 19:29:25 ctillman kernel: [137175.601442] PM: Marking nosave pages: [mem 0xac6be000-0xacffefff]
Feb 12 19:29:25 ctillman kernel: [137175.601520] PM: Marking nosave pages: [mem 0xad000000-0xffffffff]
Feb 12 19:29:25 ctillman kernel: [137175.603563] PM: Basic memory bitmaps created
Feb 12 19:29:25 ctillman kernel: [137175.603564] PM: Preallocating image memory... done (allocated 404398 pages)
Feb 12 19:29:25 ctillman kernel: [137186.513725] PM: Allocated 1617592 kbytes in 10.91 seconds (148.26 MB/s)
Feb 12 19:29:25 ctillman kernel: [137186.513726] Freezing remaining freezable tasks ... (elapsed 0.003 seconds) done.
Feb 12 19:29:25 ctillman kernel: [137186.517311] Suspending console(s) (use no_console_suspend to debug)
Feb 12 19:29:25 ctillman kernel: [137186.518811] ACPI : EC: event blocked
Feb 12 19:29:25 ctillman kernel: [137186.722963] PM: freeze of devices complete after 205.657 msecs
Feb 12 19:29:25 ctillman kernel: [137186.742807] PM: late freeze of devices complete after 19.838 msecs
Feb 12 19:29:25 ctillman kernel: [137186.743540] ACPI : EC: interrupt blocked
Feb 12 19:29:25 ctillman kernel: [137186.744696] PM: noirq freeze of devices complete after 1.883 msecs
Feb 12 19:29:25 ctillman kernel: [137186.744698] Disabling non-boot CPUs ...
Feb 12 19:29:25 ctillman kernel: [137186.745245] Broke affinity for irq 16
Feb 12 19:29:25 ctillman kernel: [137186.746302] smpboot: CPU 1 is now offline
Feb 12 19:29:25 ctillman kernel: [137186.747989] Broke affinity for irq 16
Feb 12 19:29:25 ctillman kernel: [137186.748016] Broke affinity for irq 31
Feb 12 19:29:25 ctillman kernel: [137186.748019] Broke affinity for irq 34
Feb 12 19:29:25 ctillman kernel: [137186.749055] smpboot: CPU 2 is now offline
Feb 12 19:29:25 ctillman kernel: [137186.750003] Broke affinity for irq 1
Feb 12 19:29:25 ctillman kernel: [137186.750013] Broke affinity for irq 9
Feb 12 19:29:25 ctillman kernel: [137186.750019] Broke affinity for irq 12
Feb 12 19:29:25 ctillman kernel: [137186.750024] Broke affinity for irq 16
Feb 12 19:29:25 ctillman kernel: [137186.750044] Broke affinity for irq 31
Feb 12 19:29:25 ctillman kernel: [137186.750047] Broke affinity for irq 34
Feb 12 19:29:25 ctillman kernel: [137186.751089] smpboot: CPU 3 is now offline
Feb 12 19:29:25 ctillman kernel: [137186.751668] PM: Creating hibernation image:
Feb 12 19:29:25 ctillman kernel: [137186.894061] PM: Need to copy 402304 pages
Feb 12 19:29:25 ctillman kernel: [137186.894066] PM: Normal pages needed: 402304 + 1024, available pages: 629372
Feb 12 19:29:25 ctillman kernel: [137187.650256] PM: Hibernation image created (402304 pages copied)
Feb 12 19:29:25 ctillman kernel: [137186.753541] Suspended for 0.225 seconds
Feb 12 19:29:25 ctillman kernel: [137186.753623] Enabling non-boot CPUs ...
Feb 12 19:29:25 ctillman kernel: [137186.753730] x86: Booting SMP configuration:
Feb 12 19:29:25 ctillman kernel: [137186.753732] smpboot: Booting Node 0 Processor 1 APIC 0x1
Feb 12 19:29:25 ctillman kernel: [137186.756832]  cache: parent cpu1 should not be sleeping
Feb 12 19:29:25 ctillman kernel: [137186.757407] CPU1 is up
Feb 12 19:29:25 ctillman kernel: [137186.757525] smpboot: Booting Node 0 Processor 2 APIC 0x2
Feb 12 19:29:25 ctillman kernel: [137186.760461]  cache: parent cpu2 should not be sleeping
Feb 12 19:29:25 ctillman kernel: [137186.761131] CPU2 is up
Feb 12 19:29:25 ctillman kernel: [137186.761230] smpboot: Booting Node 0 Processor 3 APIC 0x3
Feb 12 19:29:25 ctillman kernel: [137186.764034]  cache: parent cpu3 should not be sleeping
Feb 12 19:29:25 ctillman kernel: [137186.764809] CPU3 is up
Feb 12 19:29:25 ctillman kernel: [137186.771072] ACPI : EC: interrupt unblocked
Feb 12 19:29:25 ctillman kernel: [137186.771233] PM: noirq thaw of devices complete after 0.487 msecs
Feb 12 19:29:25 ctillman kernel: [137186.789109] PM: early thaw of devices complete after 17.844 msecs
Feb 12 19:29:25 ctillman kernel: [137186.789343] ACPI : EC: event unblocked
Feb 12 19:29:25 ctillman kernel: [137186.836934] rtc_cmos 00:03: System wakeup disabled by ACPI
Feb 12 19:29:25 ctillman kernel: [137186.929986] PM: thaw of devices complete after 140.884 msecs
Feb 12 19:29:25 ctillman kernel: [137186.930118] PM: writing image.
Feb 12 19:29:25 ctillman kernel: [137186.932868] r8169 0000:26:00.0 enp38s0: link down
Feb 12 19:29:25 ctillman kernel: [137187.123813] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 12 19:29:25 ctillman kernel: [137187.123851] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 12 19:29:25 ctillman kernel: [137187.124896] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 12 19:29:25 ctillman kernel: [137187.126254] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 12 19:29:25 ctillman kernel: [137187.126429] ata1.00: configured for UDMA/100
Feb 12 19:29:25 ctillman kernel: [137187.127893] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 12 19:29:25 ctillman kernel: [137187.130326] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 12 19:29:25 ctillman kernel: [137187.130337] ata2.00: configured for UDMA/100
Feb 12 19:29:25 ctillman kernel: [137187.227125] PM: Using 3 thread(s) for compression.
Feb 12 19:29:25 ctillman kernel: [137187.227125] PM: Compressing and saving image data (403090 pages)...
Feb 12 19:29:25 ctillman kernel: [137187.227153] PM: Image saving progress:   0%
Feb 12 19:29:25 ctillman kernel: [137187.568430] PM: Image saving progress:  10%
Feb 12 19:29:25 ctillman kernel: [137187.850651] PM: Image saving progress:  20%
Feb 12 19:29:25 ctillman kernel: [137188.146698] PM: Image saving progress:  30%
Feb 12 19:29:25 ctillman kernel: [137188.688473] PM: Image saving progress:  40%
Feb 12 19:29:25 ctillman kernel: [137189.180544] PM: Image saving progress:  50%
Feb 12 19:29:25 ctillman kernel: [137189.786011] PM: Image saving progress:  60%
Feb 12 19:29:25 ctillman kernel: [137190.337637] PM: Image saving progress:  70%
Feb 12 19:29:25 ctillman kernel: [137191.138095] PM: Image saving progress:  80%
Feb 12 19:29:25 ctillman kernel: [137191.621181] PM: Image saving progress:  90%
Feb 12 19:29:25 ctillman kernel: [137192.794430] PM: Image saving done.
Feb 12 19:29:25 ctillman kernel: [137192.794440] PM: Wrote 1612360 kbytes in 5.56 seconds (289.99 MB/s)
Feb 12 19:29:25 ctillman kernel: [137192.794839] PM: S
Feb 12 19:29:25 ctillman kernel: [137192.827693] |
Feb 12 19:29:25 ctillman kernel: [137192.935438] Suspending console(s) (use no_console_suspend to debug)
Feb 12 19:29:25 ctillman kernel: [137192.935899] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Feb 12 19:29:25 ctillman kernel: [137192.936021] sd 0:0:0:0: [sda] Stopping disk
Feb 12 19:29:25 ctillman kernel: [137192.985802] ACPI : EC: event blocked
Feb 12 19:29:25 ctillman kernel: [137193.575630] PM: suspend of devices complete after 640.086 msecs
Feb 12 19:29:25 ctillman kernel: [137193.596214] PM: late suspend of devices complete after 20.579 msecs
Feb 12 19:29:25 ctillman kernel: [137193.596874] ACPI : EC: interrupt blocked
Feb 12 19:29:25 ctillman kernel: [137193.597383] r8169 0000:26:00.0: System wakeup enabled by ACPI
Feb 12 19:29:25 ctillman kernel: [137193.597639] ehci-pci 0000:00:1d.0: System wakeup enabled by ACPI
Feb 12 19:29:25 ctillman kernel: [137193.597902] ehci-pci 0000:00:1a.0: System wakeup enabled by ACPI
Feb 12 19:29:25 ctillman kernel: [137193.636127] PM: noirq suspend of devices complete after 39.910 msecs
Feb 12 19:29:25 ctillman kernel: [137193.636806] ACPI: Preparing to enter system sleep state S3
Feb 12 19:29:25 ctillman kernel: [137193.638394] ACPI : EC: EC stopped
Feb 12 19:29:25 ctillman kernel: [137193.638395] PM: Saving platform NVS memory
Feb 12 19:29:25 ctillman kernel: [137193.638411] Disabling non-boot CPUs ...
Feb 12 19:29:25 ctillman kernel: [137193.638901] Broke affinity for irq 16
Feb 12 19:29:25 ctillman kernel: [137193.639953] smpboot: CPU 1 is now offline
Feb 12 19:29:25 ctillman kernel: [137193.641242] Broke affinity for irq 16
Feb 12 19:29:25 ctillman kernel: [137193.641266] Broke affinity for irq 31
Feb 12 19:29:25 ctillman kernel: [137193.641269] Broke affinity for irq 34
Feb 12 19:29:25 ctillman kernel: [137193.642299] smpboot: CPU 2 is now offline
Feb 12 19:29:25 ctillman kernel: [137193.643575] Broke affinity for irq 1
Feb 12 19:29:25 ctillman kernel: [137193.643595] Broke affinity for irq 9
Feb 12 19:29:25 ctillman kernel: [137193.643600] Broke affinity for irq 12
Feb 12 19:29:25 ctillman kernel: [137193.643605] Broke affinity for irq 16
Feb 12 19:29:25 ctillman kernel: [137193.643624] Broke affinity for irq 31
Feb 12 19:29:25 ctillman kernel: [137193.643626] Broke affinity for irq 34
Feb 12 19:29:25 ctillman kernel: [137193.644662] smpboot: CPU 3 is now offline
Feb 12 19:29:25 ctillman kernel: [137193.646220] ACPI: Low-level resume complete
Feb 12 19:29:25 ctillman kernel: [137193.646270] ACPI : EC: EC started
Feb 12 19:29:25 ctillman kernel: [137193.646270] PM: Restoring platform NVS memory
Feb 12 19:29:25 ctillman kernel: [137193.646565] Suspended for 4.107 seconds
Feb 12 19:29:25 ctillman kernel: [137193.646644] Enabling non-boot CPUs ...
Feb 12 19:29:25 ctillman kernel: [137193.646792] x86: Booting SMP configuration:
Feb 12 19:29:25 ctillman kernel: [137193.646795] smpboot: Booting Node 0 Processor 1 APIC 0x1
Feb 12 19:29:25 ctillman kernel: [137193.649814]  cache: parent cpu1 should not be sleeping
Feb 12 19:29:25 ctillman kernel: [137193.650182] CPU1 is up
Feb 12 19:29:25 ctillman kernel: [137193.650322] smpboot: Booting Node 0 Processor 2 APIC 0x2
Feb 12 19:29:25 ctillman kernel: [137193.653192]  cache: parent cpu2 should not be sleeping
Feb 12 19:29:25 ctillman kernel: [137193.653608] CPU2 is up
Feb 12 19:29:25 ctillman kernel: [137193.653778] smpboot: Booting Node 0 Processor 3 APIC 0x3
Feb 12 19:29:25 ctillman kernel: [137193.656726]  cache: parent cpu3 should not be sleeping
Feb 12 19:29:25 ctillman kernel: [137193.657170] CPU3 is up
Feb 12 19:29:25 ctillman kernel: [137193.660630] ACPI: Waking up from system sleep state S3
Feb 12 19:29:25 ctillman kernel: [137193.678025] acpi LNXPOWER:02: Turning OFF
Feb 12 19:29:25 ctillman kernel: [137193.678065] acpi LNXPOWER:01: Turning OFF
Feb 12 19:29:25 ctillman kernel: [137193.678231] ACPI : EC: interrupt unblocked
Feb 12 19:29:25 ctillman kernel: [137193.697917] ehci-pci 0000:00:1d.0: System wakeup disabled by ACPI
Feb 12 19:29:25 ctillman kernel: [137193.698109] ehci-pci 0000:00:1a.0: System wakeup disabled by ACPI
Feb 12 19:29:25 ctillman kernel: [137193.745819] PM: noirq resume of devices complete after 67.727 msecs
Feb 12 19:29:25 ctillman kernel: [137193.746138] PM: early resume of devices complete after 0.281 msecs
Feb 12 19:29:25 ctillman kernel: [137193.746215] ACPI : EC: event unblocked
Feb 12 19:29:25 ctillman kernel: [137193.746648] sd 0:0:0:0: [sda] Starting disk
Feb 12 19:29:25 ctillman kernel: [137193.746793] r8169 0000:26:00.0: System wakeup disabled by ACPI
Feb 12 19:29:25 ctillman kernel: [137193.789877] rtc_cmos 00:03: System wakeup disabled by ACPI
Feb 12 19:29:25 ctillman kernel: [137193.885944] r8169 0000:26:00.0 enp38s0: link down
Feb 12 19:29:25 ctillman kernel: [137193.989694] usb 2-1.4: reset high-speed USB device number 4 using ehci-pci
Feb 12 19:29:25 ctillman kernel: [137194.072681] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Feb 12 19:29:25 ctillman kernel: [137194.074004] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 12 19:29:25 ctillman kernel: [137194.075984] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 12 19:29:25 ctillman kernel: [137194.075992] ata2.00: configured for UDMA/100
Feb 12 19:29:25 ctillman kernel: [137194.177708] usb 2-1.6: reset full-speed USB device number 5 using ehci-pci
Feb 12 19:29:25 ctillman kernel: [137194.485024] PM: resume of devices complete after 738.940 msecs
Feb 12 19:29:25 ctillman kernel: [137194.485114] usb 2-1.6:1.0: rebind failed: -517
Feb 12 19:29:25 ctillman kernel: [137194.485119] usb 2-1.6:1.1: rebind failed: -517
Feb 12 19:29:25 ctillman kernel: [137195.231697] psmouse serio4: synaptics: queried max coordinates: x [..5756], y [..4876]
Feb 12 19:29:25 ctillman kernel: [137196.289569] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Feb 12 19:29:25 ctillman kernel: [137196.290708] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 12 19:29:25 ctillman kernel: [137196.292029] ata1.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04)
Feb 12 19:29:25 ctillman kernel: [137196.292172] ata1.00: configured for UDMA/100
Feb 12 19:29:25 ctillman kernel: [137196.412851] PM: Basic memory bitmaps freed
Feb 12 19:29:25 ctillman kernel: [137196.412866] Restarting tasks ... 
Feb 12 19:29:25 ctillman kernel: [137196.413180] acpi PNP0501:00: Still not present
Feb 12 19:29:25 ctillman kernel: [137196.415085] done.
Feb 12 19:29:25 ctillman kernel: [137196.468799] video LNXVIDEO:00: Restoring backlight state
Feb 12 19:29:25 ctillman kernel: [137196.469355] video LNXVIDEO:01: Restoring backlight state
Feb 12 19:29:28 ctillman systemd-sleep[5686]: System resumed.
Feb 12 19:29:28 ctillman rtkit-daemon[1906]: The canary thread is apparently starving. Taking action.
Feb 12 19:29:28 ctillman systemd[1711]: Time has been changed
Feb 12 19:29:28 ctillman rtkit-daemon[1906]: Demoting known real-time threads.
Feb 12 19:29:28 ctillman systemd[1]: Time has been changed
Feb 12 19:29:28 ctillman rtkit-daemon[1906]: Successfully demoted thread 1955 of process 1905 (n/a).
Feb 12 19:29:28 ctillman systemd[1]: apt-daily.timer: Adding 9h 3min 48.373330s random time.
Feb 12 19:29:28 ctillman rtkit-daemon[1906]: Successfully demoted thread 1954 of process 1905 (n/a).
Feb 12 19:29:28 ctillman rtkit-daemon[1906]: Successfully demoted thread 1905 of process 1905 (n/a).
Feb 12 19:29:28 ctillman rtkit-daemon[1906]: Demoted 3 threads.
Feb 12 19:29:28 ctillman bluetoothd[496]: Failed to obtain handles for "Service Changed" characteristic
Feb 12 19:29:28 ctillman bluetoothd[496]: Sap driver initialization failed.
Feb 12 19:29:28 ctillman bluetoothd[496]: sap-server: Operation not permitted (1)
Feb 12 19:29:36 ctillman systemd[1]: bluetooth.target: Unit not needed anymore. Stopping.
Feb 12 19:29:36 ctillman systemd[1]: Stopped target Bluetooth.
Feb 12 19:29:36 ctillman systemd[1]: Starting Load/Save RF Kill Switch Status...
Feb 12 19:29:37 ctillman systemd[1]: Started Load/Save RF Kill Switch Status.
Feb 12 19:29:44 ctillman systemd-sleep[5686]: /dev/sda:
Feb 12 19:29:44 ctillman systemd-sleep[5686]:  setting Advanced Power Management level to 0x80 (128)
Feb 12 19:29:44 ctillman systemd-sleep[5686]:  APM_level#011= 128
Feb 12 19:29:45 ctillman systemd-sleep[5686]: /dev/sda:
Feb 12 19:29:45 ctillman systemd-sleep[5686]:  setting standby to 36 (3 minutes)
Feb 12 19:29:45 ctillman systemd[1]: Started Hybrid Suspend+Hibernate.
Feb 12 19:29:45 ctillman systemd[1]: sleep.target: Unit not needed anymore. Stopping.
Feb 12 19:29:45 ctillman systemd[1]: Stopped target Sleep.
Feb 12 19:29:45 ctillman systemd[1]: Reached target Hybrid Suspend+Hibernate.
Feb 12 19:29:45 ctillman systemd[1]: hybrid-sleep.target: Unit is bound to inactive unit systemd-hybrid-sleep.service. Stopping, too.
Feb 12 19:29:45 ctillman systemd[1]: Stopped target Hybrid Suspend+Hibernate.
Feb 12 19:29:45 ctillman systemd[1]: Started Run anacron jobs at resume.
Feb 12 19:29:45 ctillman NetworkManager[535]: <info>  [1486880985.5972] manager: wake requested (sleeping: yes  enabled: yes)
Feb 12 19:29:45 ctillman NetworkManager[535]: <info>  [1486880985.6101] manager: waking up...
Feb 12 19:29:46 ctillman NetworkManager[535]: <info>  [1486880986.5349] device (enp38s0): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
Feb 12 19:29:48 ctillman NetworkManager[535]: <info>  [1486880988.3723] device (enp38s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 12 19:29:48 ctillman kernel: [137221.017219] IPv6: ADDRCONF(NETDEV_UP): enp38s0: link is not ready
Feb 12 19:29:48 ctillman ModemManager[513]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.3/0000:25:00.0': not supported by any plugin
Feb 12 19:29:48 ctillman kernel: [137221.163398] r8169 0000:26:00.0 enp38s0: link down
Feb 12 19:29:48 ctillman kernel: [137221.163473] IPv6: ADDRCONF(NETDEV_UP): enp38s0: link is not ready
Feb 12 19:29:48 ctillman ModemManager[513]: <info>  Couldn't check support for device at '/sys/devices/pci0000:00/0000:00:1c.5/0000:26:00.0': not supported by any plugin
Feb 12 19:29:48 ctillman NetworkManager[535]: <info>  [1486880988.7034] device (wlo1): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Feb 12 19:29:48 ctillman kernel: [137221.348386] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
Feb 12 19:29:48 ctillman kernel: [137221.496842] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
Feb 12 19:29:48 ctillman NetworkManager[535]: <info>  [1486880988.9450] device (wlo1): set-hw-addr: set MAC address to A6:3E:6D:F1:C5:6E (scanning)
Feb 12 19:29:49 ctillman kernel: [137221.724618] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
Feb 12 19:29:49 ctillman NetworkManager[535]: <info>  [1486880989.2985] manager: NetworkManager state is now DISCONNECTED
Feb 12 19:29:52 ctillman NetworkManager[535]: <info>  [1486880992.3825] sup-iface[0x55cbe2497210,wlo1]: supports 4 scan SSIDs
Feb 12 19:29:52 ctillman NetworkManager[535]: <info>  [1486880992.4001] device (wlo1): supplicant interface state: starting -> ready
Feb 12 19:29:52 ctillman kernel: [137225.044757] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
Feb 12 19:29:52 ctillman NetworkManager[535]: <info>  [1486880992.4003] device (wlo1): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Feb 12 19:29:53 ctillman wpa_supplicant[625]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Feb 12 19:29:55 ctillman wpa_supplicant[625]: wlo1: Reject scan trigger since one is already pending
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.1653] device (wlo1): supplicant interface state: ready -> inactive
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.1693] policy: auto-activating connection 'cs_and_ct'
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.1716] device (wlo1): Activation: starting connection 'cs_and_ct' (c9f9b725-705b-4ca6-a624-4ebf3dab985c)
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.1720] device (wlo1): state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.1723] manager: NetworkManager state is now CONNECTING
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.2140] device (wlo1): set-hw-addr: set-cloned MAC address to 68:A3:C4:A6:B3:00 (permanent)
Feb 12 19:29:58 ctillman kernel: [137230.999944] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.3605] device (wlo1): supplicant interface state: inactive -> disabled
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.3610] device (wlo1): state change: prepare -> config (reason 'none') [40 50 0]
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.3615] device (wlo1): Activation: (wifi) access point 'cs_and_ct' has security, but secrets are required.
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.3616] device (wlo1): state change: config -> need-auth (reason 'none') [50 60 0]
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.7451] device (wlo1): supplicant interface state: disabled -> inactive
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.7528] device (wlo1): state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.7542] device (wlo1): state change: prepare -> config (reason 'none') [40 50 0]
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.7549] device (wlo1): Activation: (wifi) connection 'cs_and_ct' has security, and secrets exist.  No new secrets needed.
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.7550] Config: added 'ssid' value 'cs_and_ct'
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.7550] Config: added 'scan_ssid' value '1'
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.7551] Config: added 'key_mgmt' value 'WPA-PSK'
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.7552] Config: added 'psk' value '<omitted>'
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.7581] sup-iface[0x55cbe2497210,wlo1]: config: set interface ap_scan to 1
Feb 12 19:29:58 ctillman wpa_supplicant[625]: wlo1: SME: Trying to authenticate with 64:a6:51:68:9c:ec (SSID='cs_and_ct' freq=2462 MHz)
Feb 12 19:29:58 ctillman kernel: [137231.419852] wlo1: authenticate with 64:a6:51:68:9c:ec
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.7935] device (wlo1): supplicant interface state: inactive -> authenticating
Feb 12 19:29:58 ctillman wpa_supplicant[625]: wlo1: Trying to associate with 64:a6:51:68:9c:ec (SSID='cs_and_ct' freq=2462 MHz)
Feb 12 19:29:58 ctillman kernel: [137231.436398] wlo1: send auth to 64:a6:51:68:9c:ec (try 1/3)
Feb 12 19:29:58 ctillman kernel: [137231.437837] wlo1: authenticated
Feb 12 19:29:58 ctillman kernel: [137231.438598] wlo1: associate with 64:a6:51:68:9c:ec (try 1/3)
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.8002] device (wlo1): supplicant interface state: authenticating -> associating
Feb 12 19:29:58 ctillman kernel: [137231.446528] wlo1: RX AssocResp from 64:a6:51:68:9c:ec (capab=0x411 status=0 aid=4)
Feb 12 19:29:58 ctillman kernel: [137231.446546] wlo1: AP has invalid WMM params (AIFSN=1 for ACI 2), will use 2
Feb 12 19:29:58 ctillman kernel: [137231.446548] wlo1: AP has invalid WMM params (AIFSN=1 for ACI 3), will use 2
Feb 12 19:29:58 ctillman wpa_supplicant[625]: wlo1: Associated with 64:a6:51:68:9c:ec
Feb 12 19:29:58 ctillman kernel: [137231.447546] wlo1: associated
Feb 12 19:29:58 ctillman kernel: [137231.447610] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.8099] device (wlo1): supplicant interface state: associating -> 4-way handshake
Feb 12 19:29:58 ctillman wpa_supplicant[625]: wlo1: WPA: Key negotiation completed with 64:a6:51:68:9c:ec [PTK=CCMP GTK=TKIP]
Feb 12 19:29:58 ctillman wpa_supplicant[625]: wlo1: CTRL-EVENT-CONNECTED - Connection to 64:a6:51:68:9c:ec completed [id=0 id_str=]
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.9145] device (wlo1): supplicant interface state: 4-way handshake -> completed
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.9146] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'cs_and_ct'.
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.9153] device (wlo1): state change: config -> ip-config (reason 'none') [50 70 0]
Feb 12 19:29:58 ctillman NetworkManager[535]: <info>  [1486880998.9792] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 seconds)
Feb 12 19:30:01 ctillman NetworkManager[535]: <info>  [1486881001.6623] dhcp4 (wlo1): dhclient started with pid 5904
Feb 12 19:30:03 ctillman systemd-udevd[5903]: Process '/sbin/crda' failed with exit code 249.
Feb 12 19:30:03 ctillman wpa_supplicant[625]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Feb 12 19:30:03 ctillman ntpd[713]: bind(23) AF_INET6 fe80::6aa3:c4ff:fea6:b300%3#123 flags 0x11 failed: Cannot assign requested address
Feb 12 19:30:03 ctillman ntpd[713]: unable to create socket on wlo1 (108) for fe80::6aa3:c4ff:fea6:b300%3#123
Feb 12 19:30:03 ctillman ntpd[713]: failed to init interface for address fe80::6aa3:c4ff:fea6:b300%3
Feb 12 19:30:03 ctillman avahi-daemon[512]: Joining mDNS multicast group on interface wlo1.IPv6 with address fe80::6aa3:c4ff:fea6:b300.
Feb 12 19:30:03 ctillman avahi-daemon[512]: New relevant interface wlo1.IPv6 for mDNS.
Feb 12 19:30:03 ctillman avahi-daemon[512]: Registering new address record for fe80::6aa3:c4ff:fea6:b300 on wlo1.*.
Feb 12 19:30:04 ctillman dhclient[5904]: DHCPREQUEST of 192.168.1.69 on wlo1 to 255.255.255.255 port 67
Feb 12 19:30:04 ctillman dhclient[5904]: DHCPACK of 192.168.1.69 from 192.168.1.254
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.0041] dhcp4 (wlo1):   address 192.168.1.69
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.0042] dhcp4 (wlo1):   plen 24 (255.255.255.0)
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.0042] dhcp4 (wlo1):   gateway 192.168.1.254
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.0042] dhcp4 (wlo1):   server identifier 192.168.1.254
Feb 12 19:30:05 ctillman avahi-daemon[512]: Joining mDNS multicast group on interface wlo1.IPv4 with address 192.168.1.69.
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.0043] dhcp4 (wlo1):   lease time 86400
Feb 12 19:30:05 ctillman avahi-daemon[512]: New relevant interface wlo1.IPv4 for mDNS.
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.0043] dhcp4 (wlo1):   nameserver '192.168.1.254'
Feb 12 19:30:05 ctillman avahi-daemon[512]: Registering new address record for 192.168.1.69 on wlo1.IPv4.
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.0043] dhcp4 (wlo1):   nameserver '192.168.1.254'
Feb 12 19:30:05 ctillman avahi-daemon[512]: Leaving mDNS multicast group on interface wlo1.IPv6 with address fe80::6aa3:c4ff:fea6:b300.
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.0044] dhcp4 (wlo1): state changed unknown -> bound
Feb 12 19:30:05 ctillman avahi-daemon[512]: Joining mDNS multicast group on interface wlo1.IPv6 with address fd64:a651:689c:e600:5053:35f2:9efd:9b88.
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.0085] device (wlo1): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Feb 12 19:30:05 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:5053:35f2:9efd:9b88 on wlo1.*.
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.0097] device (wlo1): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Feb 12 19:30:05 ctillman avahi-daemon[512]: Withdrawing address record for fe80::6aa3:c4ff:fea6:b300 on wlo1.
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.0105] device (wlo1): state change: secondaries -> activated (reason 'none') [90 100 0]
Feb 12 19:30:05 ctillman dbus[515]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.0109] manager: NetworkManager state is now CONNECTED_LOCAL
Feb 12 19:30:05 ctillman systemd[1]: Starting Network Manager Script Dispatcher Service...
Feb 12 19:30:05 ctillman dhclient[5904]: bound to 192.168.1.69 -- renewal in 33763 seconds.
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.3320] manager: NetworkManager state is now CONNECTED_GLOBAL
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.3323] policy: set 'cs_and_ct' (wlo1) as default for IPv4 routing and DNS
Feb 12 19:30:05 ctillman NetworkManager[535]: <info>  [1486881005.4325] device (wlo1): Activation: successful, device activated.
Feb 12 19:30:05 ctillman avahi-daemon[512]: Registering new address record for fd64:a651:689c:e600:6aa3:c4ff:fea6:b300 on wlo1.*.
Feb 12 19:30:06 ctillman dbus[515]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 12 19:30:06 ctillman systemd[1]: Started Network Manager Script Dispatcher Service.
Feb 12 19:30:06 ctillman nm-dispatcher: req:1 'connectivity-change': new request (2 scripts)
Feb 12 19:30:06 ctillman nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
Feb 12 19:30:06 ctillman nm-dispatcher: req:2 'up' [wlo1]: new request (2 scripts)
Feb 12 19:30:06 ctillman nm-dispatcher: req:2 'up' [wlo1]: start running ordered scripts...
Feb 12 19:30:07 ctillman ntpd[713]: Listen normally on 109 wlo1 192.168.1.69:123
Feb 12 19:30:07 ctillman ntpd[713]: Listen normally on 110 wlo1 [fd64:a651:689c:e600:5053:35f2:9efd:9b88]:123
Feb 12 19:30:07 ctillman ntpd[713]: Listen normally on 111 wlo1 [fd64:a651:689c:e600:6aa3:c4ff:fea6:b300]:123
Feb 12 19:30:07 ctillman ntpd[713]: Listen normally on 112 wlo1 [fe80::6aa3:c4ff:fea6:b300%3]:123
Feb 12 19:30:09 ctillman kernel: [137242.353789] usb 1-1.3: new full-speed USB device number 9 using ehci-pci
Feb 12 19:30:09 ctillman kernel: [137242.466685] usb 1-1.3: New USB device found, idVendor=046d, idProduct=c52b
Feb 12 19:30:09 ctillman kernel: [137242.466691] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 12 19:30:09 ctillman kernel: [137242.466695] usb 1-1.3: Product: USB Receiver
Feb 12 19:30:09 ctillman kernel: [137242.466697] usb 1-1.3: Manufacturer: Logitech
Feb 12 19:30:09 ctillman kernel: [137242.478249] logitech-djreceiver 0003:046D:C52B.002F: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:1a.0-1.3/input2
Feb 12 19:30:09 ctillman kernel: [137242.605959] input: Logitech M215 2nd Gen as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.2/0003:046D:C52B.002F/0003:046D:401B.0030/input/input111
Feb 12 19:30:09 ctillman kernel: [137242.606247] logitech-hidpp-device 0003:046D:401B.0030: input,hidraw1: USB HID v1.11 Mouse [Logitech M215 2nd Gen] on usb-0000:00:1a.0-1.3:1
Feb 12 19:30:12 ctillman mtp-probe: checking bus 1, device 9: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3"
Feb 12 19:30:12 ctillman mtp-probe: bus: 1, device: 9 was not an MTP device
Feb 12 19:30:26 ctillman systemd[1]: Reloading OpenBSD Secure Shell server.
Feb 12 19:30:27 ctillman systemd[1]: Reloaded OpenBSD Secure Shell server.
Feb 12 19:30:27 ctillman systemd[1]: Reloading.
Feb 12 19:30:29 ctillman sshd[604]: Could not load host key: /etc/ssh/ssh_host_dsa_key
Feb 12 19:30:39 ctillman systemd[1]: apt-daily.timer: Adding 5h 13min 59.152350s random time.
Feb 12 19:30:40 ctillman systemd[1]: Reloading OpenBSD Secure Shell server.
Feb 12 19:30:40 ctillman sshd[604]: Could not load host key: /etc/ssh/ssh_host_dsa_key
Feb 12 19:30:40 ctillman systemd[1]: Reloaded OpenBSD Secure Shell server.
Feb 12 19:30:40 ctillman systemd[1]: Reloading.
Feb 12 19:30:40 ctillman systemd[1]: apt-daily.timer: Adding 7h 13min 20.177634s random time.
Feb 12 19:30:45 ctillman wpa_supplicant[625]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Feb 12 19:31:11 ctillman systemd[1]: Created slice User Slice of root.
Feb 12 19:31:12 ctillman systemd[1]: Starting User Manager for UID 0...
Feb 12 19:31:12 ctillman systemd[1]: Started Session 46 of user root.
Feb 12 19:31:12 ctillman systemd[6193]: Reached target Timers.
Feb 12 19:31:12 ctillman systemd[6193]: Reached target Paths.
Feb 12 19:31:12 ctillman systemd[6193]: Starting D-Bus User Message Bus Socket.
Feb 12 19:31:12 ctillman systemd[6193]: Listening on D-Bus User Message Bus Socket.
Feb 12 19:31:12 ctillman systemd[6193]: Reached target Sockets.
Feb 12 19:31:12 ctillman systemd[6193]: Reached target Basic System.
Feb 12 19:31:12 ctillman systemd[6193]: Reached target Default.
Feb 12 19:31:12 ctillman systemd[6193]: Startup finished in 395ms.
Feb 12 19:31:12 ctillman systemd[1]: Started User Manager for UID 0.
Feb 12 19:31:16 ctillman systemd[1]: Time has been changed
Feb 12 19:31:16 ctillman systemd[6193]: Time has been changed
Feb 12 19:31:16 ctillman systemd[1711]: Time has been changed
Feb 12 19:31:16 ctillman systemd[1]: apt-daily.timer: Adding 8h 40min 10.661216s random time.
Feb 12 19:31:16 ctillman ntpd[713]: receive: Unexpected origin timestamp 0xdc4a7fb4.2f3f57bc does not match aorg 0000000000.00000000 from server@103.242.68.68 xmt 0xdc4a7fb4.619ffc0f
Feb 12 19:31:26 ctillman ntpd[713]: Soliciting pool server 203.97.213.52
Feb 12 19:31:27 ctillman ntpd[713]: Soliciting pool server 103.242.68.69
Feb 12 19:31:28 ctillman ntpd[713]: Soliciting pool server 103.242.70.4
Feb 12 19:31:29 ctillman ntpd[713]: Soliciting pool server 2407:f100:0:4::3

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Fwd: coretemp seems to reset immediately
  2017-02-15 10:00 ` Fwd: coretemp seems to reset immediately Chris Tillman
@ 2017-02-15 10:48   ` Guenter Roeck
  2017-02-15 17:12     ` Chris Tillman
  0 siblings, 1 reply; 4+ messages in thread
From: Guenter Roeck @ 2017-02-15 10:48 UTC (permalink / raw)
  To: Chris Tillman, linux-hwmon

On 02/15/2017 02:00 AM, Chris Tillman wrote:
> Hi,
>
> I had the awful experience of having my computer fry before my eyes
> the other day. It was running quite hot (building llvm), and it
> stopped accepting mouse inputs. I tried to regain control, and after
> 20 seconds or so it switched me to virtual console 1. But very shortly
> after that it died, and now it won't even start to boot.
>
> Anyway, the reason I'm writing: I retrieved the disk out of it, and on
> another machine, looked through the syslog. I saw that coretemp was
> reporting over temps every five minutes, and claiming the cpu was
> being throttled. But then the very next message in the log says the
> temperature is normal. I'm wondering, does this mean the throttling
> was also being cancelled immediately? If so it could explain how the
> machine got so hot that it died on the spot.
>
> I've attached the log. Here's the final refrain of what was occurring
> every 5 minutes for the fifty minutes previous:
>
> Feb 12 19:27:25 ctillman kernel: [137082.856603] CPU3: Core
> temperature above threshold, cpu clock throttled (total events =
> 804180)
> Feb 12 19:27:25 ctillman kernel: [137082.856604] CPU2: Core
> temperature above threshold, cpu clock throttled (total events =
> 804180)
> Feb 12 19:27:25 ctillman kernel: [137082.856607] CPU1: Package
> temperature above threshold, cpu clock throttled (total events =
> 862662)
> Feb 12 19:27:25 ctillman kernel: [137082.856608] CPU0: Package
> temperature above threshold, cpu clock throttled (total events =
> 862662)
> Feb 12 19:27:25 ctillman kernel: [137082.856610] CPU2: Package
> temperature above threshold, cpu clock throttled (total events =
> 862662)
> Feb 12 19:27:25 ctillman kernel: [137082.856621] CPU3: Package
> temperature above threshold, cpu clock throttled (total events =
> 862662)
> Feb 12 19:27:25 ctillman kernel: [137082.857603] CPU3: Core
> temperature/speed normal
> Feb 12 19:27:25 ctillman kernel: [137082.857604] CPU2: Core
> temperature/speed normal
> Feb 12 19:27:25 ctillman kernel: [137082.857606] CPU0: Package
> temperature/speed normal
> Feb 12 19:27:25 ctillman kernel: [137082.857608] CPU1: Package
> temperature/speed normal
> Feb 12 19:27:25 ctillman kernel: [137082.857609] CPU2: Package
> temperature/speed normal
> Feb 12 19:27:25 ctillman kernel: [137082.857612] CPU3: Package
> temperature/speed normal
>
> Notice how each core gets flagged, and then in the same millisecond
> gets cleared. For example
>
> [137082.856603] CPU3: Core temperature above threshold, cpu clock
> throttled (total events = 804180)
> [137082.857603] CPU3: Core temperature/speed normal
>
> The machine is an HP Probook 4530s, which I just bought second hand a
> couple weeks ago. I'd really been enjoying its speed! compared to the
> older computer I'm writing on now.
>
> I'd already had a run-in with overheating, and filed a bug against the
> gpu because it apparently crashed during the previous event:
>
> [Bug 99611] GPU hang after over temperature
>
> That log also showed the same pattern.
>

That has nothing to do with coretemp, which is purely passive.
Thermal throttling is supported as part of the machine check code.

No idea where you filed the bug (not on bugzilla.kernel.org), but
I don't really think you can blame software. My guess would be that
the CPU fan was not operating properly; maybe the thermal paste
between CPU and heatsink was getting old, or maybe the fan is just
broken, or maybe there is just enough dust in the machine that it
no longer cools properly.

There is also mention in some forums that a BIOS update helps with
overheating issues on this laptop.

Guenter


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Fwd: coretemp seems to reset immediately
  2017-02-15 10:48   ` Guenter Roeck
@ 2017-02-15 17:12     ` Chris Tillman
  2017-02-16  5:17       ` Guenter Roeck
  0 siblings, 1 reply; 4+ messages in thread
From: Chris Tillman @ 2017-02-15 17:12 UTC (permalink / raw)
  To: Guenter Roeck; +Cc: linux-hwmon

Thank you very much for your research and input as to the underlying
cause. I had also found those references, and when I opened it up it
looked like the fan had dust on it, so I agree that was the real issue
for my machine. However I also found some references to Linux having
problems with overheating on the machine when Windows did not.

The only reason I sent the mail to this list was that the log output
made it seem like coretemp was reporting a problem, and then reporting
no problem, in the same millisecond. If coretemp is saying there is no
problem, then machine check software will remain inactive. And the
machine will continue to get hotter.

Do you know what kernel module would be involved for the machine check
which would rely on coretemp? I could forward it to them.

On Wed, Feb 15, 2017 at 11:48 PM, Guenter Roeck <linux@roeck-us.net> wrote:
> On 02/15/2017 02:00 AM, Chris Tillman wrote:
>>
>> Hi,
>>
>> I had the awful experience of having my computer fry before my eyes
>> the other day. It was running quite hot (building llvm), and it
>> stopped accepting mouse inputs. I tried to regain control, and after
>> 20 seconds or so it switched me to virtual console 1. But very shortly
>> after that it died, and now it won't even start to boot.
>>
>> Anyway, the reason I'm writing: I retrieved the disk out of it, and on
>> another machine, looked through the syslog. I saw that coretemp was
>> reporting over temps every five minutes, and claiming the cpu was
>> being throttled. But then the very next message in the log says the
>> temperature is normal. I'm wondering, does this mean the throttling
>> was also being cancelled immediately? If so it could explain how the
>> machine got so hot that it died on the spot.
>>
>> I've attached the log. Here's the final refrain of what was occurring
>> every 5 minutes for the fifty minutes previous:
>>
>> Feb 12 19:27:25 ctillman kernel: [137082.856603] CPU3: Core
>> temperature above threshold, cpu clock throttled (total events =
>> 804180)
>> Feb 12 19:27:25 ctillman kernel: [137082.856604] CPU2: Core
>> temperature above threshold, cpu clock throttled (total events =
>> 804180)
>> Feb 12 19:27:25 ctillman kernel: [137082.856607] CPU1: Package
>> temperature above threshold, cpu clock throttled (total events =
>> 862662)
>> Feb 12 19:27:25 ctillman kernel: [137082.856608] CPU0: Package
>> temperature above threshold, cpu clock throttled (total events =
>> 862662)
>> Feb 12 19:27:25 ctillman kernel: [137082.856610] CPU2: Package
>> temperature above threshold, cpu clock throttled (total events =
>> 862662)
>> Feb 12 19:27:25 ctillman kernel: [137082.856621] CPU3: Package
>> temperature above threshold, cpu clock throttled (total events =
>> 862662)
>> Feb 12 19:27:25 ctillman kernel: [137082.857603] CPU3: Core
>> temperature/speed normal
>> Feb 12 19:27:25 ctillman kernel: [137082.857604] CPU2: Core
>> temperature/speed normal
>> Feb 12 19:27:25 ctillman kernel: [137082.857606] CPU0: Package
>> temperature/speed normal
>> Feb 12 19:27:25 ctillman kernel: [137082.857608] CPU1: Package
>> temperature/speed normal
>> Feb 12 19:27:25 ctillman kernel: [137082.857609] CPU2: Package
>> temperature/speed normal
>> Feb 12 19:27:25 ctillman kernel: [137082.857612] CPU3: Package
>> temperature/speed normal
>>
>> Notice how each core gets flagged, and then in the same millisecond
>> gets cleared. For example
>>
>> [137082.856603] CPU3: Core temperature above threshold, cpu clock
>> throttled (total events = 804180)
>> [137082.857603] CPU3: Core temperature/speed normal
>>
>> The machine is an HP Probook 4530s, which I just bought second hand a
>> couple weeks ago. I'd really been enjoying its speed! compared to the
>> older computer I'm writing on now.
>>
>> I'd already had a run-in with overheating, and filed a bug against the
>> gpu because it apparently crashed during the previous event:
>>
>> [Bug 99611] GPU hang after over temperature
>>
>> That log also showed the same pattern.
>>
>
> That has nothing to do with coretemp, which is purely passive.
> Thermal throttling is supported as part of the machine check code.
>
> No idea where you filed the bug (not on bugzilla.kernel.org), but
> I don't really think you can blame software. My guess would be that
> the CPU fan was not operating properly; maybe the thermal paste
> between CPU and heatsink was getting old, or maybe the fan is just
> broken, or maybe there is just enough dust in the machine that it
> no longer cools properly.
>
> There is also mention in some forums that a BIOS update helps with
> overheating issues on this laptop.
>
> Guenter
>



-- 
Chris Tillman
Developer

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Fwd: coretemp seems to reset immediately
  2017-02-15 17:12     ` Chris Tillman
@ 2017-02-16  5:17       ` Guenter Roeck
  0 siblings, 0 replies; 4+ messages in thread
From: Guenter Roeck @ 2017-02-16  5:17 UTC (permalink / raw)
  To: Chris Tillman; +Cc: linux-hwmon

On 02/15/2017 09:12 AM, Chris Tillman wrote:
> Thank you very much for your research and input as to the underlying
> cause. I had also found those references, and when I opened it up it
> looked like the fan had dust on it, so I agree that was the real issue
> for my machine. However I also found some references to Linux having
> problems with overheating on the machine when Windows did not.
>

Yes, but that also said that a BIOS update improved or fixed the problem.
On laptops, temperature control is typically handled by the BIOS or
through an embedded controller, and the operating system is not even
involved. Maybe Windows implements supplementary temperature control
mechanisms - who knows. Hard to say without access to sources.

> The only reason I sent the mail to this list was that the log output
> made it seem like coretemp was reporting a problem, and then reporting

Assuming that you refer to the 'coretemp' module - as mentioned before,
this module is not involved. A log message "Core temperature..."
does not mean that the coretemp module is involved.

> no problem, in the same millisecond. If coretemp is saying there is no
> problem, then machine check software will remain inactive. And the
> machine will continue to get hotter.
>

Not really.

> Do you know what kernel module would be involved for the machine check
> which would rely on coretemp? I could forward it to them.
>

None, which you can confirm easily by not loading the coretemp module
at all (or blacklisting it)  and creating the same situation again;
you'll still see the same messages.

The messages are generated in arch/x86/kernel/cpu/mcheck/therm_throt.c,
which is part of the x86 mce infrastructure. The mailing list address
is linux-edac@vger.kernel.org.

FWIW, I looked through that code. The most interesting information
in the log messages below is "total events = 862662". This means there
were a whopping 862662 thermal events. However, only a single set
of messages is displayed every 5 minutes. From that one message one
can not really draw a conclusion about what exactly happened in the
5 minutes in between. It might be interesting to know under which
circumstances the CPU generates that many thermal events, though.

Guenter

> On Wed, Feb 15, 2017 at 11:48 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>> On 02/15/2017 02:00 AM, Chris Tillman wrote:
>>>
>>> Hi,
>>>
>>> I had the awful experience of having my computer fry before my eyes
>>> the other day. It was running quite hot (building llvm), and it
>>> stopped accepting mouse inputs. I tried to regain control, and after
>>> 20 seconds or so it switched me to virtual console 1. But very shortly
>>> after that it died, and now it won't even start to boot.
>>>
>>> Anyway, the reason I'm writing: I retrieved the disk out of it, and on
>>> another machine, looked through the syslog. I saw that coretemp was
>>> reporting over temps every five minutes, and claiming the cpu was
>>> being throttled. But then the very next message in the log says the
>>> temperature is normal. I'm wondering, does this mean the throttling
>>> was also being cancelled immediately? If so it could explain how the
>>> machine got so hot that it died on the spot.
>>>
>>> I've attached the log. Here's the final refrain of what was occurring
>>> every 5 minutes for the fifty minutes previous:
>>>
>>> Feb 12 19:27:25 ctillman kernel: [137082.856603] CPU3: Core
>>> temperature above threshold, cpu clock throttled (total events =
>>> 804180)
>>> Feb 12 19:27:25 ctillman kernel: [137082.856604] CPU2: Core
>>> temperature above threshold, cpu clock throttled (total events =
>>> 804180)
>>> Feb 12 19:27:25 ctillman kernel: [137082.856607] CPU1: Package
>>> temperature above threshold, cpu clock throttled (total events =
>>> 862662)
>>> Feb 12 19:27:25 ctillman kernel: [137082.856608] CPU0: Package
>>> temperature above threshold, cpu clock throttled (total events =
>>> 862662)
>>> Feb 12 19:27:25 ctillman kernel: [137082.856610] CPU2: Package
>>> temperature above threshold, cpu clock throttled (total events =
>>> 862662)
>>> Feb 12 19:27:25 ctillman kernel: [137082.856621] CPU3: Package
>>> temperature above threshold, cpu clock throttled (total events =
>>> 862662)
>>> Feb 12 19:27:25 ctillman kernel: [137082.857603] CPU3: Core
>>> temperature/speed normal
>>> Feb 12 19:27:25 ctillman kernel: [137082.857604] CPU2: Core
>>> temperature/speed normal
>>> Feb 12 19:27:25 ctillman kernel: [137082.857606] CPU0: Package
>>> temperature/speed normal
>>> Feb 12 19:27:25 ctillman kernel: [137082.857608] CPU1: Package
>>> temperature/speed normal
>>> Feb 12 19:27:25 ctillman kernel: [137082.857609] CPU2: Package
>>> temperature/speed normal
>>> Feb 12 19:27:25 ctillman kernel: [137082.857612] CPU3: Package
>>> temperature/speed normal
>>>
>>> Notice how each core gets flagged, and then in the same millisecond
>>> gets cleared. For example
>>>
>>> [137082.856603] CPU3: Core temperature above threshold, cpu clock
>>> throttled (total events = 804180)
>>> [137082.857603] CPU3: Core temperature/speed normal
>>>
>>> The machine is an HP Probook 4530s, which I just bought second hand a
>>> couple weeks ago. I'd really been enjoying its speed! compared to the
>>> older computer I'm writing on now.
>>>
>>> I'd already had a run-in with overheating, and filed a bug against the
>>> gpu because it apparently crashed during the previous event:
>>>
>>> [Bug 99611] GPU hang after over temperature
>>>
>>> That log also showed the same pattern.
>>>
>>
>> That has nothing to do with coretemp, which is purely passive.
>> Thermal throttling is supported as part of the machine check code.
>>
>> No idea where you filed the bug (not on bugzilla.kernel.org), but
>> I don't really think you can blame software. My guess would be that
>> the CPU fan was not operating properly; maybe the thermal paste
>> between CPU and heatsink was getting old, or maybe the fan is just
>> broken, or maybe there is just enough dust in the machine that it
>> no longer cools properly.
>>
>> There is also mention in some forums that a BIOS update helps with
>> overheating issues on this laptop.
>>
>> Guenter
>>
>
>
>


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2017-02-16  5:17 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CAO299FuK1yX2JRE6E5a4G-8dcJ-RbOjZj_TPyCUJ+tZtM2NWgA@mail.gmail.com>
2017-02-15 10:00 ` Fwd: coretemp seems to reset immediately Chris Tillman
2017-02-15 10:48   ` Guenter Roeck
2017-02-15 17:12     ` Chris Tillman
2017-02-16  5:17       ` Guenter Roeck

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.