[SOLVED] AMD system hangs at idling/light tasks

MarbleXeno · 2023-07-04 14:28:37

Hey, my PC started behaving abnormally recently. I can't say when exactly it started happening though.

From time to time, everything on the desktop hangs, including my mouse cursor. I can't move it or do anything. Only turning my PC off and on solves it. The OS works fine afterwards.
After 'the crash', when the OS is booting, there's this error message displayed:

Jul 04 14:08:09 archlinux kernel: mce: [Hardware Error]: CPU 9: Machine Check: 0 Bank 5: bea0000000000108
Jul 04 14:08:09 archlinux kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffffc0be4722 MISC d012000100000000 SYND 4d000000 IPID 500b000000000
Jul 04 14:08:09 archlinux kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1688472486 SOCKET 0 APIC 9 microcode 8701030

I suspected my RAM, so I did MemTest86, but I passed the test with no issues.

This issue happened a couple of times, but I specifically remember it happening:
1) While watching YT with hardware acceleration in Firefox
2) While trying to use AMD HIP in Blender. It happened precisely when Blender said something about loading the AMD driver. I don't remember exactly what it said, but it said it was loading something from AMD
3) At doing nothing, leaving my PC to go grab something to eat
4) while installing a game

It never happened while gaming.

My PC specs:
MOBO:MSI B450-A PRO MAX
CPU: AMD Ryzen 5 3600XT (didn’t do OC)
GPU: ASUS Raden 6650XT OC Edition
RAM: G.SKILL 2x16GB 3200MHz Ripjaws (XMP Enabled)
PSU: be quiet! System Power 10 750W 80 Plus Bronze
OS Disk: ADATA XPG GAMMIX 500 GB NVME SSD

System:
Arch Linux x86_64
Kernel: 6.4.1-zen1-1-zen
mesa-git & lib32-mesa-git from AUR (happened on the regular version too)

Last edited by MarbleXeno (2023-07-06 20:41:26)

MarbleXeno · 2023-07-04 14:31:17

This is very similar to this issue on AMD's GitLab: https://gitlab.freedesktop.org/drm/amd/-/issues/2447
In fact, there's a guy who uploaded a video of the system hanging and it lookes very similar to mine (can't move the mouse cursor or do anything): https://gitlab.freedesktop.org/drm/amd/ … ooping.mp4

I don't see anybody with the MCE errors though...

Last edited by MarbleXeno (2023-07-04 14:33:07)

ewaller · 2023-07-04 16:00:14

MCE = Machine Check Exception
Sounds like you've a hardware problem.

When the 'freeze' happens, do your keyboard LEDs blink? That would indicate a kernel panic.

Are you under Volting? overclocking?

MarbleXeno · 2023-07-04 18:31:18

Nothing is overclocked or undervolted.
Nothing blinks or beeps when the freeze happens.
There are no unusual things happening when the freeze occurs.

seth · 2023-07-04 20:03:56

* https://wiki.archlinux.org/title/Ryzen#Troubleshooting (there's a bunch of suggestsions, at least limit the c-states to "1" and adjust the curve optimizer in your BIOS)
* Also try the not-zen kernel and the lts one
* Blender isn't loading any kernel modules or display drivers and
* "I passed the test with no issues" is meaningless if that was just one cycle, at least run memtest86 over night.
* See whether you can https://wiki.archlinux.org/title/Keyboa … el_(SysRq) out of the frozen system and then look out for errors in the previous boot.

MarbleXeno · 2023-07-04 21:24:51

My mistake, Blender wasn't loading the kernel driver, I meant the AMD HIP driver. It crashed while I was trying using it.
I run MemTest86 for a longer period of time with and without XMP and it still shows no errors.
I also tried Fedora 38, with the regular kernel, and the issue also happened there. I left my PC while it was installing a game and when I came back, I tried moving my mouse but I couldn't, the system was freezed again and I had to restart. Weird thing is, Fedora didn't show any Error message.
I tried Fedora because I thought maybe it was the more recent Kernel version of Arch but no, still happens there. Anyways, I'm back on Arch.

Last edited by MarbleXeno (2023-07-04 21:27:40)

MarbleXeno · 2023-07-04 21:30:53

I changed Power Idle Control to Typical current idle. Will report back if anything happens.

Last edited by MarbleXeno (2023-07-04 21:39:24)

agapito · 2023-07-05 08:08:30

MarbleXeno wrote:

Hey, my PC started behaving abnormally recently. I can't say when exactly it started happening though.
From time to time, everything on the desktop hangs, including my mouse cursor. I can't move it or do anything. Only turning my PC off and on solves it. The OS works fine afterwards.
After 'the crash', when the OS is booting, there's this error message displayed:
Jul 04 14:08:09 archlinux kernel: mce: [Hardware Error]: CPU 9: Machine Check: 0 Bank 5: bea0000000000108
Jul 04 14:08:09 archlinux kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffffc0be4722 MISC d012000100000000 SYND 4d000000 IPID 500b000000000
Jul 04 14:08:09 archlinux kernel: mce: [Hardware Error]: PROCESSOR 2:870f10 TIME 1688472486 SOCKET 0 APIC 9 microcode 8701030

If you are suffering idle hangs means that one of your CPU cores needs more voltage, the problem is your Zen 2 CPU doesn´t support Curve Optimizer, so you will have to raise the voltage to the entire CPU.

Instead of turning up the voltage beforehand you can try disabling the C6 states, which is exactly what you have done. If you still have hangs you will have no choice but to apply a positive voltage offset to the entire CPU.

MarbleXeno wrote:

2) While trying to use AMD HIP in Blender. It happened precisely when Blender said something about loading the AMD driver. I don't remember exactly what it said, but it said it was loading something from AMD.

Blender will crash your RDNA2 card if you try to use HIP. It will work, installing rocm packages from staging repo (5.6 version)

MarbleXeno · 2023-07-05 10:14:19

Yeah, the hangs were mostly happening when idling, so it’s probably that.

