You are not logged in.
Pages: 1
For a while when system goes to suspend, my laptop warms crazy hot with random suspends. I tried Lts and regular kernels but there is no differences. Here is the log from after wake up with the problem appears:
4:26:02 ÖS systemd: systemd-journald.service: Watchdog timeout (limit 3min)!
4:26:02 ÖS kernel: ELF object binary architecture: AMD x86-64
4:26:02 ÖS kernel: #7 0x000055dfbffd229e n/a (systemd-journald + 0x829e)
4:26:02 ÖS kernel: #6 0x00007f50fd6ea3c1 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2d3c1)
4:26:02 ÖS kernel: #5 0x00007f50fd6ea310 __libc_start_call_main (libc.so.6 + 0x2d310)
4:26:02 ÖS kernel: #4 0x000055dfbffd1b5e n/a (systemd-journald + 0x7b5e)
4:26:02 ÖS kernel: #3 0x00007f50fdb4a703 sd_event_run (libsystemd-shared-250.so + 0x23f703)
4:26:02 ÖS kernel: #2 0x00007f50fdb4a0a0 sd_event_prepare (libsystemd-shared-250.so + 0x23f0a0)
4:26:02 ÖS kernel: #1 0x00007f50fdb4934b sd_event_wait (libsystemd-shared-250.so + 0x23e34b)
4:26:02 ÖS kernel: #0 0x00007f50fd7cf9ae epoll_wait (libc.so.6 + 0x1129ae)
4:26:02 ÖS kernel: Stack trace of thread 730:
4:26:02 ÖS kernel: Module systemd-journald with build-id 69fd8da091a70a9342c21dbd93066f6d03e22569
4:26:02 ÖS kernel: Module systemd-journald with build-id 69fd8da091a70a9342c21dbd93066f6d03e22569
4:26:02 ÖS kernel: Module libsystemd-shared-250.so with build-id 987186711c5f375bb16af30432893d8f24bc690e
4:26:02 ÖS kernel: Module libgcc_s.so.1 with build-id 5d817452a709ca3a213341555ddcf446ecee37fa
4:26:02 ÖS kernel: Module libpthread.so.0 with build-id 7fa8b52fae071a370ba4ca32bf9490a30aff31c4
4:26:02 ÖS kernel: Module libc.so.6 with build-id 85766e9d8458b16e9c7ce6e07c712c02b8471dbc
4:26:02 ÖS kernel: Module libacl.so.1 with build-id 27869ed0219ade5d2ffd50eaee11f967187faa8b
4:26:02 ÖS kernel: Module libblkid.so.1 with build-id 9e4bb910a2e63ba71cae0e3b89c07fdd45033ff2
4:26:02 ÖS kernel: Module libcap.so.2 with build-id eb6dae97527fc89dbb0d5bb581a15acd02ae9f56
4:26:02 ÖS kernel: Module libcrypt.so.2 with build-id a0a45f81771945f0559d04e93726d245159930da
4:26:02 ÖS kernel: Module libdl.so.2 with build-id bb9bd2657bfba9f60bd34d2050cc63a7eb024bc4
4:26:02 ÖS kernel: Module libgcrypt.so.20 with build-id db45f5d5e0f7af1e77324fea1885f974619ad268
4:26:02 ÖS kernel: Module libip4tc.so.2 with build-id 614c189c0dad12cfff3dd96e3ffdd698bf209fb8
4:26:02 ÖS kernel: Module libkmod.so.2 with build-id 4cdb0fbea046752f70208205a28289cd28b11af0
4:26:02 ÖS kernel: Module liblz4.so.1 with build-id e63600ab23b2f6997f42fac2fa56e1f02ce159a1
4:26:02 ÖS kernel: Module libmount.so.1 with build-id 765508fe9812e693ac41fd3d0aedd65d7a78b287
4:26:02 ÖS kernel: Module libcrypto.so.1.1 with build-id 4c926b672d97886b123e03a008387aecf0786de4
4:26:02 ÖS kernel: Module libp11-kit.so.0 with build-id cc372ea3c28c4d3dfc633b4d2e933c8584d2af16
4:26:02 ÖS kernel: Module libpam.so.0 with build-id bb11b2685fe89555938ffd330ea44d82b0f8701c
4:26:02 ÖS kernel: Module librt.so.1 with build-id 4761858b348db8303e872e515aa8d56c046c921c
4:26:02 ÖS kernel: Module libseccomp.so.2 with build-id 54179323d84e1b713b7547ba0b3f8310e65eec93
4:26:02 ÖS kernel: Module libzstd.so.1 with build-id 72f3511cba7db578f6a2647925f35664da6c838b
4:26:02 ÖS kernel: Module liblzma.so.5 with build-id 8b615460aa230708c5183f16bede67aa0437d95e
4:26:02 ÖS kernel: Module libm.so.6 with build-id 596b63a006a4386dcab30912d2b54a7a61827b07
4:26:02 ÖS kernel: Module ld-linux-x86-64.so.2 with build-id c09c6f50f6bcec73c64a0b4be77eadb8f7202410
4:26:02 ÖS kernel: Module libgpg-error.so.0 with build-id 82524ee3d1c4c2244d7cfdcc1e6eea5f9855f6c6
4:26:02 ÖS kernel: Module libz.so.1 with build-id 0c1459c56513efd5d53eb3868290e9afee6a6a26
4:26:02 ÖS kernel: Module libffi.so.8 with build-id f90d8b734f6de9b25faedb8cbfab7054dafc0a42
4:26:02 ÖS kernel: Module libaudit.so.1 with build-id 27ca9470fd239e2f61c83e293f24f266789485b6
4:26:02 ÖS kernel: Module libcap-ng.so.0 with build-id 09690c43af29ef92bbec2e53e29101b2b8e9c48c
4:26:02 ÖS kernel: Module linux-vdso.so.1 with build-id bf4ed7d70241039dd0fc7f51de8118e93bf3af20
4:26:02 ÖS kernel: Coredump diverted to /var/lib/systemd/coredump/core.systemd-journal.0.fde49e895c2d45058e58b1dc342d06c5.730.1646400362000000.zst
4:26:02 ÖS kernel: Process 730 (systemd-journal) of user 0 dumped core.
4:26:02 ÖS kernel: rcu: 7-....: (78011 ticks this GP) idle=0b9/1/0x4000000000000000 softirq=937552/937552 fqs=39005
4:26:02 ÖS kernel: rcu: 7-....: (78011 ticks this GP) idle=0b9/1/0x4000000000000000 softirq=937552/937552 fqs=39005
4:26:02 ÖS kernel: rcu: INFO: rcu_sched self-detected stall on CPU
4:26:02 ÖS kernel: rcu: 7-....: (60008 ticks this GP) idle=0b9/1/0x4000000000000000 softirq=937552/937552 fqs=30004
4:26:02 ÖS kernel: rcu: INFO: rcu_sched self-detected stall on CPU
4:26:02 ÖS kernel: rcu: 7-....: (42005 ticks this GP) idle=0b9/1/0x4000000000000000 softirq=937552/937552 fqs=21002
4:26:02 ÖS kernel: rcu: INFO: rcu_sched self-detected stall on CPU
4:26:02 ÖS kernel: rcu: 7-....: (24002 ticks this GP) idle=0b9/1/0x4000000000000000 softirq=937552/937552 fqs=12001
4:26:02 ÖS kernel: rcu: INFO: rcu_sched self-detected stall on CPU
4:26:02 ÖS kernel: rcu: 7-....: (5999 ticks this GP) idle=0b9/1/0x4000000000000000 softirq=937552/937552 fqs=2999
4:26:02 ÖS kernel: rcu: INFO: rcu_sched self-detected stall on CPU
3:11:55 ÖS kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x71b
3:11:55 ÖS kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x71b
3:11:55 ÖS kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x71b
3:11:55 ÖS kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x71b
3:11:55 ÖS kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x71b
3:11:55 ÖS kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x71b
3:11:55 ÖS kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x71b
3:11:55 ÖS kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x71b
3:11:55 ÖS kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x71b
3:11:55 ÖS kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x71b
3:11:55 ÖS kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x71b
2:06:12 ÖS kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
2:06:12 ÖS kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
2:06:12 ÖS kernel: sd 0:0:0:0: [sda] No Caching mode page foundLast edited by ndhakara (2022-03-04 14:04:10)
Offline
Well finally I can manage to reproduce the issue. While my huawei matebook 14s suspended if I disconnect or connect the charge port, heat issue appears. There is no problem if I connect it to charging while not suspended. Just only disconnect / connect from charging, the laptop already suspended.
I think this problem is related with huawei-wmi driver.
Any suggestion?
Last edited by ndhakara (2022-03-07 16:29:21)
Offline
Probably seeing this: https://bbs.archlinux.org/viewtopic.php?id=274292
Same issue with overheating laptop with me, in which I nearly killed my CPU before I realized what was happening.
Upstream Linux kernel introduced this bug; hopefully fixed with 5.17's release.
Last edited by flan_suse (2022-03-07 19:30:52)
Offline
Probably seeing this: https://bbs.archlinux.org/viewtopic.php?id=274292
Same issue with overheating laptop with me, in which I nearly killed my CPU before I realized what was happening.
Upstream Linux kernel introduced this bug; hopefully fixed with 5.17's release.
For now I am very carefully about charging
, I hope the fix at 5.17 solves my problem too.
Offline
For now I am very carefully about charging
, I hope the fix at 5.17 solves my problem too.
5.17 does indeed fix the issue (I'm using the latest "-rc"). Which means they've located / reverted the bug that introduced it. However, I hope they backport it to 5.15 LTS, since 5.17 also introduced some strange bugs with CIFS shares and credentials. I keep getting this on 5.17 when connecting to some shares, and the only resolution is to reboot:
[57144.583276] CIFS: Attempting to mount \\192.168.0.200\media
[57144.583308] CIFS: VFS: \\192.168.0.200 failed to connect to IPC (rc=-11)
[57144.583321] CIFS: VFS: session 0000000020ff1117 has no tcon available for a dfs referral request
[57144.583327] CIFS: VFS: cifs_mount failed w/return code = -11Using kernel 5.15 works fine, 100% of the time.
P.S. I can't believe a nasty suspend bug was backported into an LTS kernel. What ever happened the slow and steady of LTS kernels, and staying clear of major changes in code/behaviour?
Offline
ndhakara wrote:For now I am very carefully about charging
, I hope the fix at 5.17 solves my problem too.
5.17 does indeed fix the issue (I'm using the latest "-rc"). Which means they've located / reverted the bug that introduced it. However, I hope they backport it to 5.15 LTS, since 5.17 also introduced some strange bugs with CIFS shares and credentials. I keep getting this on 5.17 when connecting to some shares, and the only resolution is to reboot:
[57144.583276] CIFS: Attempting to mount \\192.168.0.200\media [57144.583308] CIFS: VFS: \\192.168.0.200 failed to connect to IPC (rc=-11) [57144.583321] CIFS: VFS: session 0000000020ff1117 has no tcon available for a dfs referral request [57144.583327] CIFS: VFS: cifs_mount failed w/return code = -11Using kernel 5.15 works fine, 100% of the time.
P.S. I can't believe a nasty suspend bug was backported into an LTS kernel. What ever happened the slow and steady of LTS kernels, and staying clear of major changes in code/behaviour?
Btw I saw that this problem is not related with charging. It is about usb connection and disconnection while laptop suspended.
I was charging my Phone from laptop and after enougj charging, I disconnected the Phone while laptop suspended and the issue was appeared again. ![]()
Let's see 5.17. ![]()
Offline
Pages: 1