# \[TRACKING\] Freezing Arch Linux AMD **URL:** \ **Category:** Linux\ **Tags:** arch\ **Created:** [November 5, 2023, 9:44pm UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495 "2023-11-05T21:44:04Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Smig\_Tech](https://avatars.discourse-cdn.com/v4/letter/s/d6d6ee/32.png) [@Smig\_Tech](https://community.frame.work/u/Smig_Tech)\ **Post date:** [November 5, 2023, 9:44pm UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/1 "2023-11-05T21:44:04Z")
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. ```auto [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2 ``` I’m currently on BIOS version 03.03 ---
**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\ **Post date:** [November 6, 2023, 7:47pm UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/2 "2023-11-06T19:47:54Z")
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. ---
**Author:** ![Smig\_Tech](https://avatars.discourse-cdn.com/v4/letter/s/d6d6ee/32.png) [@Smig\_Tech](https://community.frame.work/u/Smig_Tech)\ **Post date:** [November 7, 2023, 1:05am UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/3 "2023-11-07T01:05:58Z")
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? ---
**Author:** ![Loell\_Framework](https://avatars.discourse-cdn.com/v4/letter/l/9f8e36/32.png) [@Loell\_Framework](https://community.frame.work/u/Loell_Framework)\ **Post date:** [November 7, 2023, 1:29am UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/4 "2023-11-07T01:29:26Z")
Hi @Smig_Tech , This thread should suffice, perhaps change “Freezing” to “Issues with”? or something similar. do post your dmesg errors, thanks. 🙂 ---
**Author:** ![Smig\_Tech](https://avatars.discourse-cdn.com/v4/letter/s/d6d6ee/32.png) [@Smig\_Tech](https://community.frame.work/u/Smig_Tech)\ **Post date:** [November 7, 2023, 2:01am UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/5 "2023-11-07T02:01:54Z")
EDIT: I’m having trouble locating the edit button for the original post. 🤦‍♂️ 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. ```auto [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 ``` ---
**Author:** ![M.Sanchez-Ramirez](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@M.Sanchez-Ramirez](https://community.frame.work/u/M.Sanchez-Ramirez)\ **Post date:** [November 7, 2023, 3:12am UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/6 "2023-11-07T03:12:57Z")
I’ve got the same errors; running arch with plasma though. ```auto [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. ---
**Author:** ![pierce](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/pierce/32/18894_2.png) [@pierce](https://community.frame.work/u/pierce)\ **Post date:** [November 7, 2023, 5:28am UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/7 "2023-11-07T05:28:09Z")
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: ```auto [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 … ---
**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\ **Post date:** [November 7, 2023, 7:09pm UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/8 "2023-11-07T19:09:01Z")
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. ---
**Author:** ![Sharp\_Hall](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/sharp_hall/32/20047_2.png) [@Sharp\_Hall](https://community.frame.work/u/Sharp_Hall)\ **Post date:** [November 12, 2023, 2:30am UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/9 "2023-11-12T02:30:11Z")
> [@Smig\_Tech](#): > > `[drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2` 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. ```auto Linux framework 6.5.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.10-1 (2023-11-03) x86_64 GNU/Linux ``` ---
**Author:** ![Sharp\_Hall](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/sharp_hall/32/20047_2.png) [@Sharp\_Hall](https://community.frame.work/u/Sharp_Hall)\ **Post date:** [November 12, 2023, 2:37am UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/10 "2023-11-12T02:37:42Z")
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](https://gitlab.freedesktop.org/drm/amd/-/issues/1887#note_1992900) ---
**Author:** ![Michael\_Schmid](https://avatars.discourse-cdn.com/v4/letter/m/c37758/32.png) [@Michael\_Schmid](https://community.frame.work/u/Michael_Schmid)\ **Post date:** [November 12, 2023, 9:33am UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/11 "2023-11-12T09:33:02Z")
> [@Sharp\_Hall](#): > > > [@Smig\_Tech](#): > > > > `[drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2` > > 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. > > ```auto > Linux framework 6.5.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.10-1 (2023-11-03) x86_64 GNU/Linux > > ``` Hm I encounter the same errors on debian stable with backported 6.5.0-3 and latest firmware form [kernel.org](http://kernel.org), with same freezing and stuttering behavior. As soon as the screen is of the machine freezes. Only a hard shutdown helps. ---
**Author:** ![Smig\_Tech](https://avatars.discourse-cdn.com/v4/letter/s/d6d6ee/32.png) [@Smig\_Tech](https://community.frame.work/u/Smig_Tech)\ **Post date:** [November 14, 2023, 12:24am UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/12 "2023-11-14T00:24:52Z")
Still experiencing the freezing from the touchpad. ![Screenshot from 2023-11-13 19-23-46](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/b/c/bc93bfefd7e2828d8f5038c5abc3586f1a5bfe0b.png) ---
**Author:** ![TossedTripod645](https://avatars.discourse-cdn.com/v4/letter/t/a9adbd/32.png) [@TossedTripod645](https://community.frame.work/u/TossedTripod645)\ **Post date:** [November 14, 2023, 4:53pm UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/13 "2023-11-14T16:53:14Z")
are you by any chance running 4800MTs ram? ---
**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\ **Post date:** [November 15, 2023, 1:42am UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/14 "2023-11-15T01:42:36Z")
Appreciate everyone’s reports on this. For those just visiting: > [@\[TRACKING\] Freezing Arch Linux AMD](http://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/8): > > 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. ---
**Author:** ![Sharp\_Hall](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/sharp_hall/32/20047_2.png) [@Sharp\_Hall](https://community.frame.work/u/Sharp_Hall)\ **Post date:** [November 15, 2023, 3:30am UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/15 "2023-11-15T03:30:25Z")
> [@Matt\_Hartley](#): > > Appreciate everyone’s reports on this. > [@Matt\_Hartley](#): > > 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. 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. ---
**Author:** ![Matt\_Hartley](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/matt_hartley/32/13623_2.png) [@Matt\_Hartley](https://community.frame.work/u/Matt_Hartley)\ **Post date:** [November 15, 2023, 5:58pm UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/16 "2023-11-15T17:58:54Z")
> [@Sharp\_Hall](#): > > 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](http://community.frame.work/t/officially-supported-vs-compatible-community-supported-linux-distributions/40041). The DMUB error is tracked here [at the link you provided](https://gitlab.freedesktop.org/drm/amd/-/issues/1887#note_1992900). ---
**Author:** ![fw13amd](https://avatars.discourse-cdn.com/v4/letter/f/bb73d2/32.png) [@fw13amd](https://community.frame.work/u/fw13amd)\ **Post date:** [December 20, 2023, 9:15pm UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/17 "2023-12-20T21:15:45Z")
Started getting this on tumbleweed, kernel 6.6.6. No external monitor attached, mostly happens while on YouTube or intellij idea. Hard reset only way out, very disruptive for work. Tried Fedora 39 on the same kernel version (fedora’s take on it), and also got a freeze but here it was recoverable, system became responsive again after a few seconds. Didn’t think of copy pasting my dmesg, but I got a bunch of amdgpu errors that resemble those mentioned here, with something about queueing ---
**Author:** ![Alex\_S](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/alex_s/32/24003_2.png) [@Alex\_S](https://community.frame.work/u/Alex_S)\ **Post date:** [December 20, 2023, 11:18pm UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/18 "2023-12-20T23:18:37Z")
> [@fw13amd](#): > > Started getting this on tumbleweed, kernel 6.6.6. Are you seeing the issue on 6.6.7 or newer? ---
**Author:** ![fw13amd](https://avatars.discourse-cdn.com/v4/letter/f/bb73d2/32.png) [@fw13amd](https://community.frame.work/u/fw13amd)\ **Post date:** [December 21, 2023, 8:55am UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/19 "2023-12-21T08:55:51Z")
Haven’t tried on anything newer. I’m jumping back and forth between tumbleweed and Fedora, but since they’re both on the same kernel now, I’m back to using TW, since both distros will crash on my eventually. This morning I got this on fedora, user session totally borked, both screens turned white (but mouse cursor was changing from pointer to text according to where I moved it, so the DE itself was running fine, just with a coat of white paint on top. I Ctrl Alt F7 into a cli session and journalctl -k showed this ![PXL_20231221_083944489](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/a/1/a1d44a72d785748e65f624054463ca3a930b0d9d.jpeg) Hope it gets fixed soon, right now I feel like a beta tester although this HW has been announced several months ago. ---
**Author:** ![Smig\_Tech](https://avatars.discourse-cdn.com/v4/letter/s/d6d6ee/32.png) [@Smig\_Tech](https://community.frame.work/u/Smig_Tech)\ **Post date:** [December 21, 2023, 11:44am UTC](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495/20 "2023-12-21T11:44:44Z")
> Hope it gets fixed soon, right now I feel like a beta tester although this HW has been announced several months ago. That’s how Linux is on new hardware, takes time for devs to get some stuff working. Are you on the latest bios from from framework? v03.03 `# dmidecode -s bios-version` [Next page](https://community.frame.work/t/tracking-freezing-arch-linux-amd/39495.md?page=2)