I reseated everything in the PC, updated BIOS and set everything to default. No hangs observed. If I do notice hangs I will probably just disable C states. Thanks for help!

Last edited by MarbleXeno (2023-07-05 10:15:36)

agapito · 2023-07-05 10:48:02

If u use Windows, you could try CoreCycler, which is a tool for detecting this type of crashes, assigning light loads to the cores intermittently.

https://github.com/sp00n/corecycler

Even if you no longer suffer crashes, your CPU may not perform calculations correctly and you may suffer data corruption in the future, and with this program you can ensure the proper functioning of all your cores.

MarbleXeno · 2023-07-05 21:22:00

Today, while watching a stream on Twitch, my PC again froze. This time, during the reboot there were no error messages.
I looked in the journalctl and I found this:

Jul 05 23:10:06 hiroshima kernel: NMI watchdog: Watchdog detected hard LOCKUP on cpu 10
Jul 05 23:10:06 hiroshima kernel: Modules linked in: uinput rfcomm cmac algif_hash algif_skcipher af_alg bnep exfat snd_seq_dummy snd_hrtimer snd_seq ccm uas usb_storage mousedev btusb btrtl btbcm btintel btmtk snd_usb_audio joydev blu>
Jul 05 23:10:06 hiroshima kernel:  pkcs8_key_parser crypto_user fuse dm_mod loop ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 nvme nvme_core crc32c_intel xhci_pci xhci_pci_renesas nvme_common
Jul 05 23:10:06 hiroshima kernel: CPU: 10 PID: 422 Comm: NetworkManager Not tainted 6.4.1-zen2-1-zen #1 283fe783debeadb699c9eb91cc8199825c9de3d6
Jul 05 23:10:06 hiroshima kernel: Hardware name: Micro-Star International Co., Ltd MS-7B86/B450-A PRO MAX (MS-7B86), BIOS M.I0 04/27/2023
Jul 05 23:10:06 hiroshima kernel: RIP: 0010:iwl_trans_pcie_read32+0x14/0x20 [iwlwifi]
Jul 05 23:10:06 hiroshima kernel: Code: 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 89 f6 48 03 b7 18 29 00 00 8b 06 <c3> cc cc cc cc 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90
Jul 05 23:10:06 hiroshima kernel: RSP: 0018:ffffb4cd41067420 EFLAGS: 00000086
Jul 05 23:10:06 hiroshima kernel: RAX: 00000000ffffffff RBX: ffff8dd4cb1b4028 RCX: 000000000000000a
Jul 05 23:10:06 hiroshima kernel: RDX: 00000000000097da RSI: ffffb4cd42538024 RDI: ffff8dd4cb1b4028
Jul 05 23:10:06 hiroshima kernel: RBP: 000000000000028a R08: 0000000000003a98 R09: 0000000000000000
Jul 05 23:10:06 hiroshima kernel: R10: ffff8dd4c5662800 R11: 000000000000001d R12: 0000000000000024
Jul 05 23:10:06 hiroshima kernel: R13: 0000000000000011 R14: 0000000000000001 R15: 0000000000003a98
Jul 05 23:10:06 hiroshima kernel: FS:  00007f75d8676200(0000) GS:ffff8ddbdea80000(0000) knlGS:0000000000000000
Jul 05 23:10:06 hiroshima kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 05 23:10:06 hiroshima kernel: CR2: 00007f35f0940000 CR3: 0000000106cc8000 CR4: 0000000000350ee0
Jul 05 23:10:06 hiroshima kernel: Call Trace:
Jul 05 23:10:06 hiroshima kernel:  <NMI>
Jul 05 23:10:06 hiroshima kernel:  ? watchdog_overflow_callback+0xc1/0x120
Jul 05 23:10:06 hiroshima kernel:  ? __perf_event_overflow+0x114/0x3a0
Jul 05 23:10:06 hiroshima kernel:  ? x86_pmu_handle_irq+0x145/0x1b0
Jul 05 23:10:06 hiroshima kernel:  ? amd_pmu_handle_irq+0x4b/0xc0
Jul 05 23:10:06 hiroshima kernel:  ? perf_event_nmi_handler+0x2a/0x50
Jul 05 23:10:06 hiroshima kernel:  ? nmi_handle+0x5e/0x150
Jul 05 23:10:06 hiroshima kernel:  ? default_do_nmi+0x40/0x1d0
Jul 05 23:10:06 hiroshima kernel:  ? exc_nmi+0x136/0x180
Jul 05 23:10:06 hiroshima kernel:  ? end_repeat_nmi+0x16/0x67
Jul 05 23:10:06 hiroshima kernel:  ? iwl_trans_pcie_read32+0x14/0x20 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  ? iwl_trans_pcie_read32+0x14/0x20 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  ? iwl_trans_pcie_read32+0x14/0x20 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  </NMI>
Jul 05 23:10:06 hiroshima kernel:  <TASK>
Jul 05 23:10:06 hiroshima kernel:  iwl_poll_bit+0x53/0xd0 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  ? mod_timer+0x22f/0x3d0
Jul 05 23:10:06 hiroshima kernel:  __iwl_trans_pcie_grab_nic_access+0xb7/0x150 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  iwl_pcie_enqueue_hcmd+0x5b6/0xb20 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  iwl_trans_txq_send_hcmd+0x15a/0x450 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  ? __kmem_cache_alloc_node+0x198/0x330
Jul 05 23:10:06 hiroshima kernel:  ? cfg80211_sinfo_alloc_tid_stats+0x40/0x80 [cfg80211 5a721c454c6aadc41fa72c37eee18cb3a3ad95fc]
Jul 05 23:10:06 hiroshima kernel:  iwl_trans_send_cmd+0x98/0x100 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  iwl_mvm_request_statistics+0xa1/0x210 [iwlmvm e88b72bec1d0893e71413e9f4e29f96807d0f7f6]
Jul 05 23:10:06 hiroshima kernel:  iwl_mvm_mac_sta_statistics+0x185/0x3a0 [iwlmvm e88b72bec1d0893e71413e9f4e29f96807d0f7f6]
Jul 05 23:10:06 hiroshima kernel:  sta_set_sinfo+0xc0/0xc20 [mac80211 221b70a8399e10b1336b2e420e75d052087b1899]
Jul 05 23:10:06 hiroshima kernel:  ieee80211_dump_station+0x6f/0x90 [mac80211 221b70a8399e10b1336b2e420e75d052087b1899]
Jul 05 23:10:06 hiroshima kernel:  nl80211_dump_station+0x13f/0x290 [cfg80211 5a721c454c6aadc41fa72c37eee18cb3a3ad95fc]
Jul 05 23:10:06 hiroshima kernel:  netlink_dump+0x15a/0x400
Jul 05 23:10:06 hiroshima kernel:  __netlink_dump_start+0x1b4/0x270
Jul 05 23:10:06 hiroshima kernel:  genl_rcv_msg+0x3f7/0x490
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_nl80211_dump_station+0x10/0x10 [cfg80211 5a721c454c6aadc41fa72c37eee18cb3a3ad95fc]
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_genl_start+0x10/0x10
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_nl80211_dump_station+0x10/0x10 [cfg80211 5a721c454c6aadc41fa72c37eee18cb3a3ad95fc]
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_genl_parallel_done+0x10/0x10
Jul 05 23:10:06 hiroshima kernel:  ? __ep_eventpoll_poll.isra.0+0x189/0x1c0
Jul 05 23:10:06 hiroshima kernel:  ? free_unref_page+0x330/0x710
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_genl_rcv_msg+0x10/0x10
Jul 05 23:10:06 hiroshima kernel:  netlink_rcv_skb+0x58/0x110
Jul 05 23:10:06 hiroshima kernel:  genl_rcv+0x28/0x40
Jul 05 23:10:06 hiroshima kernel:  netlink_unicast+0x53e/0x5e0
Jul 05 23:10:06 hiroshima kernel:  netlink_sendmsg+0x24f/0x4d0
Jul 05 23:10:06 hiroshima kernel:  sock_sendmsg+0x93/0xa0
Jul 05 23:10:06 hiroshima kernel:  ____sys_sendmsg+0x26f/0x300
Jul 05 23:10:06 hiroshima kernel:  __sys_sendmsg+0x1d9/0x2b0
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_pollwake+0x10/0x10
Jul 05 23:10:06 hiroshima kernel:  ? __x64_sys_epoll_wait+0x17c/0x1e0
Jul 05 23:10:06 hiroshima kernel:  do_syscall_64+0x5d/0x90
Jul 05 23:10:06 hiroshima kernel:  ? do_syscall_64+0x6c/0x90
Jul 05 23:10:06 hiroshima kernel:  ? do_syscall_64+0x6c/0x90
Jul 05 23:10:06 hiroshima kernel:  ? do_syscall_64+0x6c/0x90
Jul 05 23:10:06 hiroshima kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Jul 05 23:10:06 hiroshima kernel: RIP: 0033:0x7f75d956ee9d
Jul 05 23:10:06 hiroshima kernel: Code: 28 89 54 24 1c 48 89 74 24 10 89 7c 24 08 e8 4a 69 f7 ff 8b 54 24 1c 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 33 44 89 c7 48 89 44 24 08 e8 9e 69 f7 ff 48
Jul 05 23:10:06 hiroshima kernel: RSP: 002b:00007ffcc8b67c00 EFLAGS: 00000293 ORIG_RAX: 000000000000002e
Jul 05 23:10:06 hiroshima kernel: RAX: ffffffffffffffda RBX: 000055f0d2b63ba0 RCX: 00007f75d956ee9d
Jul 05 23:10:06 hiroshima kernel: RDX: 0000000000000000 RSI: 00007ffcc8b67c40 RDI: 000000000000000b
Jul 05 23:10:06 hiroshima kernel: RBP: 000055f0d2b63ba0 R08: 0000000000000000 R09: 00007f75d963e0f0
Jul 05 23:10:06 hiroshima kernel: R10: 00007f75d963e0f0 R11: 0000000000000293 R12: 00007ffcc8b67cd0
Jul 05 23:10:06 hiroshima kernel: R13: 000055f0d2c6e7e0 R14: 00007ffcc8b67f04 R15: 0000000000000000
Jul 05 23:10:06 hiroshima kernel:  </TASK>
Jul 05 23:10:06 hiroshima kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 23s! [swapper/9:0]
Jul 05 23:10:06 hiroshima kernel: Modules linked in: uinput rfcomm cmac algif_hash algif_skcipher af_alg bnep exfat snd_seq_dummy snd_hrtimer snd_seq ccm uas usb_storage mousedev btusb btrtl btbcm btintel btmtk snd_usb_audio joydev blu>
Jul 05 23:10:06 hiroshima kernel:  pkcs8_key_parser crypto_user fuse dm_mod loop ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 nvme nvme_core crc32c_intel xhci_pci xhci_pci_renesas nvme_common
Jul 05 23:10:06 hiroshima kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 6.4.1-zen2-1-zen #1 283fe783debeadb699c9eb91cc8199825c9de3d6
Jul 05 23:10:06 hiroshima kernel: Hardware name: Micro-Star International Co., Ltd MS-7B86/B450-A PRO MAX (MS-7B86), BIOS M.I0 04/27/2023
Jul 05 23:10:06 hiroshima kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x6e/0x2e0
Jul 05 23:10:06 hiroshima kernel: Code: 77 7f f0 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 3d ff 00 00 00 77 5b 85 c0 74 10 0f b6 03 84 c0 74 09 f3 90 <0f> b6 03 84 c0 75 f7 b8 01 00 00 00 66 89 03 65 48 ff 05 c3 b3 e5
Jul 05 23:10:06 hiroshima kernel: RSP: 0018:ffffb4cd4044cdb0 EFLAGS: 00000202
Jul 05 23:10:06 hiroshima kernel: RAX: 0000000000000001 RBX: ffff8dd4cb1b69b4 RCX: 00000001002b1a00
Jul 05 23:10:06 hiroshima kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8dd4cb1b69b4
Jul 05 23:10:06 hiroshima kernel: RBP: ffff8dd4cb07a8b8 R08: 000000000080158e R09: ffffb4cd4044cf10
Jul 05 23:10:06 hiroshima kernel: R10: 0000000000000006 R11: 00000000000006ae R12: 0000000000a02d38
Jul 05 23:10:06 hiroshima kernel: R13: ffff8dd4cb07a898 R14: ffff8dd4cb1b69b4 R15: 000000000000000b
Jul 05 23:10:06 hiroshima kernel: FS:  0000000000000000(0000) GS:ffff8ddbdea40000(0000) knlGS:0000000000000000
Jul 05 23:10:06 hiroshima kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 05 23:10:06 hiroshima kernel: CR2: 00007f2cc08a2b20 CR3: 0000000145e98000 CR4: 0000000000350ee0
Jul 05 23:10:06 hiroshima kernel: Call Trace:
Jul 05 23:10:06 hiroshima kernel:  <IRQ>
Jul 05 23:10:06 hiroshima kernel:  ? watchdog_timer_fn+0x1a8/0x210
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_watchdog_timer_fn+0x10/0x10
Jul 05 23:10:06 hiroshima kernel:  ? __hrtimer_run_queues+0x121/0x2c0
Jul 05 23:10:06 hiroshima kernel:  ? hrtimer_interrupt+0xfb/0x440
Jul 05 23:10:06 hiroshima kernel:  ? sched_clock_cpu+0xf/0x1b0
Jul 05 23:10:06 hiroshima kernel:  ? __sysvec_apic_timer_interrupt+0x5e/0x170
Jul 05 23:10:06 hiroshima kernel:  ? sysvec_apic_timer_interrupt+0x39/0x90
Jul 05 23:10:06 hiroshima kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jul 05 23:10:06 hiroshima kernel:  ? native_queued_spin_lock_slowpath+0x6e/0x2e0
Jul 05 23:10:06 hiroshima kernel:  _raw_spin_lock+0x29/0x30
Jul 05 23:10:06 hiroshima kernel:  iwl_trans_pcie_grab_nic_access+0x30/0x170 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  iwl_read_prph+0x20/0xc0 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  iwl_txq_log_scd_error+0x143/0x220 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  iwl_txq_stuck_timer+0x41/0x60 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_genl_rcv_msg+0x10/0x10
Jul 05 23:10:06 hiroshima kernel:  netlink_rcv_skb+0x58/0x110
Jul 05 23:10:06 hiroshima kernel:  genl_rcv+0x28/0x40
Jul 05 23:10:06 hiroshima kernel:  netlink_unicast+0x53e/0x5e0
Jul 05 23:10:06 hiroshima kernel:  netlink_sendmsg+0x24f/0x4d0
Jul 05 23:10:06 hiroshima kernel:  sock_sendmsg+0x93/0xa0
Jul 05 23:10:06 hiroshima kernel:  ____sys_sendmsg+0x26f/0x300
Jul 05 23:10:06 hiroshima kernel:  __sys_sendmsg+0x1d9/0x2b0
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_pollwake+0x10/0x10
Jul 05 23:10:06 hiroshima kernel:  ? __x64_sys_epoll_wait+0x17c/0x1e0
Jul 05 23:10:06 hiroshima kernel:  do_syscall_64+0x5d/0x90
Jul 05 23:10:06 hiroshima kernel:  ? do_syscall_64+0x6c/0x90
Jul 05 23:10:06 hiroshima kernel:  ? do_syscall_64+0x6c/0x90
Jul 05 23:10:06 hiroshima kernel:  ? do_syscall_64+0x6c/0x90
Jul 05 23:10:06 hiroshima kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Jul 05 23:10:06 hiroshima kernel: RIP: 0033:0x7f75d956ee9d
Jul 05 23:10:06 hiroshima kernel: Code: 28 89 54 24 1c 48 89 74 24 10 89 7c 24 08 e8 4a 69 f7 ff 8b 54 24 1c 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 33 44 89 c7 48 89 44 24 08 e8 9e 69 f7 ff 48
Jul 05 23:10:06 hiroshima kernel: RSP: 002b:00007ffcc8b67c00 EFLAGS: 00000293 ORIG_RAX: 000000000000002e
Jul 05 23:10:06 hiroshima kernel: RAX: ffffffffffffffda RBX: 000055f0d2b63ba0 RCX: 00007f75d956ee9d
Jul 05 23:10:06 hiroshima kernel: RDX: 0000000000000000 RSI: 00007ffcc8b67c40 RDI: 000000000000000b
Jul 05 23:10:06 hiroshima kernel: RBP: 000055f0d2b63ba0 R08: 0000000000000000 R09: 00007f75d963e0f0
Jul 05 23:10:06 hiroshima kernel: R10: 00007f75d963e0f0 R11: 0000000000000293 R12: 00007ffcc8b67cd0
Jul 05 23:10:06 hiroshima kernel: R13: 000055f0d2c6e7e0 R14: 00007ffcc8b67f04 R15: 0000000000000000
Jul 05 23:10:06 hiroshima kernel:  </TASK>
Jul 05 23:10:06 hiroshima kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 23s! [swapper/9:0]
Jul 05 23:10:06 hiroshima kernel: Modules linked in: uinput rfcomm cmac algif_hash algif_skcipher af_alg bnep exfat snd_seq_dummy snd_hrtimer snd_seq ccm uas usb_storage mousedev btusb btrtl btbcm btintel btmtk snd_usb_audio joydev blu>
Jul 05 23:10:06 hiroshima kernel:  pkcs8_key_parser crypto_user fuse dm_mod loop ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 nvme nvme_core crc32c_intel xhci_pci xhci_pci_renesas nvme_common
Jul 05 23:10:06 hiroshima kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 6.4.1-zen2-1-zen #1 283fe783debeadb699c9eb91cc8199825c9de3d6
Jul 05 23:10:06 hiroshima kernel: Hardware name: Micro-Star International Co., Ltd MS-7B86/B450-A PRO MAX (MS-7B86), BIOS M.I0 04/27/2023
Jul 05 23:10:06 hiroshima kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x6e/0x2e0
Jul 05 23:10:06 hiroshima kernel: Code: 77 7f f0 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 3d ff 00 00 00 77 5b 85 c0 74 10 0f b6 03 84 c0 74 09 f3 90 <0f> b6 03 84 c0 75 f7 b8 01 00 00 00 66 89 03 65 48 ff 05 c3 b3 e5
Jul 05 23:10:06 hiroshima kernel: RSP: 0018:ffffb4cd4044cdb0 EFLAGS: 00000202
Jul 05 23:10:06 hiroshima kernel: RAX: 0000000000000001 RBX: ffff8dd4cb1b69b4 RCX: 00000001002b1a00
Jul 05 23:10:06 hiroshima kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8dd4cb1b69b4
Jul 05 23:10:06 hiroshima kernel: RBP: ffff8dd4cb07a8b8 R08: 000000000080158e R09: ffffb4cd4044cf10
Jul 05 23:10:06 hiroshima kernel: R10: 0000000000000006 R11: 00000000000006ae R12: 0000000000a02d38
Jul 05 23:10:06 hiroshima kernel: R13: ffff8dd4cb07a898 R14: ffff8dd4cb1b69b4 R15: 000000000000000b
Jul 05 23:10:06 hiroshima kernel: FS:  0000000000000000(0000) GS:ffff8ddbdea40000(0000) knlGS:0000000000000000
Jul 05 23:10:06 hiroshima kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 05 23:10:06 hiroshima kernel: CR2: 00007f2cc08a2b20 CR3: 0000000145e98000 CR4: 0000000000350ee0
Jul 05 23:10:06 hiroshima kernel: Call Trace:
Jul 05 23:10:06 hiroshima kernel:  <IRQ>
Jul 05 23:10:06 hiroshima kernel:  ? watchdog_timer_fn+0x1a8/0x210
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_watchdog_timer_fn+0x10/0x10
Jul 05 23:10:06 hiroshima kernel:  ? __hrtimer_run_queues+0x121/0x2c0
Jul 05 23:10:06 hiroshima kernel:  ? hrtimer_interrupt+0xfb/0x440
Jul 05 23:10:06 hiroshima kernel:  ? sched_clock_cpu+0xf/0x1b0
Jul 05 23:10:06 hiroshima kernel:  ? __sysvec_apic_timer_interrupt+0x5e/0x170
Jul 05 23:10:06 hiroshima kernel:  ? sysvec_apic_timer_interrupt+0x39/0x90
Jul 05 23:10:06 hiroshima kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jul 05 23:10:06 hiroshima kernel:  ? native_queued_spin_lock_slowpath+0x6e/0x2e0
Jul 05 23:10:06 hiroshima kernel:  _raw_spin_lock+0x29/0x30
Jul 05 23:10:06 hiroshima kernel:  iwl_trans_pcie_grab_nic_access+0x30/0x170 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  iwl_read_prph+0x20/0xc0 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  iwl_txq_log_scd_error+0x143/0x220 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  iwl_txq_stuck_timer+0x41/0x60 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_genl_rcv_msg+0x10/0x10
Jul 05 23:10:06 hiroshima kernel:  netlink_rcv_skb+0x58/0x110
Jul 05 23:10:06 hiroshima kernel:  genl_rcv+0x28/0x40
Jul 05 23:10:06 hiroshima kernel:  netlink_unicast+0x53e/0x5e0
Jul 05 23:10:06 hiroshima kernel:  netlink_sendmsg+0x24f/0x4d0
Jul 05 23:10:06 hiroshima kernel:  sock_sendmsg+0x93/0xa0
Jul 05 23:10:06 hiroshima kernel:  ____sys_sendmsg+0x26f/0x300
Jul 05 23:10:06 hiroshima kernel:  __sys_sendmsg+0x1d9/0x2b0
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_pollwake+0x10/0x10
Jul 05 23:10:06 hiroshima kernel:  ? __x64_sys_epoll_wait+0x17c/0x1e0
Jul 05 23:10:06 hiroshima kernel:  do_syscall_64+0x5d/0x90
Jul 05 23:10:06 hiroshima kernel:  ? do_syscall_64+0x6c/0x90
Jul 05 23:10:06 hiroshima kernel:  ? do_syscall_64+0x6c/0x90
Jul 05 23:10:06 hiroshima kernel:  ? do_syscall_64+0x6c/0x90
Jul 05 23:10:06 hiroshima kernel:  entry_SYSCALL_64_after_hwframe+0x72/0xdc
Jul 05 23:10:06 hiroshima kernel: RIP: 0033:0x7f75d956ee9d
Jul 05 23:10:06 hiroshima kernel: Code: 28 89 54 24 1c 48 89 74 24 10 89 7c 24 08 e8 4a 69 f7 ff 8b 54 24 1c 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 33 44 89 c7 48 89 44 24 08 e8 9e 69 f7 ff 48
Jul 05 23:10:06 hiroshima kernel: RSP: 002b:00007ffcc8b67c00 EFLAGS: 00000293 ORIG_RAX: 000000000000002e
Jul 05 23:10:06 hiroshima kernel: RAX: ffffffffffffffda RBX: 000055f0d2b63ba0 RCX: 00007f75d956ee9d
Jul 05 23:10:06 hiroshima kernel: RDX: 0000000000000000 RSI: 00007ffcc8b67c40 RDI: 000000000000000b
Jul 05 23:10:06 hiroshima kernel: RBP: 000055f0d2b63ba0 R08: 0000000000000000 R09: 00007f75d963e0f0
Jul 05 23:10:06 hiroshima kernel: R10: 00007f75d963e0f0 R11: 0000000000000293 R12: 00007ffcc8b67cd0
Jul 05 23:10:06 hiroshima kernel: R13: 000055f0d2c6e7e0 R14: 00007ffcc8b67f04 R15: 0000000000000000
Jul 05 23:10:06 hiroshima kernel:  </TASK>
Jul 05 23:10:06 hiroshima kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 23s! [swapper/9:0]
Jul 05 23:10:06 hiroshima kernel: Modules linked in: uinput rfcomm cmac algif_hash algif_skcipher af_alg bnep exfat snd_seq_dummy snd_hrtimer snd_seq ccm uas usb_storage mousedev btusb btrtl btbcm btintel btmtk snd_usb_audio joydev blu>
Jul 05 23:10:06 hiroshima kernel:  pkcs8_key_parser crypto_user fuse dm_mod loop ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 nvme nvme_core crc32c_intel xhci_pci xhci_pci_renesas nvme_common
Jul 05 23:10:06 hiroshima kernel: CPU: 9 PID: 0 Comm: swapper/9 Not tainted 6.4.1-zen2-1-zen #1 283fe783debeadb699c9eb91cc8199825c9de3d6
Jul 05 23:10:06 hiroshima kernel: Hardware name: Micro-Star International Co., Ltd MS-7B86/B450-A PRO MAX (MS-7B86), BIOS M.I0 04/27/2023
Jul 05 23:10:06 hiroshima kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x6e/0x2e0
Jul 05 23:10:06 hiroshima kernel: Code: 77 7f f0 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 3d ff 00 00 00 77 5b 85 c0 74 10 0f b6 03 84 c0 74 09 f3 90 <0f> b6 03 84 c0 75 f7 b8 01 00 00 00 66 89 03 65 48 ff 05 c3 b3 e5
Jul 05 23:10:06 hiroshima kernel: RSP: 0018:ffffb4cd4044cdb0 EFLAGS: 00000202
Jul 05 23:10:06 hiroshima kernel: RAX: 0000000000000001 RBX: ffff8dd4cb1b69b4 RCX: 00000001002b1a00
Jul 05 23:10:06 hiroshima kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8dd4cb1b69b4
Jul 05 23:10:06 hiroshima kernel: RBP: ffff8dd4cb07a8b8 R08: 000000000080158e R09: ffffb4cd4044cf10
Jul 05 23:10:06 hiroshima kernel: R10: 0000000000000006 R11: 00000000000006ae R12: 0000000000a02d38
Jul 05 23:10:06 hiroshima kernel: R13: ffff8dd4cb07a898 R14: ffff8dd4cb1b69b4 R15: 000000000000000b
Jul 05 23:10:06 hiroshima kernel: FS:  0000000000000000(0000) GS:ffff8ddbdea40000(0000) knlGS:0000000000000000
Jul 05 23:10:06 hiroshima kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 05 23:10:06 hiroshima kernel: CR2: 00007f2cc08a2b20 CR3: 0000000145e98000 CR4: 0000000000350ee0
Jul 05 23:10:06 hiroshima kernel: Call Trace:
Jul 05 23:10:06 hiroshima kernel:  <IRQ>
Jul 05 23:10:06 hiroshima kernel:  ? watchdog_timer_fn+0x1a8/0x210
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_watchdog_timer_fn+0x10/0x10
Jul 05 23:10:06 hiroshima kernel:  ? __hrtimer_run_queues+0x121/0x2c0
Jul 05 23:10:06 hiroshima kernel:  ? hrtimer_interrupt+0xfb/0x440
Jul 05 23:10:06 hiroshima kernel:  ? sched_clock_cpu+0xf/0x1b0
Jul 05 23:10:06 hiroshima kernel:  ? __sysvec_apic_timer_interrupt+0x5e/0x170
Jul 05 23:10:06 hiroshima kernel:  ? sysvec_apic_timer_interrupt+0x39/0x90
Jul 05 23:10:06 hiroshima kernel:  ? asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jul 05 23:10:06 hiroshima kernel:  ? native_queued_spin_lock_slowpath+0x6e/0x2e0
Jul 05 23:10:06 hiroshima kernel:  _raw_spin_lock+0x29/0x30
Jul 05 23:10:06 hiroshima kernel:  iwl_trans_pcie_grab_nic_access+0x30/0x170 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  iwl_read_prph+0x20/0xc0 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  iwl_txq_log_scd_error+0x143/0x220 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  iwl_txq_stuck_timer+0x41/0x60 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_iwl_txq_stuck_timer+0x10/0x10 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  call_timer_fn+0x24/0x130
Jul 05 23:10:06 hiroshima kernel:  run_timer_softirq+0x407/0xac0
Jul 05 23:10:06 hiroshima kernel:  ? __pfx_iwl_txq_stuck_timer+0x10/0x10 [iwlwifi e6e461c160a36fc51e02e1826f44fcb87a9bb349]
Jul 05 23:10:06 hiroshima kernel:  ? timerqueue_add+0x98/0xb0
Jul 05 23:10:06 hiroshima kernel:  __do_softirq+0xd1/0x2c8
Jul 05 23:10:06 hiroshima kernel:  irq_exit_rcu+0xc0/0xf0
Jul 05 23:10:06 hiroshima kernel:  sysvec_apic_timer_interrupt+0x72/0x90
Jul 05 23:10:06 hiroshima kernel:  </IRQ>
Jul 05 23:10:06 hiroshima kernel:  <TASK>
Jul 05 23:10:06 hiroshima kernel:  asm_sysvec_apic_timer_interrupt+0x1a/0x20
Jul 05 23:10:06 hiroshima kernel: RIP: 0010:cpuidle_enter_state+0xcc/0x830
Jul 05 23:10:06 hiroshima kernel: Code: 8a c8 1a ff e8 05 f2 ff ff 8b 53 04 49 89 c6 0f 1f 44 00 00 31 ff e8 53 96 19 ff 45 84 ff 0f 85 c4 02 00 00 fb 0f 1f 44 00 00 <45> 85 ed 0f 88 9e 02 00 00 49 63 f5 4c 89 f2 48 8d 04 76 48 8d 04
Jul 05 23:10:06 hiroshima kernel: RSP: 0018:ffffb4cd401bfe90 EFLAGS: 00000246
Jul 05 23:10:06 hiroshima kernel: RAX: ffff8ddbdea73f00 RBX: ffff8dd4c538e400 RCX: 0000000000000000
Jul 05 23:10:06 hiroshima kernel: RDX: 0000000000000009 RSI: fffffffae154c0df RDI: 0000000000000000
Jul 05 23:10:06 hiroshima kernel: RBP: 0000000000000002 R08: 0000000000000002 R09: 0000000021af286c
Jul 05 23:10:06 hiroshima kernel: R10: 00000000000003d3 R11: 0000000000000008 R12: ffffffffb234b600
Jul 05 23:10:06 hiroshima kernel: R13: 0000000000000002 R14: 000002d799e6c15f R15: 0000000000000000
Jul 05 23:10:06 hiroshima kernel:  cpuidle_enter+0x2d/0x40
Jul 05 23:10:06 hiroshima kernel:  do_idle+0x1d8/0x230
Jul 05 23:10:06 hiroshima kernel:  cpu_startup_entry+0x1d/0x20
Jul 05 23:10:06 hiroshima kernel:  start_secondary+0x12b/0x150
Jul 05 23:10:06 hiroshima kernel:  secondary_startup_64_no_verify+0x10b/0x10b
Jul 05 23:10:06 hiroshima kernel:  </TASK>

