Arch crashing

BluNate · 2025-01-05 21:05:44

I'm running the ASUS FA707NU. It's a laptop with a Ryzen 7 processor and an RTX 4050 mobile chip in it.

Running an installed version or arch, the 2025.01.01 or 2024.12.01 ISOs, when booted, will eventually crash. It could crash anywhere between a couple of minutes to a couple of seconds, but it WILL crash eventually. Before it has crashed, the entire system is operational, nothing strange. Whenever it does crash, it suddenly shuts down and reboots into the BIOS's first boot option.

Setting acpi=off in kernel parameters fixes this bug, but since it's a laptop, it's not a great option. I found these pages on the Arch Wiki: ACPI and this particular section of DSDT. These pages seemed to have made my system more stable, but it still crashes.

JournalCtl does not log any events when this happens, but I now receive machine check messages before it crashes. They're never consistent, but they're almost always on CPU 6 and 7, and they usually come in a pair, both at the same time. 0x0.st/8i9L.txt

Last edited by BluNate (2025-01-05 21:17:10)

twelveeighty · 2025-01-06 01:37:53

An MCE (Machine Check Exception) is almost always a hardware issue. Assuming you're not overclocking the laptop (in which case you should undo that to confirm), do a stress test of CPU and/or RAM to check.

Do you get the MCE errors even with acpi=off? Because then it's almost guaranteed a hardware issue.

BluNate · 2025-01-06 03:54:09

twelveeighty wrote:

Do you get the MCE errors even with acpi=off? Because then it's almost guaranteed a hardware issue.

Nope, I don't get any errors with acpi=off!
I used Memtest86+ and that passed, arch will run for hours with no errors, considering acpi=off.
Also, there are almost no real options in this BIOS. I'm not sure why, but there's basically nothing.

Last edited by BluNate (2025-01-06 09:39:44)

twelveeighty · 2025-01-06 16:04:25

Without acpi=off, are you keeping an eye out for CPU temperature? - see ASUS fan speed control. Overheating could cause that type of crash.

Btw: what exactly do you mean by "an installed version of arch, the 2025.01.01 or 2024.12.01 ISOs". It doesn't matter which ISO you used to install, as long as you are fully up-to-date (pacman -Syu).

BluNate · 2025-01-06 16:27:31

twelveeighty wrote:

Without acpi=off, are you keeping an eye out for CPU temperature? - see ASUS fan speed control. Overheating could cause that type of crash.

It would be strange, it seems to crash more often when completley cold (+ the fans are active during acpi). I haven't felt any heat from the laptop, so I just assumed it was fine until now.

I installed it, and I'm not sure it detected the CPU temp, but it picked up the iGPU, so close enough.
It got to 41°C before it crashed. There was a suspiciously CPU-like sensor that got up to around 45ish before stopping, so that's all I have.

twelveeighty wrote:

Btw: what exactly do you mean by "an installed version of arch, the 2025.01.01 or 2024.12.01 ISOs". It doesn't matter which ISO you used to install, as long as you are fully up-to-date (pacman -Syu).

Because it was affecting the ISOs pre-install too. It was a pain to get arch installed.

Last edited by BluNate (2025-01-06 21:49:58)

twelveeighty · 2025-01-07 01:26:45

Probably safe to eliminate heat as a possible culprit then.

Are you saying that when booted into the Arch ISO (i.e. without any graphics loaded) you're still seeing the crash? That would narrow things down, for sure.

BluNate · 2025-01-07 04:15:55

twelveeighty wrote:

Probably safe to eliminate heat as a possible culprit then.
Are you saying that when booted into the Arch ISO (i.e. without any graphics loaded) you're still seeing the crash? That would narrow things down, for sure.

Yea, the ISO is crashing as well, same way.
I also tried nomodeset on the ISO with the same results as everything else.

twelveeighty · 2025-01-07 16:05:03

