Laptop random reboots

mr.simo · 10-04-2018, 02:33 AM

Hello,

Since a few days I am experiencing random reboots of my laptop.
I don't think it's caused by thermal overheat of the CPU since sensors command returns the following output:

Code:

$ sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +47.0°C  (crit = +126.0°C)
temp2:        +47.0°C  (crit = +98.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +50.0°C  (high = +100.0°C, crit = +100.0°C)

but last command returns some suspicious results:

Code:

$ last
simo     tty7         :0               Thu Oct  4 09:21   still logged in
reboot   system boot  4.9.0-4-amd64    Thu Oct  4 09:17   still running
simo     tty7         :0               Thu Oct  4 09:03 - crash  (00:13)
reboot   system boot  4.9.0-4-amd64    Thu Oct  4 08:57   still running
simo     tty7         :0               Wed Oct  3 22:31 - 23:12  (00:40)
reboot   system boot  4.9.0-4-amd64    Wed Oct  3 22:31 - 23:12  (00:41)
simo     tty7         :0               Wed Oct  3 22:28 - crash  (00:03)
reboot   system boot  4.9.0-4-amd64    Wed Oct  3 22:27 - 23:12  (00:44)
simo     tty7         :0               Wed Oct  3 22:25 - crash  (00:01)
reboot   system boot  4.9.0-4-amd64    Wed Oct  3 22:25 - 23:12  (00:47)
simo     tty7         :0               Wed Oct  3 22:16 - crash  (00:08)
reboot   system boot  4.9.0-4-amd64    Wed Oct  3 22:15 - 23:12  (00:56)
reboot   system boot  4.9.0-4-amd64    Wed Oct  3 22:14 - 23:12  (00:58)
simo     tty7         :0               Wed Oct  3 16:21 - 20:19  (03:57)
reboot   system boot  4.9.0-4-amd64    Wed Oct  3 16:21 - 20:19  (03:58)
simo     tty7         :0               Wed Oct  3 09:39 - 15:50  (06:11)
reboot   system boot  4.9.0-4-amd64    Wed Oct  3 09:38 - 15:50  (06:12)
simo     tty7         :0               Wed Oct  3 09:06 - crash  (00:32)
reboot   system boot  4.9.0-4-amd64    Wed Oct  3 09:05 - 15:50  (06:45)
simo     tty7         :0               Tue Oct  2 21:53 - down   (02:43)
reboot   system boot  4.9.0-4-amd64    Tue Oct  2 21:52 - 00:36  (02:44)
reboot   system boot  4.9.0-4-amd64    Tue Oct  2 21:49 - 00:36  (02:47)
reboot   system boot  4.9.0-4-amd64    Tue Oct  2 21:10 - 00:36  (03:26)
simo     tty7         :0               Tue Oct  2 20:59 - crash  (00:11)
reboot   system boot  4.9.0-4-amd64    Tue Oct  2 20:58 - 00:36  (03:37)
simo     tty7         :0               Tue Oct  2 09:01 - 18:51  (09:49)
reboot   system boot  4.9.0-4-amd64    Tue Oct  2 09:00 - 18:51  (09:50)
simo     tty7         :0               Tue Oct  2 08:52 - crash  (00:08)
reboot   system boot  4.9.0-4-amd64    Tue Oct  2 08:51 - 18:51  (09:59)
reboot   system boot  4.9.0-4-amd64    Tue Oct  2 08:42 - 18:51  (10:09)

wtmp begins Mon Oct  1 19:25:58 2018

grepping /var/log/ in search of some system voluntary reboot I don't see any evidence of this behavior, just these cron line:

Code:

/var/log/syslog:1254:Oct  4 09:17:29 <hostname> cron[528]: (CRON) INFO (Running @reboot jobs)
/var/log/syslog.1:1001:Oct  3 09:05:31 <hostname> cron[503]: (CRON) INFO (Running @reboot jobs)
/var/log/syslog.1:2452:Oct  3 09:38:42 <hostname> cron[490]: (CRON) INFO (Running @reboot jobs)
/var/log/syslog.1:4264:Oct  3 16:21:25 <hostname> cron[494]: (CRON) INFO (Running @reboot jobs)
/var/log/syslog.1:6010:Oct  3 22:14:35 <hostname> cron[510]: (CRON) INFO (Running @reboot jobs)

as I know these are printed after reboot, not before.
Is there another way to inspect if these reboots are caused by a program or a driver ?

Thank you in advance.
s.

jsbjsb001 · 10-04-2018, 07:01 AM

The "Adapter: Virtual device" line in your output makes me think that's referring to a virtual machine rather than a real machine.

In your output from the "last" command it saying that there has been what looks like a number of "system crashes". In that case I'd be looking at the /var/log/messages files as well as dmesg, etc. If it's a part of the OS crashing, then there's a good chance that at least something useful might be in the logs somewhere. I don't know of any specific program that could tell you exactly what's doing it, other than the logs. There may also be logs for whatever it is that's "crashing" that could tell you something.

Start with the system logs and go from there.

mr.simo · 10-04-2018, 07:56 AM

Unfortunetly I cannot find any relevant info from log files.
I am suspecting that the power supply sits down for a few μs in such a way that the whole system reboots or shuts it down.

This makes sense since I also exeperienced random shut-down.
I changed the PS and I am testing it. Until now it didn't rebooted or powered off.

I will keep this thread updated.
Regards,
s.

jsbjsb001 · 10-04-2018, 08:01 AM

If it was just randomly rebooting, then yes, it could well be the power supply unit at fault. But given the "last" command is listing actual "crashes" and says the word "crash", that would suggest that a piece of software has crashed. Rather than a hardware fault of some description. At this stage I can't pinpoint exactly what the problem is on the info provided thus far, so it's wide open at this point.

I would personally if it were me, be trying to find out what's "crashed", and be going from there.

dc.901 · 10-12-2018, 11:21 AM

Some BIOS contains hardware event logs; have you checked?