Lenovo T440p reboots suddenly

General system Kernel & Hardware
1

I had installed EndeavourOS on a Lenovo T440p. Most of the time things working fine. But from time to time it happens that the screen is black and a reboot takes place.

journalctl shows

Aug 03 15:42:10 hogwart rtkit-daemon[784]: Supervising 11 threads of 8 processes of 1 users.
Aug 03 15:42:34 hogwart wpa_supplicant[706]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-70 noise=9999 txrate=240000
Aug 03 15:42:42 hogwart wpa_supplicant[706]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-57 noise=9999 txrate=270000
-- Boot 13c7487a769e454d8c1927d19f8a8f3e --
Aug 03 15:44:28 hogwart kernel: microcode: updated early: 0x25 -> 0x28, date = 2019-11-12

Is there anything I can turn on to get more messages in case it happens again?

Thanks.

–
Manfred

2

Hi, the first thing I would try would be a different kernel. If you are currently on the main kernel, try the LTS kernel.

3

These logs seem a bit strange… You mentioned that an actual reboot took place? Usually, each step taken by systemd during the reboot process will be logged. I’m assuming that this isn’t the full log?

4

It happened with LTS and arch kernel.

5

My English was bad.

The screen got dark and the laptop was more or less immmediately turned off. I didn’t see any shutdown actions.

Then I rebooted.

6

Are there any specific patterns that you noticed? For example, does it only occur with high cpu activity? Could heat be an issue?

7

This part shows the log after you reboot, right? And the lines above it are the logs before/during the event where the screen turned black? Can you show more of lines of the logs before the screen went black?

8

Yes.

Here some mover lines before the screen went black.

Aug 03 15:36:05 hogwart rtkit-daemon[784]: Successfully made thread 59791 of process 59349 owned by '1000' RT at priority>
Aug 03 15:36:05 hogwart rtkit-daemon[784]: Supervising 11 threads of 8 processes of 1 users.
Aug 03 15:38:09 hogwart wpa_supplicant[706]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-54 noise=9999 txrate=300000
Aug 03 15:38:15 hogwart rtkit-daemon[784]: Supervising 11 threads of 8 processes of 1 users.
Aug 03 15:38:15 hogwart rtkit-daemon[784]: Supervising 11 threads of 8 processes of 1 users.
Aug 03 15:39:27 hogwart rtkit-daemon[784]: Supervising 11 threads of 8 processes of 1 users.
Aug 03 15:39:27 hogwart rtkit-daemon[784]: Supervising 11 threads of 8 processes of 1 users.
Aug 03 15:40:03 hogwart gsd-media-keys[1484]: Unable to get default source
Aug 03 15:40:09 hogwart rtkit-daemon[784]: Supervising 11 threads of 8 processes of 1 users.
Aug 03 15:40:09 hogwart rtkit-daemon[784]: Supervising 11 threads of 8 processes of 1 users.
Aug 03 15:40:21 hogwart wpa_supplicant[706]: wlan0: WPA: Group rekeying completed with 44:4e:6d:93:1d:88 [GTK=CCMP]
Aug 03 15:41:07 hogwart rtkit-daemon[784]: Supervising 11 threads of 8 processes of 1 users.
Aug 03 15:41:07 hogwart rtkit-daemon[784]: Supervising 11 threads of 8 processes of 1 users.
Aug 03 15:42:10 hogwart rtkit-daemon[784]: Supervising 11 threads of 8 processes of 1 users.
Aug 03 15:42:10 hogwart rtkit-daemon[784]: Supervising 11 threads of 8 processes of 1 users.
Aug 03 15:42:34 hogwart wpa_supplicant[706]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-70 noise=9999 txrate=240000
Aug 03 15:42:42 hogwart wpa_supplicant[706]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-57 noise=9999 txrate=270000
-- Boot 13c7487a769e454d8c1927d19f8a8f3e --
9

Perhaps post the logs for that entire (problematic) boot session with the eos-log tool? It’s hard to tell at which line the system crashed.

Also, do you remember when this first occurred? In particular, do you remember the kernel version that was first affected by this? Maybe it’s a regression in the linux kernel.

10

Hm, not sure I chose the right sections. http://ix.io/4CfM

11

Assuming that the previous boot is the problematic one, try

journalctl -b1 | eos-sendlog
12

Are you sure it’s not a power management issue with the WiFi?

13

Done. But -b-1

http://ix.io/4CfS

14

I am not sure in any way and have to admit I didn’t think about wifi power management at all.

15

Were you able to switch to TTY when this occured?

16

I hadn’t tried to switch to TTY but will try next time.

There was no responce at all and I pressed the power button which started the system again.

17

I have never taken a look at wifi powermgmt.

Issuing iw dev wlan0 get power_save I get Power save: on. Should I turn it off?

18

Yes you could try that to see if that’s causing the issue?

19

Ok, I have set it to off. Will see if it happens again.