When booted into the ISO, is there anything echoed back to the terminal when it crashes? Can you try booting into the ISO, then have journalctl --follow running until a crash and see what's being logged up to the crash. It'll be a big challenge trying to get that back to these forums from the ISO, since there's no persistent journal with the ISO boot, but at least it may give us a hint.

seth · 2025-01-07 17:28:52

acpi_osi=! acpi_osi="Windows 10, version 2004" acpi_os_name="Microsoft Windows NT"

Did chatgpt tell you that?

acpi_osi=! acpi_osi="Windows 2015"

https://learn.microsoft.com/en-us/windo … inacpi-osi

acpi_os_name is nonsense.

processor.max_cstate=0 idle=nomwait rcu_nocbs=0-15

Are already mitigational efforts?

The big thing is obviously https://wiki.archlinux.org/title/Ryzen#Random_reboots
Are you able to increase the CPU voltage?

BluNate · 2025-01-07 20:31:43

seth wrote:

Did chatgpt tell you that?
acpi_os_name is nonsense.

No, it was in the arch wiki
This was a linked page from the "ACPI modules" page on the arch wiki

processor.max_cstate=0 idle=nomwait rcu_nocbs=0-15
Are already mitigational efforts?

I already linked these pages in the original post.

The big thing is obviously https://wiki.archlinux.org/title/Ryzen#Random_reboots
Are you able to increase the CPU voltage?

Nope, the BIOS is pretty barren, even in 'advanced' mode. Such options do not exist because you're fully expected to use the 'armoury crate' app instead.

This is probably the issue, so now I need a way to do this in software... strange that it only happens when ACPI devices are on though.

Last edited by BluNate (2025-01-07 20:36:14)

BluNate · 2025-01-07 20:35:07

twelveeighty wrote:

When booted into the ISO, is there anything echoed back to the terminal when it crashes?

Nothing extra seems to happen in the ISO, I've tried but there's not a lot there.

seth · 2025-01-07 20:41:12

No, it was in the arch wiki

Worse, it's also in the kernel parameter docs - so I stand corrected.
Stick w/ one approach though and make it acpi_osi

This is probably the issue, though, so now I need a way to do this in software...

https://aur.archlinux.org/packages/asusctl ?

BluNate · 2025-01-09 06:53:17

seth wrote:

https://aur.archlinux.org/packages/asusctl ?

does look promising, but im getting the same errors as this guy:
https://www.reddit.com/r/ZephyrusG14/co … _panicked/

asusd was running and g14 kernel was seemingly no help

I seem to get this error for just invoking asusctl, and doing any commands has the same error.

seth · 2025-01-09 15:03:19

Looks like it can't connect the asusd via dbus, though?

dbus-send --system --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames | sed '/string/!d; s/^\s*string //g
dbus-send --session --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames | sed '/string/!d; s/^\s*string //g