These are colored in red:

Jul 05 23:10:06 hiroshima kernel: NMI watchdog: Watchdog detected hard LOCKUP on cpu 10
Jul 05 23:10:06 hiroshima kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 23s! [swapper/9:0]

Note: hiroshima is my system name

I will try to use that tool agapito mentioned.

Last edited by MarbleXeno (2023-07-06 08:05:17)

MarbleXeno · 2023-07-05 21:42:05

I don’t think this is a hardware related issue, I think it has something to do with a regression in AMDs drivers. I see many people with similar issues on Reddit or other forums. The CPU (and my whole PC) worked perfectly for two years, it’s unlikely for a CPU to just get a new issue after that long period of time. Most of these issues come up right after getting it, not after two years.

There’s one thing that worries me tho, I also remember this happened once or twice on Windows (only recently), so this might indicate a hardware issue, but still, it popped randomly after two years of having no issues whatsoever?

Anyways, thanks for your help. I will try to investigate on my own, because this clearly doesn’t have to do with Arch itself and is either an AMD issue or a hardware issue. Thanks

Last edited by MarbleXeno (2023-07-05 21:51:50)

seth · 2023-07-06 05:33:59

Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.

The ongoing amdgpu problems usually present themselves slightly different.

seth wrote:

* Also try the not-zen kernel and the lts one

