Closed 130s closed 3 years ago
Can't tell yet from syslog. Apparently the halt happened after syslogd
terminated AND before it started, so...
Jul 9 17:37:27 130s-kudu1 boinc[2218]: No protocol specified
Jul 9 17:39:00 130s-kudu1 boinc[2218]: message repeated 94 times: [ No protocol specified]
Jul 9 17:39:01 130s-kudu1 CRON[11750]: (root) CMD ( [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Jul 9 17:39:01 130s-kudu1 boinc[2218]: No protocol specified
Jul 9 17:39:10 130s-kudu1 boinc[2218]: message repeated 8 times: [ No protocol specified]
Jul 9 17:39:10 130s-kudu1 systemd[1]: Starting Clean php session files...
Jul 9 17:39:10 130s-kudu1 systemd[1]: Started Clean php session files.
Jul 9 17:39:11 130s-kudu1 boinc[2218]: No protocol specified
Jul 9 17:41:28 130s-kudu1 boinc[2218]: message repeated 137 times: [ No protocol specified]
Jul 9 17:41:29 130s-kudu1 boinc[2218]: No protocol specified
Jul 9 17:41:35 130s-kudu1 boinc[2218]: message repeated 6 times: [ No protocol specified]
Jul 9 17:41:36 130s-kudu1 system76-daemon[1193]: 2020-07-09 17:41:36,033 INFO saving brightness at 464
Jul 9 17:41:37 130s-kudu1 boinc[2218]: No protocol specified
Jul 9 17:41:44 130s-kudu1 boinc[2218]: message repeated 7 times: [ No protocol specified]
Jul 9 17:41:45 130s-kudu1 boinc[2218]: 09-Jul-2020 17:41:45 [---] Suspending network activity - computer is in use
Jul 9 17:48:42 130s-kudu1 systemd[1]: Stopping Save/Restore Sound Card State...
Jul 9 17:48:42 130s-kudu1 systemd[1]: Stopping Thunderbolt system service...
Jul 9 17:48:42 130s-kudu1 systemd[1]: Stopping LVM2 PV scan on device 8:1...
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 18972 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 18991 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 19019 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 19039 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 19064 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 19083 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 19103 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 19246 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 19332 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 19355 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 19399 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 19420 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 19444 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-294.scope: Killing process 22347 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: Stopping Session 294 of user n130s.
Jul 9 17:48:42 130s-kudu1 systemd[1]: Stopping Daemon for generating UUIDs...
Jul 9 17:48:42 130s-kudu1 systemd[1]: Stopping Session c1 of user n130s.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-296.scope: Killing process 24991 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-296.scope: Killing process 25010 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-296.scope: Killing process 25037 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-296.scope: Killing process 25057 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-296.scope: Killing process 25077 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-296.scope: Killing process 25110 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: Stopping Session 296 of user n130s.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-456.scope: Killing process 17744 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-456.scope: Killing process 17765 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-456.scope: Killing process 17795 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-456.scope: Killing process 17813 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-456.scope: Killing process 17833 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: session-456.scope: Killing process 17875 (ssh-agent) with signal SIGTERM.
Jul 9 17:48:42 130s-kudu1 systemd[1]: Stopping Session 456 of user n130s.
Jul 9 20:30:02 130s-kudu1 systemd-modules-load[532]: Inserted module 'lp'
Jul 9 20:30:02 130s-kudu1 systemd-modules-load[532]: Inserted module 'ppdev'
Jul 9 20:30:02 130s-kudu1 systemd-modules-load[532]: Inserted module 'parport_pc'
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] microcode: microcode updated early to revision 0x28, date = 2019-11-12
Jul 9 20:30:02 130s-kudu1 systemd-modules-load[532]: Inserted module 'arp_tables'
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] Linux version 5.3.0-7648-generic (buildd@lcy01-amd64-011) (gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)) #41~1586790036~18.04~600aeb5~dev-Ubuntu SMP Mon Apr 13 17:49:24 (Ubuntu 5.3.0-7648.41~1586790036~18.04~600aeb5~dev-generic 5.3.18)
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-7648-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] KERNEL supported cpus:
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] Intel GenuineIntel
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] AMD AuthenticAMD
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] Hygon HygonGenuine
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] Centaur CentaurHauls
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] zhaoxin Shanghai
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jul 9 20:30:02 130s-kudu1 systemd-modules-load[532]: Inserted module 'br_netfilter'
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Jul 9 20:30:02 130s-kudu1 kernel: [ 0.000000] BIOS-provided physical RAM map:
Immediately after the reboot above, I rebooted again. #414 and this issue both happened again. No useful info from syslog...
Jul 9 20:39:53 130s-kudu1 system76-daemon[1165]: 2020-07-09 20:39:53,577 INFO saving brightness at 464
Jul 9 20:40:12 130s-kudu1 whoopsie[3005]: [20:40:12] Cannot reach: https://daisy.ubuntu.com
Jul 9 20:40:12 130s-kudu1 whoopsie[3005]: [20:40:12] offline
Jul 9 20:40:13 130s-kudu1 whoopsie[3005]: [20:40:13] online
Jul 9 20:43:53 130s-kudu1 ntpd[1451]: 173.72.22.244 local addr 192.168.0.43 -> 192.168.0.23
Jul 9 20:44:55 130s-kudu1 systemd[1]: Stopped target RPC Port Mapper.
Jul 9 20:44:55 130s-kudu1 systemd[1]: Stopping RealtimeKit Scheduling Policy Service...
Jul 9 20:44:55 130s-kudu1 systemd[1]: Stopping Daemon for generating UUIDs...
Jul 9 20:44:55 130s-kudu1 systemd[1]: Stopping LVM2 PV scan on device 8:1...
Jul 9 20:44:55 130s-kudu1 systemd[1]: Stopping Availability of block devices...
Jul 9 20:44:55 130s-kudu1 systemd[1]: Stopping User Manager for UID 1000...
Jul 9 20:44:55 130s-kudu1 systemd[1]: Stopping ACPI event daemon...
Jul 9 20:44:55 130s-kudu1 systemd[1]: Stopped Stop ureadahead data collection 45s after completed startup.
Jul 9 20:44:55 130s-kudu1 systemd[1]: Stopped target Graphical Interface.
Jul 9 20:44:55 130s-kudu1 systemd[1]: Stopping Light Display Manager...
Jul 9 20:44:55 130s-kudu1 systemd[1]: Stopped target Multi-User System.
Jul 10 06:33:28 130s-kudu1 systemd-modules-load[552]: Inserted module 'lp'
Jul 10 06:33:28 130s-kudu1 systemd-modules-load[552]: Inserted module 'ppdev'
A few months later, now kudu1 does not reach BIOS screen at all.Note that after I ran sudo reboot
, I couldn't tell whether the laptop rebooted or it was still in the process of reboot. I manually turned the power off. I've waited for 30 mins, then force power off. Then turned it on again but it's been another 30 mins I see blackscreen.
Took syslog
around the time the long halt started. No clear indication of something that could cause the halt to me. Also note, Ubuntu doesn't seem to finish the shutdown as well https://github.com/130s/hut_10sqft/issues/414
Asked for manufacturer's support system76.com#50484. I can simply re-install OS, but because the issue can be lower than OS (BIOS not comint up right?), I'm afraid re-installing OS might not help.
https://github.com/130s/hut_10sqft/issues/440#issuecomment-692745394 The exact course of actions that took place before I saw this weird behavior is listed below
sudo shutdown
.Support goes on, but the issue still not fixed.
Since this system shipped with two sticks of RAM I'd recommend taking out one stick and testing each one on it's own. A bad stick of RAM would stop the machine from POSTing like this. I would also remove all of your drives and see if it boots to the BIOS by default.
Thanks. I tried booting with a RAM in a single slot, and each slot. I saw the computer starts, monitor remains black, then after several seconds the power light disappears and looks like reboots. I've seen it happened dozens of times :/
During then I removed some dusts/hair from the fan (BTW with kudu 2014, you guys made a significant improvement I think...from serval I bought in 2011, where dust cloggs easily).
After that experiment, I put both RAMs back in and I'm expecting to see see the same original issue (I haven't seen BIOS screen yet 1 hr after I put everything back to normal and turned the power on but I hope it'll come up).
Update: After 14 hrs, looks like it hasn't reached BIOS yet.
Now, it got worse? BIOS is not even coming up after almost a day.
Maybe need to try some of the items in https://www.lifewire.com/fix-computer-that-turns-on-but-displays-nothing-2624443
After receiving the repair at System 76 (took a few months overall b/c pandemic, and a UPS issue), I confirmed this is fixed. Their wisdom says some components just hit lifetime, but I guess I might have kept it on for too long...This isn't a server computer.
According to our hardware team the motherboard needed to be replaced just because of time and use so really the only way to have avoided this is to have a time machine.
After the manual power shutdown due to https://github.com/130s/hut_10sqft/issues/414, pressing the power button does turn on the power but then I didn't see BIOS to come up for a few minutes. Just wait then it eventually came up and Ubuntu started. Very concerning.