I noticed an error in syslog below. Is there a way to fix this, or is it safe to ignore it?

 

Nov 14 15:23:11 Zoidberg kernel: WARNING: CPU: 16 PID: 1419 at drivers/gpu/drm/drm_probe_helper.c:838 drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper]
Nov 14 15:23:11 Zoidberg kernel: Modules linked in: cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net tun vhost vhost_iotlb tap xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc e1000e r8169 realtek amdgpu edac_mce_amd edac_core intel_rapl_msr intel_rapl_common iosf_mbi gpu_sched drm_buddy video i2c_algo_bit drm_ttm_helper ttm kvm_amd drm_display_helper drm_kms_helper kvm drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 backlight aesni_intel agpgart crypto_simd cryptd wmi_bmof rapl i2c_piix4 syscopyarea nvme ahci sysfillrect i2c_core
Nov 14 15:23:11 Zoidberg kernel: k10temp ccp sysimgblt libahci fb_sys_fops nvme_core wmi tpm_crb tpm_tis tpm_tis_core tpm button acpi_cpufreq unix [last unloaded: e1000e]
Nov 14 15:23:11 Zoidberg kernel: CPU: 16 PID: 1419 Comm: kworker/16:2 Tainted: P        W  O       6.1.106-Unraid #1
Nov 14 15:23:11 Zoidberg kernel: Hardware name: System manufacturer System Product Name/PRIME X570-P, BIOS 5013 03/22/2024
Nov 14 15:23:11 Zoidberg kernel: Workqueue: pm pm_runtime_work
Nov 14 15:23:11 Zoidberg kernel: RIP: 0010:drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper]
Nov 14 15:23:11 Zoidberg kernel: Code: 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 ad 5f cc df 48 c7 c1 ef c6 8e a1 48 89 da 48 c7 c7 1d c6 8e a1 48 89 c6 e8 e0 88 79 df <0f> 0b 5b e9 40 9e 32 e0 0f 1f 44 00 00 41 55 41 54 55 53 48 8b 2f
Nov 14 15:23:11 Zoidberg kernel: RSP: 0018:ffffc90000cf7d48 EFLAGS: 00010282
Nov 14 15:23:11 Zoidberg kernel: RAX: 0000000000000000 RBX: ffff88810176e180 RCX: 0000000000000027
Nov 14 15:23:11 Zoidberg kernel: RDX: 0000000000000002 RSI: ffffffff820d99e1 RDI: 00000000ffffffff
Nov 14 15:23:11 Zoidberg kernel: RBP: ffff8881074a0000 R08: 0000000000000000 R09: ffffc90000cf7c00
Nov 14 15:23:11 Zoidberg kernel: R10: 00003fffffffffff R11: 000000002d2d2d2d R12: 0000000000000000
Nov 14 15:23:11 Zoidberg kernel: R13: ffffffffa0cb9440 R14: 0000000000000000 R15: 0000000000000000
Nov 14 15:23:11 Zoidberg kernel: FS:  0000000000000000(0000) GS:ffff889faec00000(0000) knlGS:0000000000000000
Nov 14 15:23:11 Zoidberg kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 14 15:23:11 Zoidberg kernel: CR2: ffff9d0129299000 CR3: 00000002270c8000 CR4: 0000000000350ee0
Nov 14 15:23:11 Zoidberg kernel: Call Trace:
Nov 14 15:23:11 Zoidberg kernel: <TASK>
Nov 14 15:23:11 Zoidberg kernel: ? __warn+0xab/0x122
Nov 14 15:23:11 Zoidberg kernel: ? report_bug+0x109/0x17e
Nov 14 15:23:11 Zoidberg kernel: ? drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper]
Nov 14 15:23:11 Zoidberg kernel: ? handle_bug+0x41/0x6f
Nov 14 15:23:11 Zoidberg kernel: ? exc_invalid_op+0x13/0x60
Nov 14 15:23:11 Zoidberg kernel: ? asm_exc_invalid_op+0x16/0x20
Nov 14 15:23:11 Zoidberg kernel: ? drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper]
Nov 14 15:23:11 Zoidberg kernel: ? drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper]
Nov 14 15:23:11 Zoidberg kernel: amdgpu_device_suspend+0x72/0xfd [amdgpu]
Nov 14 15:23:11 Zoidberg kernel: amdgpu_pmops_runtime_suspend+0xbb/0x165 [amdgpu]
Nov 14 15:23:11 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23
Nov 14 15:23:11 Zoidberg kernel: pci_pm_runtime_suspend+0x6d/0x155
Nov 14 15:23:11 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23
Nov 14 15:23:11 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23
Nov 14 15:23:11 Zoidberg kernel: __rpm_callback+0xce/0x13a
Nov 14 15:23:11 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23
Nov 14 15:23:11 Zoidberg kernel: rpm_callback+0x4b/0x64
Nov 14 15:23:11 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23
Nov 14 15:23:11 Zoidberg kernel: rpm_suspend+0x2ae/0x4a8
Nov 14 15:23:11 Zoidberg kernel: ? srso_return_thunk+0x5/0x10
Nov 14 15:23:11 Zoidberg kernel: ? finish_task_switch.isra.0+0x140/0x218
Nov 14 15:23:11 Zoidberg kernel: pm_runtime_work+0x75/0x7f
Nov 14 15:23:11 Zoidberg kernel: process_one_work+0x1ab/0x295
Nov 14 15:23:11 Zoidberg kernel: worker_thread+0x18b/0x244
Nov 14 15:23:11 Zoidberg kernel: ? rescuer_thread+0x281/0x281
Nov 14 15:23:11 Zoidberg kernel: kthread+0xe7/0xef
Nov 14 15:23:11 Zoidberg kernel: ? kthread_complete_and_exit+0x1b/0x1b
Nov 14 15:23:11 Zoidberg kernel: ret_from_fork+0x22/0x30
Nov 14 15:23:11 Zoidberg kernel: </TASK>
Nov 14 15:23:11 Zoidberg kernel: ---[ end trace 0000000000000000 ]---

 