I also remember this happened once or twice on Windows

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Notably as the errors in the last journal segment you posted have nothing to do w/ GPU, CPU or AMD - they're from your (intel) WiFi chip/driver (which is a common victim of MS faking a fast boot process)

agapito · 2023-07-06 08:38:59

Are u overclocking or undervolting your GPU? Sometimes the system can become unstable when you modify the GPU parameters.

If you are not touching your GPU voltage settings I am pretty sure your CPU degraded and Core 3 needs more voltage to work properly. As i said, you should use CoreCycler for hours to be sure is not a hardware/voltage problem.

https://bugzilla.kernel.org/show_bug.cgi?id=206903
If you look at the comments of this bug report you can read my two hypotheses about this issue.

Last edited by agapito (2024-05-31 06:25:08)

MarbleXeno · 2023-07-06 08:39:23

Are u overclocking or undervolting your GPU? Sometimes the system can become unstable when you modify the GPU parameters.

Nothing on my system is overclocked or underclocked. I used CoreCycler for a long period of time, checked the logs and found no errors/issues. The system didn't crash.

I am pretty sure your CPU degraded and Core 4 needs more voltage to work properly.

What makes you think this is Core 4 specifically?

Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

I'm not dual booting. I have two disks I swap when I need something from Windows or Linux.

