Asus Zenbook Fedora 36 kernel 5.19.8-200.fc36.x86_64 halt

Ask Fedora
,
1

I recently bought Asus Zenbook Flip 14 i7 12700H

             .',;::::;,'.                aniket@fedora
         .';:cccccccccccc:;,.            -------------
      .;cccccccccccccccccccccc;.         OS: Fedora Linux 36 (Workstation Edition) x86_64
    .:cccccccccccccccccccccccccc:.       Host: Zenbook UP5401ZA_UP5401ZA 1.0
  .;ccccccccccccc;.:dddl:.;ccccccc;.     Kernel: 5.19.8-200.fc36.x86_64
 .:ccccccccccccc;OWMKOOXMWd;ccccccc:.    Uptime: 26 mins
.:ccccccccccccc;KMMc;cc;xMMc:ccccccc:.   Packages: 1967 (rpm), 32 (flatpak)
,cccccccccccccc;MMM.;cc;;WW::cccccccc,   Shell: fish 3.5.0
:cccccccccccccc;MMM.;cccccccccccccccc:   Resolution: 2880x1800
:ccccccc;oxOOOo;MMM0OOk.;cccccccccccc:   DE: GNOME 42.4
cccccc:0MMKxdd:;MMMkddc.;cccccccccccc;   WM: Mutter
ccccc:XM0';cccc;MMM.;cccccccccccccccc'   WM Theme: Adwaita
ccccc;MMo;ccccc;MMW.;ccccccccccccccc;    Theme: adw-gtk3-dark [GTK2/3]
ccccc;0MNc.ccc.xMMd:ccccccccccccccc;     Icons: Adwaita [GTK2/3]
cccccc;dNMWXXXWM0::cccccccccccccc:,      Terminal: alacritty
cccccccc;.:odl:.;cccccccccccccc:,.       Terminal Font: black: '0x212121'
:cccccccccccccccccccccccccccc:'.         CPU: 12th Gen Intel i7-12700H (20) @ 4.600GHz
.:cccccccccccccccccccccc:;,..            GPU: Intel Alder Lake-P
  '::cccccccccccccc::;,.                 Memory: 5279MiB / 15685MiB

Things not working →

  • automatic fan (high performance). Works using
sudo su
[root@fedora aniket]# echo 0 > /sys/devices/platform/asus-nb-wmi/hwmon/hwmon[[:print:]]*/pwm1_enable
  • Halts
❯ journalctl -p err -b

Sep 13 14:09:52 fedora kernel: pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
Sep 13 14:09:52 fedora kernel: pci 0000:00:07.1: DPC: RP PIO log size 0 is invalid
Sep 13 14:09:52 fedora kernel: tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
Sep 13 14:10:06 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\CTDP], AE_NOT_FOUND (20220331/psargs-330)
Sep 13 14:10:06 fedora kernel: ACPI Error: Aborting method \_SB.IETM.IDSP due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep 13 14:10:06 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._CRT.S1CT], AE_NOT_FOUND (20220331/psargs-330)
Sep 13 14:10:06 fedora kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep 13 14:10:06 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._HOT.S1HT], AE_NOT_FOUND (20220331/psargs-330)
Sep 13 14:10:06 fedora kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep 13 14:10:06 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._PSV.S1PT], AE_NOT_FOUND (20220331/psargs-330)
Sep 13 14:10:06 fedora kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep 13 14:10:06 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._AC0.S1AT], AE_NOT_FOUND (20220331/psargs-330)
Sep 13 14:10:06 fedora kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._AC0 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep 13 14:10:06 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._CRT.S2CT], AE_NOT_FOUND (20220331/psargs-330)
Sep 13 14:10:06 fedora kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._CRT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep 13 14:10:06 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._HOT.S2HT], AE_NOT_FOUND (20220331/psargs-330)
Sep 13 14:10:06 fedora kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._HOT due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep 13 14:10:06 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._PSV.S2PT], AE_NOT_FOUND (20220331/psargs-330)
Sep 13 14:10:06 fedora kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._PSV due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep 13 14:10:06 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._AC0.S2AT], AE_NOT_FOUND (20220331/psargs-330)
Sep 13 14:10:06 fedora kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._AC0 due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Sep 13 14:10:06 fedora systemd-udevd[1137]: could not read from '/sys/module/acpi_cpufreq/initstate': No such device
Sep 13 14:10:09 fedora kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Sep 13 14:10:10 fedora bluetoothd[1472]: Failed to set mode: Failed (0x03)
Sep 13 14:10:11 fedora thermald[1509]: Unsupported condition 41 (Screen_state)
Sep 13 14:10:11 fedora thermald[1509]: Unsupported condition 4 (Motion)
Sep 13 14:10:11 fedora thermald[1509]: Unsupported conditions are present
Sep 13 14:10:16 fedora gdm-autologin][1854]: gkr-pam: unable to locate daemon control file
Sep 13 14:10:17 fedora systemd[1871]: Failed to start app-glib-liveinst\x2dsetup-2445.scope - Application launched by gnome-session-binary.
Sep 13 14:10:17 fedora systemd[1871]: Failed to start app-glib-xdg\x2duser\x2ddirs-2442.scope - Application launched by gnome-session-binary.
Sep 13 14:10:17 fedora systemd[1871]: Failed to start app-gnome-liveinst\x2dsetup-2445.scope - Application launched by gnome-session-binary.
Sep 13 14:10:19 fedora systemd[1871]: Failed to start app-gnome-spice\x2dvdagent-2635.scope - Application launched by gnome-session-binary.
Sep 13 14:10:19 fedora systemd[1871]: Failed to start app-glib-gnome\x2dshell\x2doverrides\x2dmigration-2728.scope - Application launched by gnome-sess>
Sep 13 14:10:19 fedora systemd[1871]: Failed to start app-glib-user\x2ddirs\x2dupdate\x2dgtk-2738.scope - Application launched by gnome-session-binary.
Sep 13 14:10:19 fedora systemd[1871]: Failed to start app-glib-vboxclient-2717.scope - Application launched by gnome-session-binary.
Sep 13 14:10:19 fedora systemd[1871]: Failed to start app-glib-vmware\x2duser-2712.scope - Application launched by gnome-session-binary.

