Arch Linux

DeKay

Member

Registered: 2008-11-15

Posts: 14

System soft lockups with Ryzen 1700, X370 Taichi, and KDE

Hi

I'm having several problems with stability.  This is my setup.
- Ryzen 1700 that has was RMA'ed and replaced after original CPU exhibited the segfault bug
- Asrock X370 Taichi with latest 3.2 BIOS
- Asrock ROG-Strix AMD 560 graphics with open source drivers
- Seasonic Gold 750W power supply
- Team Dark Pro 8Gig x 2 memory, 3200 CL14 Samsung B Die running at 3200 MHz
- Vcore and SOC Voltages bumped in BIOS, thinking maybe those were marginal
- No CPU overclock
- C6 State disabled in BIOS

I got this lockup today and have had similar ones infrequently in the past (every few days maybe).  I have been doing one thing after another to try and get rid of these (bumping BIOS voltages, disabling C6 state).  I had also seen a couple lockups where the last thing I saw in the log was Powerdevil sending a message to inhibit suspend to ck_kit when about to play a Youtube video, so I disabled that in Powerdevil as well.  The hang below happened under a light load while browsing the web and no video playing.  I'm running out of things to try.  Looking at the output below, I don't know enough to blame pulseaudio or plasma or if these are just a couple random processes hit by a wider issue.