One thing to note, I got a PCI WiFI & Bluetooth card not a long time ago, I don't know if this has anything to do with it, it's Fenvi AC-1200

Last edited by MarbleXeno (2023-07-06 11:13:23)

agapito · 2023-07-06 11:25:37

MarbleXeno wrote:

What makes you think this is Core 4 specifically?

MarbleXeno wrote:

Jul 04 14:08:09 archlinux kernel: mce: [Hardware Error]: CPU 9: Machine Check: 0 Bank 5: bea0000000000108

MarbleXeno wrote:

Jul 05 23:10:06 hiroshima kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 23s! [swapper/9:0]

CPU 9 is Core 3 on 6-core processors.

Last edited by agapito (2024-05-31 06:24:48)

MarbleXeno · 2023-07-06 11:55:25

Disabling C-States increased the CPU power usage when idle, which sucks. Rn I have Power Supply Idle Control set to Typical Power and didn't observe any freezes (that last freeze happened with it set to Auto), but I guess it has nothing to do with the issue, right?

Too bad... If I see any other crashes I guess I will just do what agapito says.

Last edited by MarbleXeno (2023-07-06 12:12:17)

seth · 2023-07-06 13:41:43

I'm not dual booting. I have two disks I swap when I need something from Windows or Linux.

That /is/ dual booting. The problem isn't related to your harddrive but the BIOS/UEFI. The 3rd link below is *VERY* relevant to the iwlwifi situation.