(If you've qdbus* installed, "qdbus6 --system" and "qdbus6" will do as well

BluNate · 2025-01-09 19:58:50

seth wrote:

Looks like it can't connect the asusd via dbus, though?
dbus-send --system --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames | sed '/string/!d; s/^\s*string //g
dbus-send --session --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.ListNames | sed '/string/!d; s/^\s*string //g
(If you've qdbus* installed, "qdbus6 --system" and "qdbus6" will do as well

The second quote on those commands seem to have left, but here's what I got:
--System

"org.freedesktop.DBus"
":1.0"
":1.1"
":1.2"
":1.3"
":1.4"
":1.7"
":1.8"
":1.9"
":1.10"
":1.11"
":1.12"
":1.25"
":1.26"
":1.27"
":1.28"
":1.30"
":1.31"
":1.32"
":1.33"
":1.34"
":1.35"
":1.36"
":1.41"
":1.45"
":1.47"
":1.56"
":1.61"
"fi.w1.wpa_supplicant1"
"net.connman.iwd"
"org.asuslinux.Daemon"
"org.bluez"
"org.freedesktop.DisplayManager"
"org.freedesktop.NetworkManager"
"org.freedesktop.PolicyKit1"
"org.freedesktop.RealtimeKit1"
"org.freedesktop.login1"
"org.freedesktop.systemd1"

--Session

"org.freedesktop.DBus"
":1.0"
":1.1"
":1.2"
":1.3"
":1.5"
":1.6"
":1.18"
":1.19"
":1.20"
":1.21"
":1.22"
":1.24"
":1.25"
":1.26"
":1.28"
":1.30"
":1.31"
":1.32"
":1.33"
":1.34"
":1.35"
":1.44"
":1.45"
":1.48"
":1.49"
":1.50"
":1.52"
":1.53"
":1.54"
"ca.desrt.dconf"
"fr.arouillard.waybar"
"org.PulseAudio1"
"org.a11y.Bus"
"org.freedesktop.Notifications"
"org.freedesktop.ScreenSaver"
"org.freedesktop.impl.portal.PermissionStore"
"org.freedesktop.impl.portal.desktop.gtk"
"org.freedesktop.impl.portal.desktop.hyprland"
"org.freedesktop.portal.Desktop"
"org.freedesktop.portal.Documents"
"org.freedesktop.systemd1"
"org.gtk.vfs.Daemon"
"org.kde.StatusNotifierHost-1676-0"
"org.kde.StatusNotifierWatcher"
"org.mozilla.firefox.L2hvbWUvYmx1Ly5tb3ppbGxhL2ZpcmVmb3gvc29hOHNuZ2cuZGVmYXVsdC1yZWxlYXNl"
"org.pulseaudio.Server"

seth · 2025-01-09 20:12:40

"org.asuslinux.Daemon" is there - the error in https://www.reddit.com/r/ZephyrusG14/co … _panicked/ indicate to fail to dbus activate it (which is pointless if it's running) but did you try to establish a dbus activation policy as explained in the first response nevertheless and allow asusctl to launch asusd this way?

BluNate · 2025-01-09 20:47:59

seth wrote:

"org.asuslinux.Daemon" is there - the error in https://www.reddit.com/r/ZephyrusG14/co … _panicked/ indicate to fail to dbus activate it (which is pointless if it's running) but did you try to establish a dbus activation policy as explained in the first response nevertheless and allow asusctl to launch asusd this way?

I got it working, but I don't see any options to change voltage or frequency, do I need to config that?
Profiles looked promising, but didn't seem to help.

Last edited by BluNate (2025-01-09 21:23:25)

seth · 2025-01-09 21:56:17

https://asus-linux.org/manual/asusctl-manual/

Bios control
Some options that you find in Armory Crate are available under this controller, so far there is:
POST sound: this is the sound you hear on bios boot post
GPU MUX: this controls if the dGPU is the only GPU, making it the main GPU and disabling the iGPU
These options are not written to the config file as they are stored in efivars. The only way to change these is to use the exposed safe dbus methods, or use the asusctl CLI tool.

Nothing about any voltage control.

It is https://preisvergleich.heise.de/asus-tu … 00905.html this thing?
A "gaming" notebook and the manual explains how to push the power button and use the touchpad and windows systemsettings to adjust the brightness and the advanced bios features will allow you to boot from usb.
Is that some sort of joke?
A *gaming* notebook you cannot overclock/control?

Can you actually configure that via the windows armoury control?

BluNate · 2025-01-09 23:54:38

seth wrote:

Nothing about any voltage control.
It is https://preisvergleich.heise.de/asus-tu … 00905.html this thing?
A "gaming" notebook and the manual explains how to push the power button and use the touchpad and windows systemsettings to adjust the brightness and the advanced bios features will allow you to boot from usb.
Is that some sort of joke?
A *gaming* notebook you cannot overclock/control?
Can you actually configure that via the windows armoury control?

Yea, you had manual control over the clock and voltage of both CPU and GPU in that app [+fan curve con]

I have nothing else to say but 'worked on windows' - even if I almost never touched those options other than to crank it and see what happens in heavy games

Last edited by BluNate (2025-01-09 23:57:10)

mytArch · 2025-01-10 00:34:45

Is there any possibility that changing the power profile might help? ('asusctl can support setting a power profile via platform_profile drivers')

BluNate · 2025-01-10 00:37:13

mytArch wrote:

Is there any possibility that changing the power profile might help? ('asusctl can support setting a power profile via platform_profile drivers')

I think that's what I just tried - the quiet/balanced/preformance profiles didn't seem to do anything

mytArch · 2025-01-10 00:41:58

Okay have you considered whether there's a bios update that might help?
Obviously a double-edged sword, as sometimes those updates make matters worse, but you could try googling to check others experience. (I've seen some negative reports for 316 for other models, but not found anything for yours.)
Seems a little surprising that AMD is leaving users on a top shelf CPU to just deal with this, would have expected more.

Last edited by mytArch (2025-01-10 00:43:31)

BluNate · 2025-01-10 02:32:11

mytArch wrote:

Okay have you considered whether there's a bios update that might help?
Obviously a double-edged sword, as sometimes those updates make matters worse, but you could try googling to check others experience. (I've seen some negative reports for 316 for other models, but not found anything for yours.)
Seems a little surprising that AMD is leaving users on a top shelf CPU to just deal with this, would have expected more.

yea, i'm on the latest bios revision afaik

mytArch · 2025-01-10 03:50:04

Is using Ryzen Master in Windows an option?
I've read reports that Ryzen Master CPU / 'overclocking' settings are written to an area of bios and - I'm speculating here - potentially thus might apply for subsequent boots into Linux. Do you know if that is correct?

Last edited by mytArch (2025-01-10 03:50:42)

BluNate · 2025-01-10 04:35:46

mytArch wrote:

Is using Ryzen Master in Windows an option?
I've read reports that Ryzen Master CPU / 'overclocking' settings are written to an area of bios and - I'm speculating here - potentially thus might apply for subsequent boots into Linux. Do you know if that is correct?

I have no experience with that software, so I have no clue lol

Arch Linux

#1 2025-01-05 21:05:44

Arch crashing

#2 2025-01-06 01:37:53

Re: Arch crashing

#3 2025-01-06 03:54:09

Re: Arch crashing

#4 2025-01-06 16:04:25

Re: Arch crashing

#5 2025-01-06 16:27:31

Re: Arch crashing

#6 2025-01-07 01:26:45

Re: Arch crashing

#7 2025-01-07 04:15:55

Re: Arch crashing

#8 2025-01-07 16:05:03

Re: Arch crashing

#9 2025-01-07 17:28:52

Re: Arch crashing

#10 2025-01-07 20:31:43

Re: Arch crashing

#11 2025-01-07 20:35:07

Re: Arch crashing

#12 2025-01-07 20:41:12

Re: Arch crashing

#13 2025-01-09 06:53:17

Re: Arch crashing

#14 2025-01-09 15:03:19

Re: Arch crashing

#15 2025-01-09 19:58:50

Re: Arch crashing

#16 2025-01-09 20:12:40

Re: Arch crashing

#17 2025-01-09 20:47:59

Re: Arch crashing

#18 2025-01-09 21:56:17

Re: Arch crashing

#19 2025-01-09 23:54:38

Re: Arch crashing

#20 2025-01-10 00:34:45

Re: Arch crashing

#21 2025-01-10 00:37:13

Re: Arch crashing

#22 2025-01-10 00:41:58

Re: Arch crashing

#23 2025-01-10 02:32:11

Re: Arch crashing

#24 2025-01-10 03:50:04

Re: Arch crashing

#25 2025-01-10 04:35:46

Re: Arch crashing

Board footer