Laptop overheat and freeze after booting

Hello, I start using OpenSUSE Tumbleweed recently. While using this fantastic distro, my laptop starts to overheat and eventually freezes. Can someone give me solutions since this situation bothers me a lot? Thank you.

Welcome to the openSUSE forums.

I think you really have to provide information about your laptop like make and type. I assume you understand that your problem is not general for each and every laptop with openSUSE Tumbleweed. Thus people have to find out together with you what is peculiar in your situation. And thus just saying “laptop” without further information is not very useful.

1 Like

I’m using ASUS VivoBook Max X441UBR, powered by Intel i3-7020U (4) @2.3GHz and 2 GPU, Intel HD Graphics 620 and NVIDIA GeForce MX110.

https://www.userbenchmark.com/System/Asus-VivoBook-14-ASUS-Laptop-X441UBR/114290

Is this an OPTIMUS setup?

If so switching off the NVIDIA card may help to lower the temperature (and safe battery).

KDE has under System the System Monitor App.

The History page shows a nice overview of processor usage and temperature sensors; does that tell anything?

@susejunky, hmm how to check if it is OPTIMUS setup?

@marel, I did use this command yesterday

$ cat /sys/class/thermal/thermal_zone*/temp

just a moment before it freezed, and the highest number returned was 59000. It means that the temperature is 59°C right? Btw I forget to mention that I am using XFCE. My apologies.

The only reliable way I know of is to check the documentation supplied with your computer.

My machine is up now for roughly one hour:

# cat /sys/class/thermal/thermal_zone*/temp
42500
43000
44000
36000
#

(and I’m only browsing the forum and writing this post)

Are you sure that it is the temperature of 59°C which causes your system to freeze?

Are there no other reasons which could cause your problem (e.g. bad memory, …)?

When a freeze happens to you again please show on the next restart the result of

journalctl -b -1 -p 3

(run the command in a console as user “root” and paste the command line used, the complete result plus the next empty command line in your post)

I wasn’t aware it was possible to have both Intel UHD graphics and NVidia graphics and not have Optimus. IME, Intel graphics + NVidia graphics in the same laptop was the original definition of Optimus, which was later redefined to mean any dual graphics laptop configuration including NVidia plus graphics provided by Intel GPU or AMD APU, or an AMD GPU plus an AMD APU or Intel iGPU.

Yes, I think so, but on the command line better use:

$ sensors
acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  (crit = +97.0°C)
temp2:        +29.8°C  (crit = +97.0°C)

