Bug 1664012

Summary: efi-lockdown.patch don't allow working AMDGPU debug utility
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: airlied, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, steved, yaneti
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-16 16:35:34 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:

Description Mikhail 2019-01-07 14:16:05 UTC 
Description of problem:
My computer often hunging with message in kernel log:

[  229.741741] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=28686, emitted seq=28688
[  229.741806] [drm] GPU recovery disabled.

AMDGPU developers have advised dump gfx ring content and waves after the hang is happening.

https://lists.freedesktop.org/archives/amd-gfx/2018-December/029790.html

But as it turned out, it is impossible on default Fedora kernels due of the patch 201 efi-lockdown.patch.

Version-Release number of selected component (if applicable):
Any Fedora kernel with AMDGPU hardware.

Actual results:
# cat /sys/kernel/debug/dri/0/amdgpu_gca_config | xxd -e -
cat: /sys/kernel/debug/dri/0/amdgpu_ring_gfx: Operation not permitted

Expected results:
# cat /sys/kernel/debug/dri/0/amdgpu_gca_config | xxd -e -
00000000: 00000003 00000004 00000004 00000010  ................
00000010: 00000001 00000004 00000010 00000100  ................
00000020: 00000020 00000008 00000020 00000100   ....... .......
00000030: 00000030 000004c0 00000000 0000ffff  0...............
00000040: 00000000 00000000 00000000 00000000  ................
00000050: 00000000 00000000 2a114042 00000010  ........B@.*....
00000060: 00000001 00000000 00fe9fcf 0000008d  ................
00000070: 00000001 0000687f 000000c1 00002308  .....h.......#..
00000080: 00001458                             X...


Additional info:
Comment 1 Mikhail 2019-01-16 16:34:18 UTC 
Fixed in 5.0.0-0.rc1.git4.1.fc30
Comment 2 Mikhail 2019-01-16 16:35:34 UTC 

*** This bug has been marked as a duplicate of bug 1658675 ***