Bug 1742960
| Summary: | Frozen display (green) on AMD Ryzen 5 2400G | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Suvayu <fatkasuvayu> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 30 | CC: | airlied, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, steved | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2020-05-26 18:25:22 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Suvayu
2019-08-18 03:47:04 UTC
correction: after it hangs, I can login remotely, and shutdown. I also tried vanilla kernels from Thorsten's repos, same issue. - 5.2.9 from kernel-vanilla-stable - 5.3.0 (rc4) from kernel-vanilla-mainline (I believe this is the closest to rawhide) I have now tried booting with: - 5.3.7 from the fedora repos - 5.4.0 (rc5) from kernel-vanilla-mainline No luck. What do I do to get someone to have a look? F31 is out, but I can't upgrade because of this. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 30 kernel bugs. Fedora 30 has now been rebased to 5.5.7-100.fc30. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 31, and are still experiencing this issue, please change the version to Fedora 31. If you experience different issues, please open a new bug report for those. Hi, Sorry about the delay, unfortunately I cannot provide any more info as I do not have access to this particular machine, it's in a different country. That said, since then I have tried installing Fedora 31 (not 30) on another Ryzen with Vega IGP (ThinkPad T495s), and I have faced similar issues. Hardware: AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile Gfx (-MT MCP-) Kernel: 5.5.7-200.fc31.x86_64 x86_64 Login Manager: LightDM Desktop: XFCE I have tried with most of the 5.x series that have been pushed to fedora updates from January 2020. While initially I could get a login screen, but logging in would lead to a hard lock with a black screen. The journal would show an unending sequence of kernel backtraces like below (this one was with kernel 5.4.20 from end of Feb): ------------[ cut here ]------------ WARNING: CPU: 5 PID: 60 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:967 dcn10_verify_allow_pstate_change_high+0x32/0x290 [amdgpu] Modules linked in: ccm xt_MASQUERADE nf_conntrack_netlink xt_addrtype br_netfilter bridge stp llc ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables overlay ip6table_filter ip6_tables iptable_filter sunrpc squashfs zstd_decompress loop edac_mce_amd kvm_amd ccp kvm snd_hda_codec_realtek snd_hda_codec_generic iwlmvm snd_hda_codec_hdmi snd_hda_intel irqbypass snd_intel_dspcfg snd_hda_codec snd_usb_audio mac80211 snd_hda_core btusb crct10dif_pclmul snd_usbmidi_lib btrtl snd_rawmidi btbcm crc32_pclmul snd_hwdep uvcvideo btintel snd_seq ghash_clmulni_intel videobuf2_vmalloc videobuf2_memops snd_seq_device videobuf2_v4l2 libarc4 bluetooth pcspkr videobuf2_common wmi_bmof k10temp videodev snd_pcm iwlwifi thinkpad_acpi ecdh_generic ipmi_devintf sp5100_tco snd_timer ledtrig_audio mc joydev ecc i2c_piix4 snd_pci_acp3x cfg80211 snd ucsi_acpi typec_ucsi ipmi_msghandler rtsx_pci_ms soundcore memstick typec rfkill i2c_scmi acpi_cpufreq ip_tables amdgpu amd_iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper drm hid_logitech_hidpp rtsx_pci_sdmmc mmc_core crc32c_intel nvme rtsx_pci r8169 nvme_core serio_raw wmi video pinctrl_amd hid_logitech_dj fuse CPU: 5 PID: 60 Comm: kworker/u32:1 Not tainted 5.4.20-200.fc31.x86_64 #1 Hardware name: LENOVO 20QJCTO1WW/20QJCTO1WW, BIOS R13ET39W(1.13 ) 10/11/2019 Workqueue: events_unbound commit_work [drm_kms_helper] RIP: 0010:dcn10_verify_allow_pstate_change_high+0x32/0x290 [amdgpu] Code: 8b 87 10 03 00 00 48 89 fb 48 8b b8 b0 01 00 00 e8 53 14 01 00 84 c0 0f 85 55 02 00 00 80 3d 64 02 27 00 00 0f 85 4b 02 00 00 <0f> 0b 80 bb a3 01 00 00 00 0f 84 39 02 00 00 48 8b 83 10 03 00 00 RSP: 0018:ffffb50f40347ad8 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff8b3d648f0000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffff8b3d70f57908 RDI: ffff8b3d70f57908 RBP: ffff8b3d648f0000 R08: ffff8b3d70f57908 R09: 0000000000000003 R10: 0000000000000000 R11: 0000000000000001 R12: ffff8b3d313b01b8 R13: ffff8b3d648f0000 R14: 0000000000000004 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff8b3d70f40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fdef0009168 CR3: 000000036777c000 CR4: 00000000003406e0 Call Trace: dcn10_pipe_control_lock.part.0+0x69/0x70 [amdgpu] dc_commit_updates_for_stream+0xf34/0x14b0 [amdgpu] ? amdgpu_display_get_crtc_scanoutpos+0x85/0x190 [amdgpu] amdgpu_dm_atomic_commit_tail+0xb5e/0x1d70 [amdgpu] ? __schedule+0x2da/0x730 ? ttwu_do_wakeup+0x19/0x140 ? schedule+0x39/0xa0 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? _cond_resched+0x15/0x30 ? wait_for_completion_timeout+0x38/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? commit_tail+0x94/0x110 [drm_kms_helper] commit_tail+0x94/0x110 [drm_kms_helper] process_one_work+0x1b5/0x360 worker_thread+0x50/0x3c0 kthread+0xf9/0x130 ? process_one_work+0x360/0x360 ? kthread_park+0x90/0x90 ret_from_fork+0x22/0x40 ---[ end trace 682c1b2b8324159b ]--- [drm] pstate TEST_DEBUG_DATA: 0x36F60000 In the meantime I did find a workaround on the freedesktop gitlab instance (can't find the issue right now). If I disable compositing (with `xfconf-query -c xfwm4 -p /general/use_compositing -s false'), I could login to a functioning desktop. The condition has now changed to, I still can't login, but instead of a hard lock with black screen, LightDM segfaults. Curiously, I cannot spot a kernel backtrace any more. The workaround of disabling compositing still works. Should I update this bug report with more info, or is it better to go on a new issue? This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. The Fedora bugzilla has been such a joke. Over the last year and half I have reported several bugs, and *all* have gone this way, me talking to myself (on several occasions I have even tried to highlight them on IRC). I have been a Fedora user for over 10 years, never has it been this bad. Any day I would take the old community, struggling with drivers, pulseaudio, and systemd, and actually getting a response and fixing the problems together over this kind of neglect. Disgraceful. Maybe I should move to Arch. |