Edited November 14, 20241 yr by harrisonmeister

please post diag file. Call traces are big errors that shouldn't be ignored.

This error traceback in your Unraid server's kernel log is related to a warning triggered in the drm_kms_helper_poll_disable function, specifically in the Direct Rendering Manager (DRM) kernel module. This module handles graphics on systems with GPUs, and it appears this issue involves your AMD GPU (the amdgpu module).

 

Here’s a breakdown of what might be happening:

Source of the Warning:

The warning originates from drm_probe_helper.c:838 in the drm_kms_helper module. This function call appears to be related to a polling mechanism used by the kernel to manage GPU display outputs.

Error Type:

The "WARNING" type means the system detected something unexpected but not necessarily critical; it's more of an alert to potential instability in the GPU management code.

The RIP (instruction pointer) error specifically points to an issue with the drm_kms_helper_poll_disable function, which could be due to race conditions, unexpected states in the GPU module, or driver incompatibility.

Affected Components:

The trace involves several DRM (Direct Rendering Manager) and AMD GPU-related components, indicating the issue likely stems from GPU or display handling.

You also have ZFS and network modules loaded (zfs, vhost_net, etc.), but these modules don't directly relate to the DRM error here.

Potential Cause:

This type of error can occur due to a bug in the GPU driver (amdgpu), especially if the system has recently undergone a kernel update, or if there's a mismatch between the GPU driver and the Unraid version.

Runtime power management (pm_runtime_work) functions in the call trace suggest this may happen when the GPU is put into a low-power state or woken up, possibly during idle time or power-saving operations.

 

?Did you blacklist something?

 

 

in truth this looks like the amd reset bug...

install plugin

 

Then Reboot

Edited November 14, 20241 yr by bmartino1

15 hours ago, bmartino1 said:

please post diag file. Call traces are big errors that shouldn't be ignored.

