Bug 111459

Summary:

AMDg black screen

Product:

DRI

Reporter:

peter m <malkovjohnny>

Component:

DRM/AMDgpu

Assignee:

Default DRI bug account <dri-devel>

Status:

RESOLVED MOVED

QA Contact:

Severity:

not set

Priority:

not set

Version:

unspecified

Hardware:

x86-64 (AMD64)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
Xorg log	none

Description peter m 2019-08-21 19:16:58 UTC

Update kernel from 5.1.20-300.fc30.x86_64 to newer versions cause black screen. After entering password in welcome screen it turns completely black.

Problem exists on new kernels:
- 5.2.8-200.fc30.x86_64
- 5.2.9-200.fc30.x86_64

Environment:
CPU - AMD Ryzen 3 2200G with Radeon Vega Graphics
video - VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] (rev c8)
XFCE: xfce4-panel 4.13.7 (Xfce 4.14pre2)
Xorg: Build ID: xorg-x11-server 1.20.5-4.fc30

Aug 21 21:06:57 kernel: ------------[ cut here ]------------
Aug 21 21:06:57 kernel: WARNING: CPU: 0 PID: 182 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:854 dcn10_verify_allow_pstate_change_high.cold+0xc/0x229 [amdgpu]
Aug 21 21:06:57 kernel: Modules linked in: ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat 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 ip6table_filter ip6_tables iptable_filter ip_tables sunrpc snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi ledtrig_audio snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq edac_mce_amd snd_seq_device joydev snd_pcm snd_timer ccp kvm snd soundcore irqbypass crct10dif_pclmul pcc_cpufreq crc32_pclmul ghash_clmulni_intel acpi_cpufreq wmi_bmof k10temp sp5100_tco i2c_piix4 gpio_amdpt gpio_generic amdgpu amd_iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper crc32c_intel drm r8169 wmi pinctrl_amd video
Aug 21 21:06:57 kernel: CPU: 0 PID: 182 Comm: kworker/u32:7 Not tainted 5.2.9-200.fc30.x86_64 #1
Aug 21 21:06:57 kernel: Hardware name: Gigabyte Technology Co., Ltd. A320M-S2H V2/A320M-S2H V2-CF, BIOS F2 12/25/2018
Aug 21 21:06:57 kernel: Workqueue: events_unbound commit_work [drm_kms_helper]
Aug 21 21:06:57 kernel: RIP: 0010:dcn10_verify_allow_pstate_change_high.cold+0xc/0x229 [amdgpu]
Aug 21 21:06:57 kernel: Code: 83 c8 ff e9 31 b0 f9 ff 48 c7 c7 f8 80 68 c0 e8 f4 d0 b5 c1 0f 0b 83 c8 ff e9 1b b0 f9 ff 48 c7 c7 f8 80 68 c0 e8 de d0 b5 c1 <0f> 0b 80 bb 93 01 00 00 00 75 05 e9 75 d4 f9 ff 48 8b 83 80 02 00
Aug 21 21:06:57 kernel: RSP: 0018:ffffb5b741037b58 EFLAGS: 00010246
Aug 21 21:06:57 kernel: RAX: 0000000000000024 RBX: ffff9cfa0d83d000 RCX: 0000000000000006
Aug 21 21:06:57 kernel: RDX: 0000000000000000 RSI: 0000000000000092 RDI: ffff9cfa18a17900
Aug 21 21:06:57 kernel: RBP: ffff9cfa0d83d000 R08: 0000000000000001 R09: 00000000000003fd
Aug 21 21:06:57 kernel: R10: ffffffff83bef4e4 R11: 0000000000000003 R12: ffff9cf9f68b81b8
Aug 21 21:06:57 kernel: R13: 0000000000000000 R14: ffff9cf9f68b81b8 R15: 0000000000000004
Aug 21 21:06:57 kernel: FS:  0000000000000000(0000) GS:ffff9cfa18a00000(0000) knlGS:0000000000000000
Aug 21 21:06:57 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 21 21:06:57 kernel: CR2: 000055afe80cca08 CR3: 00000001ea35a000 CR4: 00000000003406f0
Aug 21 21:06:57 kernel: Call Trace:
Aug 21 21:06:57 kernel:  dcn10_pipe_control_lock.part.0+0x69/0x70 [amdgpu]
Aug 21 21:06:57 kernel:  dc_commit_updates_for_stream+0x84c/0xc10 [amdgpu]
Aug 21 21:06:57 kernel:  amdgpu_dm_atomic_commit_tail+0xa79/0x1940 [amdgpu]
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x40/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x34/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x40/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x34/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x40/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x34/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x40/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x34/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x40/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x40/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x34/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x40/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x34/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x40/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x34/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x40/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x34/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x40/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x34/0x70
Aug 21 21:06:57 kernel:  ? _cond_resched+0x15/0x30
Aug 21 21:06:57 kernel:  ? wait_for_completion_timeout+0x38/0x170
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x40/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x34/0x70
Aug 21 21:06:57 kernel:  ? __switch_to_asm+0x40/0x70
Aug 21 21:06:57 kernel:  ? __switch_to+0x152/0x440
Aug 21 21:06:57 kernel:  ? commit_tail+0x3c/0x70 [drm_kms_helper]
Aug 21 21:06:57 kernel:  commit_tail+0x3c/0x70 [drm_kms_helper]
Aug 21 21:06:57 kernel:  process_one_work+0x19d/0x380
Aug 21 21:06:57 kernel:  worker_thread+0x50/0x3b0
Aug 21 21:06:57 kernel:  kthread+0xfb/0x130
Aug 21 21:06:57 kernel:  ? process_one_work+0x380/0x380
Aug 21 21:06:57 kernel:  ? kthread_park+0x80/0x80
Aug 21 21:06:57 kernel:  ret_from_fork+0x22/0x40
Aug 21 21:06:57 kernel: ---[ end trace 4ef68d388d918f99 ]---
Aug 21 21:06:57 kernel: [drm] pstate TEST_DEBUG_DATA: 0x36F60000

Comment 1 peter m 2019-08-21 19:18:53 UTC

Created attachment 145120 [details]
Xorg log

Comment 2 Tom Seewald 2019-08-21 20:47:35 UTC

Could you try applying the following patch set from AMD's Nicholas Kazlauskas:
https://patchwork.freedesktop.org/series/64505/

There have been similar reports filed on the kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=204181

Comment 3 peter m 2019-09-04 16:57:16 UTC

Unfortunately I don't know how to apply this patch/patches.

Updated to new kernel 5.2.11-200.fc30.x86_64, problem still exists.

Sep 04 19:45:23 kernel: WARNING: CPU: 2 PID: 1014 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_hw_sequencer.c:854 dcn10_verify_allow_pstate_change_high.cold+0xc/0x229 [amdgpu]
Sep 04 19:45:23 kernel: Modules linked in: ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat 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 ip6table_filter ip6_tables iptable_filter ip_tables sunrpc snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core edac_mce_amd snd_hwdep snd_seq ccp snd_seq_device snd_pcm snd_timer kvm snd irqbypass joydev soundcore sp5100_tco i2c_piix4 crct10dif_pclmul wmi_bmof crc32_pclmul k10temp ghash_clmulni_intel pcc_cpufreq gpio_amdpt gpio_generic acpi_cpufreq amdgpu amd_iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper crc32c_intel drm r8169 wmi video pinctrl_amd
Sep 04 19:45:23 kernel: CPU: 2 PID: 1014 Comm: InputThread Not tainted 5.2.11-200.fc30.x86_64 #1
Sep 04 19:45:23 kernel: Hardware name: Gigabyte Technology Co., Ltd. A320M-S2H V2/A320M-S2H V2-CF, BIOS F2 12/25/2018
Sep 04 19:45:23 kernel: RIP: 0010:dcn10_verify_allow_pstate_change_high.cold+0xc/0x229 [amdgpu]
Sep 04 19:45:23 kernel: Code: 83 c8 ff e9 85 af f9 ff 48 c7 c7 f8 20 78 c0 e8 e8 27 a6 f0 0f 0b 83 c8 ff e9 6f af f9 ff 48 c7 c7 f8 20 78 c0 e8 d2 27 a6 f0 <0f> 0b 80 bb 93 01 00 00 00 75 05 e9 c9 d3 f9 ff 48 8b 83 80 02 00
Sep 04 19:45:23 kernel: RSP: 0018:ffff9ba201da3a00 EFLAGS: 00010246
Sep 04 19:45:23 kernel: RAX: 0000000000000024 RBX: ffff8a12ce72c000 RCX: 0000000000000006
Sep 04 19:45:23 kernel: RDX: 0000000000000000 RSI: 0000000000000082 RDI: ffff8a12d8a97900
Sep 04 19:45:23 kernel: RBP: ffff8a12ce72c000 R08: 0000000000000001 R09: 00000000000003f9
Sep 04 19:45:23 kernel: R10: ffffffffb2bf03e0 R11: 0000000000000003 R12: ffff8a12caef81b8
Sep 04 19:45:23 kernel: R13: ffff8a12caef9bc8 R14: ffff8a12caef81b8 R15: ffff8a12b8420200
Sep 04 19:45:23 kernel: FS:  00007fc4cec4b700(0000) GS:ffff8a12d8a80000(0000) knlGS:0000000000000000
Sep 04 19:45:23 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 04 19:45:23 kernel: CR2: 00007f19f6f298a0 CR3: 00000001fb7e4000 CR4: 00000000003406e0
Sep 04 19:45:23 kernel: Call Trace:
Sep 04 19:45:23 kernel:  dcn10_pipe_control_lock.part.0+0x69/0x70 [amdgpu]
Sep 04 19:45:23 kernel:  dc_stream_set_cursor_attributes+0x121/0x170 [amdgpu]
Sep 04 19:45:23 kernel:  handle_cursor_update.isra.0+0x1af/0x310 [amdgpu]
Sep 04 19:45:23 kernel:  drm_atomic_helper_async_commit+0x63/0xd0 [drm_kms_helper]
Sep 04 19:45:23 kernel:  drm_atomic_helper_commit+0xdb/0x110 [drm_kms_helper]
Sep 04 19:45:23 kernel:  drm_atomic_helper_update_plane+0xec/0x100 [drm_kms_helper]
Sep 04 19:45:23 kernel:  drm_mode_cursor_universal+0x12c/0x240 [drm]
Sep 04 19:45:23 kernel:  drm_mode_cursor_common+0xc9/0x220 [drm]
Sep 04 19:45:23 kernel:  ? drm_mode_setplane+0x2a0/0x2a0 [drm]
Sep 04 19:45:23 kernel:  drm_mode_cursor_ioctl+0x4d/0x70 [drm]
Sep 04 19:45:23 kernel:  drm_ioctl_kernel+0xaa/0xf0 [drm]
Sep 04 19:45:23 kernel:  drm_ioctl+0x208/0x390 [drm]
Sep 04 19:45:23 kernel:  ? drm_mode_setplane+0x2a0/0x2a0 [drm]
Sep 04 19:45:23 kernel:  amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
Sep 04 19:45:23 kernel:  do_vfs_ioctl+0x405/0x660
Sep 04 19:45:23 kernel:  ksys_ioctl+0x5e/0x90
Sep 04 19:45:23 kernel:  ? ksys_read+0xc4/0xe0
Sep 04 19:45:23 kernel:  __x64_sys_ioctl+0x16/0x20
Sep 04 19:45:23 kernel:  do_syscall_64+0x5f/0x1a0
Sep 04 19:45:23 kernel:  ? page_fault+0x8/0x30
Sep 04 19:45:23 kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Sep 04 19:45:23 kernel: RIP: 0033:0x7fc4f687e1fb
Sep 04 19:45:23 kernel: Code: 0f 1e fa 48 8b 05 8d dc 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 5d dc 0c 00 f7 d8 64 89 01 48
Sep 04 19:45:23 kernel: RSP: 002b:00007fc4cec492e8 EFLAGS: 00003246 ORIG_RAX: 0000000000000010
Sep 04 19:45:23 kernel: RAX: ffffffffffffffda RBX: 00007fc4cec49320 RCX: 00007fc4f687e1fb
Sep 04 19:45:23 kernel: RDX: 00007fc4cec49320 RSI: 00000000c01c64a3 RDI: 0000000000000010
Sep 04 19:45:23 kernel: RBP: 00000000c01c64a3 R08: 0000000000000276 R09: 0000000000000001
Sep 04 19:45:23 kernel: R10: 0000000000000000 R11: 0000000000003246 R12: 00005591448cec60
Sep 04 19:45:23 kernel: R13: 0000000000000010 R14: 000000000000027a R15: 0000000000000155
Sep 04 19:45:23 kernel: ---[ end trace 5a51309b874ce6f0 ]---
Sep 04 19:45:23 kernel: [drm] pstate TEST_DEBUG_DATA: 0x3FF60000
Sep 04 19:45:23 kernel: ------------[ cut here ]------------

Comment 4 peter m 2019-09-04 18:06:51 UTC

Thread with similar problem

https://bugs.freedesktop.org/show_bug.cgi?id=109628

Comment 5 tajgaividra 2019-09-06 01:08:26 UTC

Hi,

Have you tried reverting the xorg amdgpu package to an older version? Of course that is just a workaround.

Comment 6 peter m 2019-09-11 17:18:38 UTC

(In reply to tajgaividra from comment #5)
> Hi,
> 
> Have you tried reverting the xorg amdgpu package to an older version? Of
> course that is just a workaround.

only kernel driver is used


dnf list available | grep xorg-x11-drv-amdgpu
xorg-x11-drv-amdgpu.x86_64                                      19.0.1-1.fc30

Comment 7 Martin Peres 2019-11-19 09:39:11 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/891.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.