MarbleXeno · 2023-07-06 15:01:23

That /is/ dual booting. The problem isn't related to your harddrive but the BIOS/UEFI. The 3rd link below is *VERY* relevant to the iwlwifi situation.

How is this dual booting? I already had Fast Boot disabled. Also, the freezing was happening when I just had Linux or Windows installed, so I don't think this has anything to do with it.

But, do you think this might be because of the PCI card and no the CPU?

Last edited by MarbleXeno (2023-07-06 15:12:09)

MarbleXeno · 2023-07-06 15:03:00

agapito wrote:

MarbleXeno wrote:
What makes you think this is Core 4 specifically?
MarbleXeno wrote:
Jul 04 14:08:09 archlinux kernel: mce: [Hardware Error]: CPU 9: Machine Check: 0 Bank 5: bea0000000000108
MarbleXeno wrote:
Jul 05 23:10:06 hiroshima kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 23s! [swapper/9:0]
CPU 9 is Core 4.

Yeah, but there was also this error:

Jul 05 23:10:06 hiroshima kernel: NMI watchdog: Watchdog detected hard LOCKUP on cpu 10

seth · 2023-07-06 15:06:21

Windows fast start is NOT the "fast boot" feature of your UEFI and you want to double and triple check this because windows re-enables it with updates.
I don't necessarily think the wifi card is the cause for your original freezes, but it's almost certainly the cause for the snippet you posted in #11