This error traceback in your Unraid server's kernel log is related to a warning triggered in the drm_kms_helper_poll_disable function, specifically in the Direct Rendering Manager (DRM) kernel module. This module handles graphics on systems with GPUs, and it appears this issue involves your AMD GPU (the amdgpu module).

 

Here’s a breakdown of what might be happening:

Source of the Warning:

The warning originates from drm_probe_helper.c:838 in the drm_kms_helper module. This function call appears to be related to a polling mechanism used by the kernel to manage GPU display outputs.

Error Type:

The "WARNING" type means the system detected something unexpected but not necessarily critical; it's more of an alert to potential instability in the GPU management code.

The RIP (instruction pointer) error specifically points to an issue with the drm_kms_helper_poll_disable function, which could be due to race conditions, unexpected states in the GPU module, or driver incompatibility.

Affected Components:

The trace involves several DRM (Direct Rendering Manager) and AMD GPU-related components, indicating the issue likely stems from GPU or display handling.

You also have ZFS and network modules loaded (zfs, vhost_net, etc.), but these modules don't directly relate to the DRM error here.

Potential Cause:

This type of error can occur due to a bug in the GPU driver (amdgpu), especially if the system has recently undergone a kernel update, or if there's a mismatch between the GPU driver and the Unraid version.

Runtime power management (pm_runtime_work) functions in the call trace suggest this may happen when the GPU is put into a low-power state or woken up, possibly during idle time or power-saving operations.

 

?Did you blacklist something?

 

 

 

Thanks for the detailed answer, and no I didnt blacklist anything. I starting looking at syslog when I had done a reboot and unraid didnt cleanly shutdown to reboot. I powered off the machine manually started it up again and then performed another reboot and it came back up fine but figured it was worth checking.

 

I've attached the diagnostics file in case you have the time to check it out!

zoidberg-diagnostics-20241115-1010.zip

Thank you. reveiwing diag now:

Yes this is the amd reset bug. you may alos need to fix/set time in bios.

Nov 14 15:00:35 Zoidberg ntpd[1594]: ntp-4 is maintained by Network Time Foundation,
Nov 14 15:00:35 Zoidberg ntpd[1594]: Inc. (NTF), a non-profit 501(c)(3) public-benefit
Nov 14 15:00:35 Zoidberg ntpd[1594]: corporation.  Support and training for ntp-4 are
Nov 14 15:00:35 Zoidberg ntpd[1594]: available at https://www.nwtime.org/support
Nov 14 15:00:35 Zoidberg ntpd[1594]: ----------------------------------------------------
Nov 14 15:00:35 Zoidberg ntpd[1594]: DEBUG behavior is enabled - a violation of any
Nov 14 15:00:35 Zoidberg ntpd[1594]: diagnostic assertion will cause ntpd to abort
Nov 14 15:00:35 Zoidberg ntpd[1596]: proto: precision = 0.040 usec (-24)
Nov 14 15:00:35 Zoidberg ntpd[1596]: basedate set to 2023-05-25
Nov 14 15:00:35 Zoidberg ntpd[1596]: gps base set to 2023-05-28 (week 2264)
Nov 14 15:00:35 Zoidberg ntpd[1596]: initial drift restored to 14.882000
Nov 14 15:00:35 Zoidberg ntpd[1596]: Listen normally on 0 lo 127.0.0.1:123
Nov 14 15:00:35 Zoidberg ntpd[1596]: Listening on routing socket on fd #17 for interface updates
Nov 14 15:00:35 Zoidberg ntpd[1596]: kernel reports TIME_ERROR: 0x41: Clock Unsynchroniz

from previous syslog in diag:

Full trace to see what happened where.

Quote