Jan 01 07:38:36 ryzen NetworkManager[521]: <info>  [1514813916.0453] manager: NetworkManager state is now CONNECTED_GLOBAL
Jan 01 07:38:36 ryzen nm-dispatcher[6319]: req:2 'connectivity-change': new request (0 scripts)
Jan 01 07:38:36 ryzen nm-dispatcher[6319]: req:2 'connectivity-change': completed: no scripts
Jan 01 07:45:18 ryzen rtkit-daemon[602]: The canary thread is apparently starving. Taking action.
Jan 01 07:45:18 ryzen rtkit-daemon[602]: Demoting known real-time threads.
Jan 01 07:45:18 ryzen rtkit-daemon[602]: Successfully demoted thread 649 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:45:18 ryzen rtkit-daemon[602]: Successfully demoted thread 600 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:45:18 ryzen rtkit-daemon[602]: Demoted 2 threads.
Jan 01 07:45:28 ryzen rtkit-daemon[602]: The canary thread is apparently starving. Taking action.
Jan 01 07:45:28 ryzen rtkit-daemon[602]: Demoting known real-time threads.
Jan 01 07:45:28 ryzen rtkit-daemon[602]: Successfully demoted thread 649 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:45:28 ryzen rtkit-daemon[602]: Successfully demoted thread 600 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:45:28 ryzen rtkit-daemon[602]: Demoted 2 threads.
Jan 01 07:45:38 ryzen rtkit-daemon[602]: The canary thread is apparently starving. Taking action.
Jan 01 07:45:38 ryzen rtkit-daemon[602]: Demoting known real-time threads.
Jan 01 07:45:38 ryzen rtkit-daemon[602]: Successfully demoted thread 649 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:45:38 ryzen rtkit-daemon[602]: Successfully demoted thread 600 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:45:38 ryzen rtkit-daemon[602]: Demoted 2 threads.
Jan 01 07:45:43 ryzen kernel: watchdog: BUG: soft lockup - CPU#14 stuck for 23s! [plasmashell:774]
Jan 01 07:45:43 ryzen kernel: Modules linked in: nls_iso8859_1 nls_cp437 vfat fat edac_mce_amd kvm_amd kvm amdkfd amd_iommu_v2 arc4 amdgpu iwlmvm mac80211 irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek ghash_clmulni_intel snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec ttm btusb pcbc snd_hda_core aesni_intel btrtl drm_kms_helper snd_hwdep aes_x86_64 btbcm igb crypto_simd btintel ptp snd_pcm drm agpgart snd_timer mousedev pps_core joydev input_leds led_class bluetooth snd iwlwifi syscopyarea i2c_algo_bit cfg80211 glue_helper sysfillrect cryptd dca ecdh_generic evdev sysimgblt rfkill wmi_bmof mxm_wmi fb_sys_fops ccp soundcore rng_core mac_hid sp5100_tco shpchp i2c_piix4 pcspkr wmi tpm_tis acpi_cpufreq tpm_tis_core tpm button 8250_dw sch_fq_codel virtio crypto_user ip_tables x_tables
Jan 01 07:45:43 ryzen kernel:  ext4 crc16 mbcache jbd2 fscrypto sd_mod hid_generic usbhid hid crc32c_intel ahci xhci_pci libahci xhci_hcd libata usbcore scsi_mod usb_common serio
Jan 01 07:45:43 ryzen kernel: CPU: 14 PID: 774 Comm: plasmashell Tainted: G        W       4.14.4-1-ARCH #1
Jan 01 07:45:43 ryzen kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X370 Taichi, BIOS P3.20 09/08/2017
Jan 01 07:45:43 ryzen kernel: task: ffff928a3b568ec0 task.stack: ffff9db7895a4000
Jan 01 07:45:43 ryzen kernel: RIP: 0010:smp_call_function_many+0x20d/0x230
Jan 01 07:45:43 ryzen kernel: RSP: 0018:ffff9db7895a7d60 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff10
Jan 01 07:45:43 ryzen kernel: RAX: 0000000000000006 RBX: ffff928a5ef99e18 RCX: 0000000000000001
Jan 01 07:45:43 ryzen kernel: RDX: ffff928a5ed9da80 RSI: 0000000000000000 RDI: ffff928a5ef99e08
Jan 01 07:45:43 ryzen kernel: RBP: ffff928a5ef99e08 R08: ffffffffffffffff R09: 0000000000000140
Jan 01 07:45:43 ryzen kernel: R10: ffff9db7895a7d60 R11: 0000000000000002 R12: ffff928a5ef99e00
Jan 01 07:45:43 ryzen kernel: R13: 0000000000000080 R14: ffffffff9506fb90 R15: ffff9db7895a7da0
Jan 01 07:45:43 ryzen kernel: FS:  00007f46d8d5c800(0000) GS:ffff928a5ef80000(0000) knlGS:0000000000000000
Jan 01 07:45:43 ryzen kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 01 07:45:43 ryzen kernel: CR2: 00007f46bc01dd70 CR3: 00000003fa9cf000 CR4: 00000000003406e0
Jan 01 07:45:43 ryzen kernel: Call Trace:
Jan 01 07:45:43 ryzen kernel:  flush_tlb_mm_range+0xb3/0x120
Jan 01 07:45:43 ryzen kernel:  copy_process.part.42+0x10d9/0x1a90
Jan 01 07:45:43 ryzen kernel:  _do_fork+0xcc/0x3b0
Jan 01 07:45:43 ryzen kernel:  do_syscall_64+0x55/0x110
Jan 01 07:45:43 ryzen kernel:  entry_SYSCALL64_slow_path+0x25/0x25
Jan 01 07:45:43 ryzen kernel: RIP: 0033:0x7f46d22b8285
Jan 01 07:45:43 ryzen kernel: RSP: 002b:00007ffd1a31b7c0 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
Jan 01 07:45:43 ryzen kernel: RAX: ffffffffffffffda RBX: 00007ffd1a31b7c0 RCX: 00007f46d22b8285
Jan 01 07:45:43 ryzen kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
Jan 01 07:45:43 ryzen kernel: RBP: 00007ffd1a31b840 R08: 00007f46d8d5c800 R09: 0000000000000000
Jan 01 07:45:43 ryzen kernel: R10: 00007f46d8d5cad0 R11: 0000000000000246 R12: 0000000000000000
Jan 01 07:45:43 ryzen kernel: R13: 0000000000000020 R14: 0000000000000001 R15: 00007ffd1a31b7e0
Jan 01 07:45:43 ryzen kernel: Code: ee 89 c7 e8 b6 ed 53 00 3b 05 94 d1 c0 00 0f 83 76 fe ff ff 48 63 c8 49 8b 14 24 48 03 14 cd c0 53 9b 95 8b 4a 18 83 e1 01 74 0a <f3> 90 8b 4a 18 83 e1 01 75 f6 eb c7 48 c7 c2 70 33 d1 95 48 89 
Jan 01 07:45:48 ryzen rtkit-daemon[602]: The canary thread is apparently starving. Taking action.
Jan 01 07:45:48 ryzen rtkit-daemon[602]: Demoting known real-time threads.
Jan 01 07:45:48 ryzen rtkit-daemon[602]: Successfully demoted thread 649 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:45:48 ryzen rtkit-daemon[602]: Successfully demoted thread 600 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:45:48 ryzen rtkit-daemon[602]: Demoted 2 threads.
Jan 01 07:45:58 ryzen rtkit-daemon[602]: The canary thread is apparently starving. Taking action.
Jan 01 07:45:58 ryzen rtkit-daemon[602]: Demoting known real-time threads.
Jan 01 07:45:58 ryzen rtkit-daemon[602]: Successfully demoted thread 649 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:45:58 ryzen rtkit-daemon[602]: Successfully demoted thread 600 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:45:58 ryzen rtkit-daemon[602]: Demoted 2 threads.
Jan 01 07:46:08 ryzen rtkit-daemon[602]: The canary thread is apparently starving. Taking action.
Jan 01 07:46:08 ryzen rtkit-daemon[602]: Demoting known real-time threads.
Jan 01 07:46:08 ryzen rtkit-daemon[602]: Successfully demoted thread 649 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:46:08 ryzen rtkit-daemon[602]: Successfully demoted thread 600 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:46:08 ryzen rtkit-daemon[602]: Demoted 2 threads.
Jan 01 07:46:11 ryzen kernel: watchdog: BUG: soft lockup - CPU#14 stuck for 23s! [plasmashell:774]
Jan 01 07:46:11 ryzen kernel: Modules linked in: nls_iso8859_1 nls_cp437 vfat fat edac_mce_amd kvm_amd kvm amdkfd amd_iommu_v2 arc4 amdgpu iwlmvm mac80211 irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek ghash_clmulni_intel snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec ttm btusb pcbc snd_hda_core aesni_intel btrtl drm_kms_helper snd_hwdep aes_x86_64 btbcm igb crypto_simd btintel ptp snd_pcm drm agpgart snd_timer mousedev pps_core joydev input_leds led_class bluetooth snd iwlwifi syscopyarea i2c_algo_bit cfg80211 glue_helper sysfillrect cryptd dca ecdh_generic evdev sysimgblt rfkill wmi_bmof mxm_wmi fb_sys_fops ccp soundcore rng_core mac_hid sp5100_tco shpchp i2c_piix4 pcspkr wmi tpm_tis acpi_cpufreq tpm_tis_core tpm button 8250_dw sch_fq_codel virtio crypto_user ip_tables x_tables
Jan 01 07:46:11 ryzen kernel:  ext4 crc16 mbcache jbd2 fscrypto sd_mod hid_generic usbhid hid crc32c_intel ahci xhci_pci libahci xhci_hcd libata usbcore scsi_mod usb_common serio
Jan 01 07:46:11 ryzen kernel: CPU: 14 PID: 774 Comm: plasmashell Tainted: G        W    L  4.14.4-1-ARCH #1
Jan 01 07:46:11 ryzen kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X370 Taichi, BIOS P3.20 09/08/2017
Jan 01 07:46:11 ryzen kernel: task: ffff928a3b568ec0 task.stack: ffff9db7895a4000
Jan 01 07:46:11 ryzen kernel: RIP: 0010:smp_call_function_many+0x212/0x230
Jan 01 07:46:11 ryzen kernel: RSP: 0018:ffff9db7895a7d60 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff10
Jan 01 07:46:11 ryzen kernel: RAX: 0000000000000006 RBX: ffff928a5ef99e18 RCX: 0000000000000003
Jan 01 07:46:11 ryzen kernel: RDX: ffff928a5ed9da80 RSI: 0000000000000000 RDI: ffff928a5ef99e08
Jan 01 07:46:11 ryzen kernel: RBP: ffff928a5ef99e08 R08: ffffffffffffffff R09: 0000000000000140
Jan 01 07:46:11 ryzen kernel: R10: ffff9db7895a7d60 R11: 0000000000000002 R12: ffff928a5ef99e00
Jan 01 07:46:11 ryzen kernel: R13: 0000000000000080 R14: ffffffff9506fb90 R15: ffff9db7895a7da0
Jan 01 07:46:11 ryzen kernel: FS:  00007f46d8d5c800(0000) GS:ffff928a5ef80000(0000) knlGS:0000000000000000
Jan 01 07:46:11 ryzen kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 01 07:46:11 ryzen kernel: CR2: 00007f46bc01dd70 CR3: 00000003fa9cf000 CR4: 00000000003406e0
Jan 01 07:46:11 ryzen kernel: Call Trace:
Jan 01 07:46:11 ryzen kernel:  flush_tlb_mm_range+0xb3/0x120
Jan 01 07:46:11 ryzen kernel:  copy_process.part.42+0x10d9/0x1a90
Jan 01 07:46:11 ryzen kernel:  _do_fork+0xcc/0x3b0
Jan 01 07:46:11 ryzen kernel:  do_syscall_64+0x55/0x110
Jan 01 07:46:11 ryzen kernel:  entry_SYSCALL64_slow_path+0x25/0x25
Jan 01 07:46:11 ryzen kernel: RIP: 0033:0x7f46d22b8285
Jan 01 07:46:11 ryzen kernel: RSP: 002b:00007ffd1a31b7c0 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
Jan 01 07:46:11 ryzen kernel: RAX: ffffffffffffffda RBX: 00007ffd1a31b7c0 RCX: 00007f46d22b8285
Jan 01 07:46:11 ryzen kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
Jan 01 07:46:11 ryzen kernel: RBP: 00007ffd1a31b840 R08: 00007f46d8d5c800 R09: 0000000000000000
Jan 01 07:46:11 ryzen kernel: R10: 00007f46d8d5cad0 R11: 0000000000000246 R12: 0000000000000000
Jan 01 07:46:11 ryzen kernel: R13: 0000000000000020 R14: 0000000000000001 R15: 00007ffd1a31b7e0
Jan 01 07:46:11 ryzen kernel: Code: ed 53 00 3b 05 94 d1 c0 00 0f 83 76 fe ff ff 48 63 c8 49 8b 14 24 48 03 14 cd c0 53 9b 95 8b 4a 18 83 e1 01 74 0a f3 90 8b 4a 18 <83> e1 01 75 f6 eb c7 48 c7 c2 70 33 d1 95 48 89 de 89 c7 e8 96 
Jan 01 07:46:18 ryzen rtkit-daemon[602]: The canary thread is apparently starving. Taking action.
Jan 01 07:46:18 ryzen rtkit-daemon[602]: Demoting known real-time threads.
Jan 01 07:46:18 ryzen rtkit-daemon[602]: Successfully demoted thread 649 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:46:18 ryzen rtkit-daemon[602]: Successfully demoted thread 600 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:46:18 ryzen rtkit-daemon[602]: Demoted 2 threads.
Jan 01 07:46:28 ryzen rtkit-daemon[602]: The canary thread is apparently starving. Taking action.
Jan 01 07:46:28 ryzen rtkit-daemon[602]: Demoting known real-time threads.
Jan 01 07:46:28 ryzen rtkit-daemon[602]: Successfully demoted thread 649 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:46:28 ryzen rtkit-daemon[602]: Successfully demoted thread 600 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:46:28 ryzen rtkit-daemon[602]: Demoted 2 threads.
Jan 01 07:46:38 ryzen rtkit-daemon[602]: The canary thread is apparently starving. Taking action.
Jan 01 07:46:38 ryzen rtkit-daemon[602]: Demoting known real-time threads.
Jan 01 07:46:38 ryzen rtkit-daemon[602]: Successfully demoted thread 649 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:46:38 ryzen rtkit-daemon[602]: Successfully demoted thread 600 of process 600 (/usr/bin/pulseaudio).
Jan 01 07:46:38 ryzen rtkit-daemon[602]: Demoted 2 threads.
Jan 01 07:46:39 ryzen kernel: watchdog: BUG: soft lockup - CPU#14 stuck for 23s! [plasmashell:774]
-- Reboot --
Jan 01 07:47:39 ryzen kernel: Linux version 4.14.4-1-ARCH (builduser@heftig) (gcc version 7.2.1 20171128 (GCC)) #1 SMP PREEMPT Tue Dec 5 19:10:06 UTC 2017
Jan 01 07:47:39 ryzen kernel: Command line: root=/dev/sda5 rw initrd=/initramfs-linux.img
Jan 01 07:47:39 ryzen kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jan 01 07:47:39 ryzen kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jan 01 07:47:39 ryzen kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jan 01 07:47:39 ryzen kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jan 01 07:47:39 ryzen kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Jan 01 07:47:39 ryzen kernel: e820: BIOS-provided physical RAM map:

I have also suffered lockups like the one below that I suspect is this bug.  I disabled C6 State in the BIOS for this reason and haven't seen it since, but this happened only occassionally so don't know yet for sure.

-- Logs begin at Sat 2017-10-28 11:12:18 CST, end at Thu 2017-12-21 21:03:33 CST. --
Dec 21 20:41:16 ryzen systemd-timesyncd[523]: Synchronized to time server 144.217.240.204:123 (0.arch.pool.ntp.org).
Dec 21 20:41:16 ryzen plasmashell[788]: Time engine Clock skew signaled
-- Reboot --
Dec 21 21:02:09 ryzen kernel: Linux version 4.14.4-1-ARCH (builduser@heftig) (gcc version 7.2.1 20171128 (GCC)) #1 SMP PREEMPT Tue Dec 5 19:10:06 UTC 2017
Dec 21 21:02:09 ryzen kernel: Command line: root=/dev/sda5 rw initrd=/initramfs-linux.img
Dec 21 21:02:09 ryzen kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Dec 21 21:02:09 ryzen kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Dec 21 21:02:09 ryzen kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'

Any suggestions for the first lockup problem, assuming disabling C6 has solved the second?

EDIT: Forgot to mention that this PC dual boots Windows 10 and I've never had a problem in that OS.

