Kernel regressions on Asus Rog g14 2022 (hang on resume from hibernate)

Support Kernel
1

Apparently, all kernels >= 6.11 have regressions on this machine and cannot resume from hibernation. Kernel 6.10.13 was fine.

This is nasty, because after the last stable upgrade it leaves no fully working kernel on this machine:

  • 6.6.x can hibernate/resume, but has graphical artifacts
  • 6.11.10 no hibernation/resume
  • 6.12.1 no hibernation/resume

I have verified that locally creating a 6.10.13 kernel package using the manjaro PKGBUILD from manjaro’s packages gitlab provides a working kernel that can hibernate.

Some questions:

  • Anyone else experiencing problems with 6.11/6.12 and resuming from hibernation? Any clue? The usual suspects seem the mediatek wifi and the AMD graphics, but who knows…
  • Is this kernel issue known upstream?
  • How to stay on 6.10.13? Manjaro’s pamac tries to uninistall it whenever you use the tool, even if it is to do something totally unrelated.
2

Hi! A bit more system info may help; e.g. do you have sufficient swap vs. RAM?

inxi -zv8

will reveal this. Please highlight the pasted text and click the </> button at the top of the reply window.

Cheers! :wink:

3

Looks like it is this issue: Framework 16 Fails to Resume From Hibernate - Linux - Framework Community. Kernel developers have been made aware: see Re: [REGRESSION] bluetooth: mt7921: Crash on Resume From Suspend And Hibernate - Linux regression tracking (Thorsten Leemhuis) and replies from there.

Most likely indeed a kernel regression.

It is being mentioned that there should be an updated firmware from mediatek that fixes the issue: Update binary firmware for MT7921 WiFi devices File: mediatek/WIFI_MT7961_patch_mcu_1_2_hdr.bin Version: 20241106151007a File: mediatek/WIFI_RAM_CODE_MT7961_1.bin Version: 20241106150855

Namely, linux 6.11 and 6.12 until they get patched (in principle they should after the no-regression policy) need the firmware dated 2024-11-06.

The firmware shipped with manjaro is just before that.

1 Like
4

More tests:

  • blocking bluetooth (rfkill block bluetooth) before hibernation works around the issue
  • the updated firmware does not fix the issue neither in kernel 6.11.10, nor in 6.12.1 (unless I missed some firmware file… but I have substituted all the 6 files mentioned in the firmware patch).
5

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.