nvme-pci-0100
Adapter: PCI adapter
Composite:    +40.9°C  (low  =  -0.1°C, high = +86.8°C)
                       (crit = +89.8°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +51.0°C  (high = +86.0°C, crit = +92.0°C)
Core 0:        +42.0°C  (high = +86.0°C, crit = +92.0°C)
Core 1:        +52.0°C  (high = +86.0°C, crit = +92.0°C)
Core 2:        +43.0°C  (high = +86.0°C, crit = +92.0°C)
Core 3:        +40.0°C  (high = +86.0°C, crit = +92.0°C)

nvme-pci-0600
Adapter: PCI adapter
Composite:    +27.9°C  (low  =  -0.1°C, high = +69.8°C)
                       (crit = +84.8°C)

Apart from much better readable, that will show you also the critical temperatures .

1 Like

The desktop so far does not freeze after switching from XFCE to MATE. The highest temperature so far is 54°C. I know that desktop environment can be related to disk and memory usage, but isn’t XFCE the most lightweight DE?

No. Several web comparisons have been made between XFCE and Plasma in recent years showing Plasma can be just as light or lighter, so XFCE can’t be the lightest of all when others like LXQt and LXDE exist among other lightweights.

That said, running such high temp only using XFCE must mean something is running amuck somewhere in XFCE.

1 Like

Did you check sensors? Is there a 60°C limit, or better just post the output.

You could open the laptop and clean the fan/airflow

We do not even know what temperature we are talking about, so far just some random number out of nowhere. 59°C for a CPU is certainly not “high temp”.

Never figure out what caused the high temperature.
Here’s the current temperature of using MATE:

handsomeguy@loc:~> cat /sys/class/thermal/thermal_zone*/temp
41000
50
50
20000
45000
45000
45000

One question, btw. There are 7 numbers of temperature shown above. Can someone explain to me about them? Thank you beforehand.

It is readable but I don’t know the way to read it. Would you mind to explain? Sorry for still being a novice.

# cat /sys/class/thermal/thermal_zone*/temp
27800
29800
39000
# sensors
acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C  (crit = +90.0°C)
temp2:        +29.8°C  (crit = +90.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +39.0°C  (high = +79.0°C, crit = +85.0°C)
Core 0:        +38.0°C  (high = +79.0°C, crit = +85.0°C)
Core 1:        +39.0°C  (high = +79.0°C, crit = +85.0°C)

Looks like Centigrade temps absent decimals.

It freezed again today and here is the output of journalctl after rebooting.

sudo journalctl -b -1 -p 3
[sudo] password for root: 
Jun 24 15:33:49 localhost kernel: x86/cpu: SGX disabled by BIOS.
Jun 24 15:33:51 localhost kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ PRIVRING ]
Jun 24 15:34:18 localhost bluetoothd[1468]: src/plugin.c:plugin_init() Failed to init vcp plugin
Jun 24 15:34:18 localhost bluetoothd[1468]: src/plugin.c:plugin_init() Failed to init mcp plugin
Jun 24 15:34:18 localhost bluetoothd[1468]: src/plugin.c:plugin_init() Failed to init bap plugin
Jun 24 15:34:28 localhost.localdomain kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 6013d4 [ PRIVRING ]
Jun 24 15:34:38 localhost.localdomain lightdm[1998]: gkr-pam: unable to locate daemon control file
Jun 24 15:34:45 localhost.localdomain lightdm[2015]: gkr-pam: unable to locate daemon control file
Jun 24 16:03:26 192.168.1.6 sudo[4863]: gkr-pam: unable to locate daemon control file
Jun 24 16:04:25 192.168.1.6 (sd-pam)[5564]: pam_systemd(login:session): Failed to release session: Access denied
Jun 24 16:04:25 192.168.1.6 (sd-pam)[5564]: pam_wtmpdb(login:session): Updating logout time did not return SQLITE_DONE: 8
Jun 24 16:04:25 192.168.1.6 (sd-pam)[5582]: pam_systemd(login:session): Failed to release session: Access denied
Jun 24 16:04:25 192.168.1.6 (sd-pam)[5582]: pam_wtmpdb(login:session): Updating logout time did not return SQLITE_DONE: 8
Jun 24 16:15:28 192.168.1.6 kernel: ath9k 0000:03:00.0: AER: PCIe Bus Error: severity=Uncorrected (Fatal), type=Inaccessibl>
Jun 24 16:15:30 192.168.1.6 kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=>
Jun 24 16:15:30 192.168.1.6 kernel: ath9k 0000:03:00.0: AER: PCIe Bus Error: severity=Uncorrected (Fatal), type=Inaccessibl>
Jun 24 16:15:30 192.168.1.6 kernel: ath: phy0: Chip reset failed
Jun 24 16:15:30 192.168.1.6 kernel: ath: phy0: Unable to reset channel, reset status -22
Jun 24 16:15:30 192.168.1.6 kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=>
Jun 24 16:15:30 192.168.1.6 kernel: ath: phy0: Chip reset failed
Jun 24 16:15:30 192.168.1.6 kernel: ath: phy0: Unable to reset channel, reset status -22
Jun 24 16:15:30 192.168.1.6 kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=>
Jun 24 16:15:30 192.168.1.6 kernel: ath: phy0: Chip reset failed

Based on this last log it seems like your hardware is dying.