MarbleXeno · 2023-07-06 15:17:11

seth wrote:

Windows fast start is NOT the "fast boot" feature of your UEFI and you want to double and triple check this because windows re-enables it with updates.
I don't necessarily think the wifi card is the cause for your original freezes, but it's almost certainly the cause for the snippet you posted in #11

I know this and I assure you that Windows didn't affect Linux in any way, so this dual booting thing has nothing to do with it.

Anyways... I really think this is the PCI card. It's really unlikely there are two freezing issues going on on my PC. It's super unlikely the first one was caused by the CPU and the second by the PCI. The freezing started happening after I got the card, which was quite recently. Before, I used my PC for two years without problems in Linux and Windows. If the second one was caused by the card it's very much possible the first one also got caused by it. Isn't that right? Also I tested the shit out of the CPU. Tried benchmarking it, stress testing, running the CoreCycler script and nothing happened.

seth · 2023-07-06 15:20:02

That's easy enough to test: remove the card, undo everything else, see whether the system is stable again.

MarbleXeno · 2023-07-06 16:32:08

Removed the card. Will report if any other freezes happen.

agapito · 2023-07-06 19:24:19

MarbleXeno wrote:

agapito wrote:
MarbleXeno wrote:
What makes you think this is Core 4 specifically?
MarbleXeno wrote:
Jul 04 14:08:09 archlinux kernel: mce: [Hardware Error]: CPU 9: Machine Check: 0 Bank 5: bea0000000000108
MarbleXeno wrote:
Jul 05 23:10:06 hiroshima kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 23s! [swapper/9:0]
CPU 9 is Core 4.
Yeah, but there was also this error:
Jul 05 23:10:06 hiroshima kernel: NMI watchdog: Watchdog detected hard LOCKUP on cpu 10

