[TRACKING] Freezing Arch Linux AMD

Greetings,

I’ve recently recieved the AMD mainboard, and I’ve been experiencing random freezing in Gnome under Arch Linux. The only recovery option is a hard reboot.

I haven’t been able to figure out the root cause, however seeing these messages in the sys logs after the crash occurs.

[drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2

I’m currently on BIOS version 03.03

2 Likes

Please try adding this to your grub parameters and update grub.

GRUB_CMDLINE_LINUX_DEFAULT=

And adding in this debug mask:

amdgpu.dcdebugmask=0x10

Make sure to update grub afterward with grub-mkconfig per your own configuration, reboot. Then report back.

1 Like

Thanks for the suggestion! I’ve updated the kernel params on my install.
I’m using dracut/systemd-boot, will report back if the freezing occurs.

I’m seeing a few touchpad errors in dmesg as well. Should I create a new thread for those?

Hi @Smig_Tech ,

This thread should suffice, perhaps change “Freezing” to “Issues with”? or something similar.
do post your dmesg errors, thanks. :slight_smile:

1 Like

EDIT: I’m having trouble locating the edit button for the original post. :man_facepalming:

It can get a bit spammy, but these are the common errors I’m seeing. The touch pad has been a bit inconsistent sometimes laggy. I’ve tried reseating the touchpad cable, unfortunately did not help.

[Nov 6 20:11] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[Nov 6 20:15] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[Nov 6 20:20] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[Nov 6 20:24] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[Nov 6 20:27] i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration

I’ve got the same errors; running arch with plasma though.

[131484.207000] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[131639.046823] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[131692.186786] i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration
[131845.258538] i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration

These are spamming pretty constantly and I’m also experiencing the freezes while this is going on. I haven’t had to force a reboot though; if I wait for a few minutes it comes back. If I was doing something important at the time I wouldn’t have that luxury though.

I also noticed these i2c errors in dmesg. For me they come in bursts every once in a while, they’re not too frequent, and I also don’t have any freezes (since upgrading to firmware 3.03). I figured they were harmless. With some context to show timing:

[   55.427501] rfkill: input handler enabled
[   56.353230] warning: `cinnamon' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl802
11
[  359.481849] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[  399.486523] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[  590.064311] i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration
[  654.123909] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[  852.197012] i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration
[  901.219415] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[ 1040.044662] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[ 1133.277971] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[ 1379.580224] i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration
[ 1420.708595] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[ 1688.233264] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[ 2431.040790] i2c_designware AMDI0010:00: i2c_dw_handle_tx_abort: lost arbitration
[ 2833.533958] i2c_hid_acpi i2c-FRMW0005:00: i2c_hid_get_input: incomplete report (7/65535)
[ 2842.616193] wlan0: deauthenticating from 24:4b:fe:0b:44:7c by local choice (Reason: 3=DEAUTH_LEAVING)
[ 2843.000198] ucsi_acpi USBC000:00: ucsi_handle_connector_change: ACK failed (-110)
[ 2843.309913] PM: suspend entry (s2idle)
[ 2843.312983] Filesystems sync: 0.003 seconds

I did have a different error filling my dmesg (and annoying me), related to xhci which I know is usb, so I swapped my front left card from usb-a to hdmi, and it went away … sorry I can’t be more specific, maybe I’ll try to trigger it again …

Excellent reports everyone. Appreciate it. We have an internal ticket that is being addressed regarding the i2c errors. We have our own logs as well.

2 Likes

I’ve also been able to see this same log output in dmesg while also experiencing freezing and stuttering behavior (as I imagine existed with BIOS 3.02.) I’m running Debian Testing, Gnome, BIOS 3.03 as delivered with the laptop.

Linux framework 6.5.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.10-1 (2023-11-03) x86_64 GNU/Linux
2 Likes

I found some related info at [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3 log spam on 5.16.3 (#1887) · Issues · drm / amd · GitLab

1 Like

Hm I encounter the same errors on debian stable with backported 6.5.0-3 and latest firmware form kernel.org, with same freezing and stuttering behavior. As soon as the screen is of the machine freezes. Only a hard shutdown helps.

Still experiencing the freezing from the touchpad.

are you by any chance running 4800MTs ram?

Appreciate everyone’s reports on this.

For those just visiting:

Thanks Matt! Are you tracking two separate issues, or just one? I am experiencing the issue and symptoms at the top of this thread, but nothing related to the touchpad or i2c, as far as I can tell.

We have an internal ticket for i2c errors as it affects supported distros.

The DMUB error is tracked here at the link you provided.

1 Like