Last edited by DeKay (2018-01-01 16:40:16)

DeKay

Member

Registered: 2008-11-15

Posts: 14

Re: System soft lockups with Ryzen 1700, X370 Taichi, and KDE

According to the link I posted earlier, it seems that some BIOSes enable C6 states even when told to disable it.  Weird.  That thread points to this python script that lets you disable C6 States from the command line.

[root@ryzen ZenStates-Linux]# modprobe msr
[root@ryzen ZenStates-Linux]# ./zenstates.py --list
P0 - Enabled - FID = 78 - DID = 8 - VID = 3A - Ratio = 30.00 - vCore = 1.18750
P1 - Enabled - FID = 87 - DID = A - VID = 50 - Ratio = 27.00 - vCore = 1.05000
P2 - Enabled - FID = 7C - DID = 10 - VID = 6C - Ratio = 15.50 - vCore = 0.87500
P3 - Disabled
P4 - Disabled
P5 - Disabled
P6 - Disabled
P7 - Disabled
C6 State - Package - Enabled
C6 State - Core - Enabled
[root@ryzen ZenStates-Linux]# ./zenstates.py --c6-disable
Disabling C6 state
[root@ryzen ZenStates-Linux]# ./zenstates.py --list
P0 - Enabled - FID = 78 - DID = 8 - VID = 3A - Ratio = 30.00 - vCore = 1.18750
P1 - Enabled - FID = 87 - DID = A - VID = 50 - Ratio = 27.00 - vCore = 1.05000
P2 - Enabled - FID = 7C - DID = 10 - VID = 6C - Ratio = 15.50 - vCore = 0.87500
P3 - Disabled
P4 - Disabled
P5 - Disabled
P6 - Disabled
P7 - Disabled
C6 State - Package - Disabled
C6 State - Core - Disabled

I'm going to run like this for a while and see if it helps.

circleface

Member

Registered: 2012-05-26

Posts: 639

Re: System soft lockups with Ryzen 1700, X370 Taichi, and KDE

Make sure your system is up to date since you are not running the latest kernel.  I know you said your power supply is good, but what about the power going to that supply (like house wiring).

Morn

Member

Registered: 2012-09-02

Posts: 886

Re: System soft lockups with Ryzen 1700, X370 Taichi, and KDE

According to the link I posted earlier, it seems that some BIOSes enable C6 states even when told to disable it.  Weird.  That thread points to this python script that lets you disable C6 States from the command line.

Normally you would simply use the kernel boot parameter processor.max_cstate=5 to disable that C-state (https://wiki.gentoo.org/wiki/Ryzen). Linux has a habit of ignoring BIOS settings in general.

Gigamo

Member

Registered: 2008-01-19

Posts: 394

Re: System soft lockups with Ryzen 1700, X370 Taichi, and KDE

Just chiming in here to say I experienced the exact same type of lockups, and I have the same motherboard (but with an 1700X CPU). For me, disabling "Global C-State Control" in the BIOS did actually fix the issue though... Using 3.00 BIOS instead of 3.20 as I haven't updated that yet, FWIW.