Maybe Core 4 is also failing or as I told you before, and it is something I have experienced myself, manipulating the GPU voltage and frequency values can leave the system unstable and when rebooting you get those kind of messages.

And although you said that you have not touched the GPU settings. the problem may be caused by the GPU and the CPU only shows the symptoms.

Last edited by agapito (2024-05-31 06:25:54)

Arch Linux

#1 2023-07-04 14:28:37

[SOLVED] AMD system hangs at idling/light tasks

#2 2023-07-04 14:31:17

Re: [SOLVED] AMD system hangs at idling/light tasks

#3 2023-07-04 16:00:14

Re: [SOLVED] AMD system hangs at idling/light tasks

#4 2023-07-04 18:31:18

Re: [SOLVED] AMD system hangs at idling/light tasks

#5 2023-07-04 20:03:56

Re: [SOLVED] AMD system hangs at idling/light tasks

#6 2023-07-04 21:24:51

Re: [SOLVED] AMD system hangs at idling/light tasks

#7 2023-07-04 21:30:53

Re: [SOLVED] AMD system hangs at idling/light tasks

#8 2023-07-05 08:08:30

Re: [SOLVED] AMD system hangs at idling/light tasks

#9 2023-07-05 10:14:19

Re: [SOLVED] AMD system hangs at idling/light tasks

#10 2023-07-05 10:48:02

Re: [SOLVED] AMD system hangs at idling/light tasks

#11 2023-07-05 21:22:00

Re: [SOLVED] AMD system hangs at idling/light tasks

#12 2023-07-05 21:42:05

Re: [SOLVED] AMD system hangs at idling/light tasks

#13 2023-07-06 05:33:59

Re: [SOLVED] AMD system hangs at idling/light tasks

#14 2023-07-06 08:38:59

Re: [SOLVED] AMD system hangs at idling/light tasks

#15 2023-07-06 08:39:23

Re: [SOLVED] AMD system hangs at idling/light tasks

#16 2023-07-06 11:25:37

Re: [SOLVED] AMD system hangs at idling/light tasks

#17 2023-07-06 11:55:25

Re: [SOLVED] AMD system hangs at idling/light tasks

#18 2023-07-06 13:41:43

Re: [SOLVED] AMD system hangs at idling/light tasks

#19 2023-07-06 15:01:23

Re: [SOLVED] AMD system hangs at idling/light tasks

#20 2023-07-06 15:03:00

Re: [SOLVED] AMD system hangs at idling/light tasks

#21 2023-07-06 15:06:21

Re: [SOLVED] AMD system hangs at idling/light tasks

#22 2023-07-06 15:17:11

Re: [SOLVED] AMD system hangs at idling/light tasks

#23 2023-07-06 15:20:02

Re: [SOLVED] AMD system hangs at idling/light tasks

#24 2023-07-06 16:32:08

Re: [SOLVED] AMD system hangs at idling/light tasks

#25 2023-07-06 19:24:19

Re: [SOLVED] AMD system hangs at idling/light tasks

Board footer