### [PREVIOUS LINE REPEATED 1 TIMES] ###
Nov 14 15:00:35 Zoidberg acpid: starting up with netlink and the input layer
Nov 14 15:00:35 Zoidberg acpid: 1 rule loaded
Nov 14 15:00:35 Zoidberg acpid: waiting for events: event logging is off
Nov 14 15:00:35 Zoidberg crond[1621]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel notice
Nov 14 15:00:35 Zoidberg kernel: ------------[ cut here ]------------
Nov 14 15:00:35 Zoidberg kernel: amdgpu 0000:0a:00.0: drm_WARN_ON(!dev->mode_config.poll_enabled)
Nov 14 15:00:35 Zoidberg kernel: WARNING: CPU: 10 PID: 362 at drivers/gpu/drm/drm_probe_helper.c:838 drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper]
Nov 14 15:00:35 Zoidberg kernel: Modules linked in: efivarfs bridge stp llc e1000e r8169 realtek amdgpu edac_mce_amd edac_core gpu_sched intel_rapl_msr intel_rapl_common drm_buddy iosf_mbi video i2c_algo_bit drm_ttm_helper ttm kvm_amd drm_display_helper drm_kms_helper kvm drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 backlight aesni_intel agpgart i2c_piix4 crypto_simd cryptd wmi_bmof rapl syscopyarea nvme i2c_core ahci sysfillrect ccp sysimgblt k10temp libahci fb_sys_fops nvme_core wmi tpm_crb tpm_tis tpm_tis_core tpm button acpi_cpufreq unix [last unloaded: e1000e]
Nov 14 15:00:35 Zoidberg kernel: CPU: 10 PID: 362 Comm: kworker/10:1 Not tainted 6.1.106-Unraid #1
Nov 14 15:00:35 Zoidberg kernel: Hardware name: System manufacturer System Product Name/PRIME X570-P, BIOS 5013 03/22/2024
Nov 14 15:00:35 Zoidberg kernel: Workqueue: pm pm_runtime_work
Nov 14 15:00:35 Zoidberg kernel: RIP: 0010:drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper]
Nov 14 15:00:35 Zoidberg kernel: Code: 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 ad ef 0a e1 48 c7 c1 ef 36 50 a0 48 89 da 48 c7 c7 1d 36 50 a0 48 89 c6 e8 e0 18 b8 e0 <0f> 0b 5b e9 40 2e 71 e1 0f 1f 44 00 00 41 55 41 54 55 53 48 8b 2f
Nov 14 15:00:35 Zoidberg kernel: RSP: 0018:ffffc90005157d48 EFLAGS: 00010282
Nov 14 15:00:35 Zoidberg kernel: RAX: 0000000000000000 RBX: ffff88810176e180 RCX: 0000000000000027
Nov 14 15:00:35 Zoidberg kernel: RDX: 0000000000000002 RSI: ffffffff820d99e1 RDI: 00000000ffffffff
Nov 14 15:00:35 Zoidberg kernel: RBP: ffff888101000000 R08: 0000000000000000 R09: ffffc90005157c00
Nov 14 15:00:35 Zoidberg kernel: R10: 00003fffffffffff R11: 000000002d2d2d2d R12: 0000000000000000
Nov 14 15:00:35 Zoidberg kernel: R13: ffffffffa0b61440 R14: 0000000000000000 R15: 0000000000000000
Nov 14 15:00:35 Zoidberg kernel: FS:  0000000000000000(0000) GS:ffff889faea80000(0000) knlGS:0000000000000000
Nov 14 15:00:35 Zoidberg kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 14 15:00:35 Zoidberg kernel: CR2: 00007ffc33497668 CR3: 000000000520a000 CR4: 0000000000350ee0
Nov 14 15:00:35 Zoidberg kernel: Call Trace:
Nov 14 15:00:35 Zoidberg kernel: <TASK>
Nov 14 15:00:35 Zoidberg kernel: ? __warn+0xab/0x122
Nov 14 15:00:35 Zoidberg kernel: ? report_bug+0x109/0x17e
Nov 14 15:00:35 Zoidberg kernel: ? drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper]
Nov 14 15:00:35 Zoidberg kernel: ? handle_bug+0x41/0x6f
Nov 14 15:00:35 Zoidberg kernel: ? exc_invalid_op+0x13/0x60
Nov 14 15:00:35 Zoidberg kernel: ? asm_exc_invalid_op+0x16/0x20
Nov 14 15:00:35 Zoidberg kernel: ? drm_kms_helper_poll_disable+0x49/0x51 [drm_kms_helper]
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Nov 14 15:00:35 Zoidberg kernel: amdgpu_device_suspend+0x72/0xfd [amdgpu]
Nov 14 15:00:35 Zoidberg kernel: amdgpu_pmops_runtime_suspend+0xbb/0x165 [amdgpu]
Nov 14 15:00:35 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23
Nov 14 15:00:35 Zoidberg kernel: pci_pm_runtime_suspend+0x6d/0x155
Nov 14 15:00:35 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Nov 14 15:00:35 Zoidberg kernel: __rpm_callback+0xce/0x13a
Nov 14 15:00:35 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23
Nov 14 15:00:35 Zoidberg kernel: rpm_callback+0x4b/0x64
Nov 14 15:00:35 Zoidberg kernel: ? pci_pm_default_resume+0x23/0x23
Nov 14 15:00:35 Zoidberg kernel: rpm_suspend+0x2ae/0x4a8
Nov 14 15:00:35 Zoidberg kernel: ? srso_return_thunk+0x5/0x10
Nov 14 15:00:35 Zoidberg kernel: ? finish_task_switch.isra.0+0x140/0x218
Nov 14 15:00:35 Zoidberg kernel: pm_runtime_work+0x75/0x7f
Nov 14 15:00:35 Zoidberg kernel: process_one_work+0x1ab/0x295
Nov 14 15:00:35 Zoidberg kernel: worker_thread+0x18b/0x244
Nov 14 15:00:35 Zoidberg kernel: ? rescuer_thread+0x281/0x281
Nov 14 15:00:35 Zoidberg kernel: kthread+0xe7/0xef
Nov 14 15:00:35 Zoidberg kernel: ? kthread_complete_and_exit+0x1b/0x1b
Nov 14 15:00:35 Zoidberg kernel: ret_from_fork+0x22/0x30
Nov 14 15:00:35 Zoidberg kernel: </TASK>
Nov 14 15:00:35 Zoidberg kernel: ---[ end trace 0000000000000000 ]---
 

 