❯ sudo fprintd-enroll
[sudo] password for aniket:
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-disconnected

Everything works out of the box on Windows 11. But the thing is I don’t want to use windows, I want to use Fedora (Rust Developer). If someone could help me fix the halting issue, it would make my new laptop reliable. Random halts during meetings are a pain.

2

I’m very sorry for the crash. I don’t think any of the messages you see from journalctl would cause the kernel to crash, so we’ll have to look deeper.

Can you post this issue to the linux-kernel@vger.kernel.org mailing list and cc me (bjorn@helgaas.com)? (The mailing list will reject any HTML or multi-part email, but attachments should be OK.) I know you’re trying to run Fedora, but it’s likely that an unmodified upstream kernel would have the same problem.

Please describe what happens in as much detail as possible. I guess the system is usable for a while before it crashes, right? Does the system automatically reboot? Does it hang completely, so you must reboot it or power-cycle it manually? Is there a panic message before it reboots? If so, a picture of it would be useful. If you can attach the complete dmesg log and output of “sudo lspci -vv” before the crash, that might help, too.

3

Thanks for the reply @bjorn-helgaas

Output of sudo lspci -vv can be found at lspci output · GitHub

The crash is happening quite frequently and causes a restart (sometimes).

4

Can you attach a complete dmesg log, too, please?

Without some kind of hint about what the crash looks like, it will be pretty hard to figure anything out.

5

Before Crash

After Crash

6

Thanks for these. They look pretty much identical except for a few address and ordering differences, which are expected.

I assume the sequence was:

  • Boot Linux
  • Collect “before” dmesg log
  • Linux crashes
  • Reboot Linux from scratch
  • Collect “after” dmesg log

If that’s correct, we wouldn’t expect any information about the crash from the “after” log.

The only thing I can think of to get more information about what caused the crash is to use pstore and ramoops. This might not work if your BIOS clears memory at reboot, but you can try this:

  • Boot with these kernel parameters:
memmap=2M!8M ramoops.mem_address=0x00800000 ramoops.mem_size=0x00200000 ramoops.ecc=1
  • Wait for a crash and reboot
  • After reboot, run these commands as root and attach the output:
mount | grep pstore
modprobe ramoops mem_address=0x00800000 mem_size=0x00200000 ecc=1
dmesg | egrep -i 'pstore|ramoops'
ls -l /sys/fs/pstore/
cat /sys/fs/pstore/*
7

@bjorn-helgaas will update u on this.
Can the crashes be problematic with GDM, gnome, or pipe wire?
The keyboard backlights remain lit up for a couple of seconds and on pressing the power button I can see the spinner and asus logo.
Firefox crashes a lot sometimes while watching a youtube videos (HD and 4k Mostly)
No other distro is able to get the speakers to work.
Gnome used to crash while changing audio and mic.

Should I clean install fedora 37

8

I doubt a reinstall would fix it. If pstore/ramoops can capture anything, it might show a kernel problem we could fix. I have no idea about GDM, gnome, firefox, etc. Those are all out of my scope :slight_smile: