https://bugzilla.kernel.org/show_bug.cgi?id=205523
Bug ID: 205523 Summary: AMDGPU display lockup during boot with 5.4 RC on Ryzen 2700u Product: Drivers Version: 2.5 Kernel Version: 5.4.0-rc7 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri@kernel-bugs.osdl.org Reporter: briancschott@gmail.com Regression: No
Created attachment 285907 --> https://bugzilla.kernel.org/attachment.cgi?id=285907&action=edit journalctl output
I'm getting a black screen on boot when testing the 5.4 release candidate kernels on a Dell Inspiron 7375 laptop. The system responds to the magic sysrq, so the kernel is not completely dead, but the display is. The system boots correctly with a 5.3.1 kernel. The log showing the stack trace is attached. I'll start working on bisecting the problem soon.
https://bugzilla.kernel.org/show_bug.cgi?id=205523
--- Comment #1 from briancschott@gmail.com --- 1c4259159132ae4ceaf7c6db37a6cf76417f73d9 is the first bad commit commit 1c4259159132ae4ceaf7c6db37a6cf76417f73d9 Author: Shirish S shirish.s@amd.com Date: Tue Jul 16 14:49:48 2019 +0530
drm/amd/display: enable S/G for RAVEN chip
enables gpu_vm_support in dm and adds AMDGPU_GEM_DOMAIN_GTT as supported domain
v2: Move BO placement logic into amdgpu_display_supported_domains
v3: Use amdgpu_bo_validate_uswc in amdgpu_display_supported_domains.
v4: amdgpu_bo_validate_uswc moved to sepperate patch.
Signed-off-by: Shirish S shirish.s@amd.com Signed-off-by: Andrey Grodzovsky andrey.grodzovsky@amd.com Reviewed-by: Nicholas Kazlauskas nicholas.kazlauskas@amd.com Signed-off-by: Alex Deucher alexander.deucher@amd.com
drivers/gpu/drm/amd/amdgpu/amdgpu_display.c | 2 +- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
https://bugzilla.kernel.org/show_bug.cgi?id=205523
Alex Deucher (alexdeucher@gmail.com) changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexdeucher@gmail.com
--- Comment #2 from Alex Deucher (alexdeucher@gmail.com) --- Does disabling the IOMMU help? Set iommu=off or iommu=pt on the kernel command line.
https://bugzilla.kernel.org/show_bug.cgi?id=205523
--- Comment #3 from briancschott@gmail.com --- "iommu=off" seems to work, "iommu=pt" does not.
https://bugzilla.kernel.org/show_bug.cgi?id=205523
Haxk20 (haxk612@gmail.com) changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |haxk612@gmail.com
--- Comment #4 from Haxk20 (haxk612@gmail.com) --- (In reply to Alex Deucher from comment #2)
Does disabling the IOMMU help? Set iommu=off or iommu=pt on the kernel command line.
Is this permanent too ? This will regress and produce tearing in games running with PRIME setup.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠bugzilla.kernel.org