Quote

Nov 14 15:02:14 Zoidberg kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400000000).
Nov 14 15:02:15 Zoidberg kernel: [drm] UVD and UVD ENC initialized successfully.
Nov 14 15:02:15 Zoidberg kernel: [drm] VCE initialized successfully.
Nov 14 15:02:15 Zoidberg kernel: ------------[ cut here ]------------
Nov 14 15:02:15 Zoidberg kernel: amdgpu 0000:0a:00.0: drm_WARN_ON_ONCE(!dev->mode_config.poll_enabled)
Nov 14 15:02:15 Zoidberg kernel: WARNING: CPU: 11 PID: 11738 at drivers/gpu/drm/drm_probe_helper.c:252 drm_kms_helper_poll_enable+0x6b/0x105 [drm_kms_helper]
Nov 14 15:02:15 Zoidberg kernel: Modules linked in: cmac cifs asn1_decoder cifs_arc4 cifs_md4 dns_resolver xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 vhost_net tun vhost vhost_iotlb tap xfs nfsd auth_rpcgss oid_registry lockd grace sunrpc md_mod zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) tcp_diag inet_diag nct6775 nct6775_core hwmon_vid ip6table_filter ip6_tables iptable_filter ip_tables x_tables efivarfs bridge stp llc e1000e r8169 realtek amdgpu edac_mce_amd edac_core gpu_sched intel_rapl_msr intel_rapl_common drm_buddy iosf_mbi video i2c_algo_bit drm_ttm_helper ttm kvm_amd drm_display_helper drm_kms_helper kvm drm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha256_ssse3 sha1_ssse3 backlight aesni_intel agpgart i2c_piix4 crypto_simd cryptd wmi_bmof rapl syscopyarea nvme i2c_core ahci sysfillrect
Nov 14 15:02:15 Zoidberg kernel: ccp sysimgblt k10temp libahci fb_sys_fops nvme_core wmi tpm_crb tpm_tis tpm_tis_core tpm button acpi_cpufreq unix [last unloaded: e1000e]
Nov 14 15:02:15 Zoidberg kernel: CPU: 11 PID: 11738 Comm: sensors Tainted: P        W  O       6.1.106-Unraid #1
Nov 14 15:02:15 Zoidberg kernel: Hardware name: System manufacturer System Product Name/PRIME X570-P, BIOS 5013 03/22/2024
Nov 14 15:02:15 Zoidberg kernel: RIP: 0010:drm_kms_helper_poll_enable+0x6b/0x105 [drm_kms_helper]
Nov 14 15:02:15 Zoidberg kernel: Code: 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 f1 e9 0a e1 48 c7 c1 c5 37 50 a0 48 89 da 48 c7 c7 1d 36 50 a0 48 89 c6 e8 24 13 b8 e0 <0f> 0b eb 74 44 8a 25 11 5f 01 00 45 84 e4 74 68 40 8a af 29 03 00
Nov 14 15:02:15 Zoidberg kernel: RSP: 0018:ffffc90004dd3c30 EFLAGS: 00010282
Nov 14 15:02:15 Zoidberg kernel: RAX: 0000000000000000 RBX: ffff88810176e180 RCX: 0000000000000027
Nov 14 15:02:15 Zoidberg kernel: RDX: 0000000000000002 RSI: ffffffff820d99e1 RDI: 00000000ffffffff
Nov 14 15:02:15 Zoidberg kernel: RBP: ffff888101000010 R08: 0000000000000000 R09: ffffc90004dd3b00
Nov 14 15:02:15 Zoidberg kernel: R10: 00003fffffffffff R11: 000000002d2d2d2d R12: ffff888101000000
Nov 14 15:02:15 Zoidberg kernel: R13: 0000000000000000 R14: ffff888101018470 R15: 0000000000000000
Nov 14 15:02:15 Zoidberg kernel: FS:  00001550098a1740(0000) GS:ffff889faeac0000(0000) knlGS:0000000000000000
Nov 14 15:02:15 Zoidberg kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 14 15:02:15 Zoidberg kernel: CR2: 0000153728d981e0 CR3: 00000004322b2000 CR4: 0000000000350ee0
Nov 14 15:02:15 Zoidberg kernel: Call Trace:
Nov 14 15:02:15 Zoidberg kernel: <TASK>
Nov 14 15:02:15 Zoidberg kernel: ? __warn+0xab/0x122
Nov 14 15:02:15 Zoidberg kernel: ? report_bug+0x109/0x17e
Nov 14 15:02:15 Zoidberg kernel: ? drm_kms_helper_poll_enable+0x6b/0x105 [drm_kms_helper]
Nov 14 15:02:15 Zoidberg kernel: ? handle_bug+0x41/0x6f
Nov 14 15:02:15 Zoidberg kernel: ? exc_invalid_op+0x13/0x60
Nov 14 15:02:15 Zoidberg kernel: ? asm_exc_invalid_op+0x16/0x20
Nov 14 15:02:15 Zoidberg kernel: ? drm_kms_helper_poll_enable+0x6b/0x105 [drm_kms_helper]
Nov 14 15:02:15 Zoidberg kernel: amdgpu_device_resume+0x1b9/0x258 [amdgpu]
Nov 14 15:02:15 Zoidberg kernel: ? pci_pm_default_resume_early+0x29/0x29
Nov 14 15:02:15 Zoidberg kernel: amdgpu_pmops_runtime_resume+0xa6/0xe5 [amdgpu]
Nov 14 15:02:15 Zoidberg kernel: __rpm_callback+0xce/0x13a
Nov 14 15:02:15 Zoidberg kernel: ? pci_pm_default_resume_early+0x29/0x29
Nov 14 15:02:15 Zoidberg kernel: rpm_callback+0x4b/0x64
Nov 14 15:02:15 Zoidberg kernel: rpm_resume+0x40a/0x54e
Nov 14 15:02:15 Zoidberg kernel: ? slab_post_alloc_hook+0x4d/0x15e
Nov 14 15:02:15 Zoidberg kernel: __pm_runtime_resume+0x57/0x76
Nov 14 15:02:15 Zoidberg kernel: amdgpu_hwmon_show_vddgfx+0x5e/0xda [amdgpu]
Nov 14 15:02:15 Zoidberg kernel: dev_attr_show+0x1f/0x44
Nov 14 15:02:15 Zoidberg kernel: sysfs_kf_seq_show+0x7e/0xb9
Nov 14 15:02:15 Zoidberg kernel: seq_read_iter+0x16c/0x346
Nov 14 15:02:15 Zoidberg kernel: vfs_read+0x105/0x19f
Nov 14 15:02:15 Zoidberg kernel: ksys_read+0x76/0xc2
Nov 14 15:02:15 Zoidberg kernel: do_syscall_64+0x65/0x7b
Nov 14 15:02:15 Zoidberg kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Nov 14 15:02:15 Zoidberg kernel: RIP: 0033:0x155009a8dafd
Nov 14 15:02:15 Zoidberg kernel: Code: 31 c0 e9 e6 fe ff ff 50 48 8d 3d 36 a1 0a 00 e8 49 15 02 00 66 0f 1f 84 00 00 00 00 00 80 3d e1 ca 0e 00 00 74 17 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 5b c3 66 2e 0f 1f 84 00 00 00 00 00 48 83 ec
Nov 14 15:02:15 Zoidberg kernel: RSP: 002b:00007ffc4caeaa98 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
Nov 14 15:02:15 Zoidberg kernel: RAX: ffffffffffffffda RBX: 00000000004112e0 RCX: 0000155009a8dafd
Nov 14 15:02:15 Zoidberg kernel: RDX: 0000000000001000 RSI: 000000000042a960 RDI: 0000000000000008
Nov 14 15:02:15 Zoidberg kernel: RBP: 0000155009b6f600 R08: 0000155009b73410 R09: 0000155009b73410
Nov 14 15:02:15 Zoidberg kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000066
Nov 14 15:02:15 Zoidberg kernel: R13: 0000000000000a68 R14: 0000155009b6ed00 R15: 0000000000000a68
Nov 14 15:02:15 Zoidberg kernel: </TASK>
Nov 14 15:02:15 Zoidberg kernel: ---[ end trace 0000000000000000 ]---
Nov 14 15:02:15 Zoidberg kernel: amdgpu 0000:0a:00.0: [drm] Cannot find any crtc or sizes
 

 

Given where it is at in the boot process when this happens, yes this is the amd reset bug a known issues casued by amd.... Installing the plugin should fix this issues which essential modprobe calls amdgpu.

You can learn more on that here:
 

amd reset bug

The AMD reset bug is an issue in qemu with many AMD cards. Apparently qemu fails to correctly reset the card on guest shutdown/reboot which causes the card to not be usable anymore until host reboot.
https://vfio.blogspot.com/2015/04/progress-on-amd-front.html
https://www.reddit.com/r/VFIO/comments/5tf62v/who_still_experiences_the_amd_reset_bug/
https://www.reddit.com/r/VFIO/comments/52ij8j/the_amdresetbug_will_it_ever_be_fixedwhere_to/
https://www.reddit.com/r/VFIO/comments/angluw/restart_vs_shutdown_of_vm/

Possible solution:
https://forum.level1techs.com/t/linux-host-windows-guest-gpu-passthrough-reinitialization-fix/121097
https://forums.unraid.net/topic/69373-graphics-card-reset-issue-amd/?tab=comments#comment-635252
https://github.com/inga-lovinde/RadeonResetBugFix