[Bug 115251] New: amdgpu: Black screen + hang with Kaveri
bugzilla-daemon at bugzilla.kernel.org
bugzilla-daemon at bugzilla.kernel.org
Thu Mar 24 19:40:36 UTC 2016
https://bugzilla.kernel.org/show_bug.cgi?id=115251
Bug ID: 115251
Summary: amdgpu: Black screen + hang with Kaveri
Product: Drivers
Version: 2.5
Kernel Version: 4.4.5
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri at kernel-bugs.osdl.org
Reporter: linux at bernd-steinhauser.de
Regression: No
Created attachment 210661
--> https://bugzilla.kernel.org/attachment.cgi?id=210661&action=edit
Xorg log
With 4.4.6, I noticed I cannot use the xf86-video-amdgpu ddx anymore.
When the X server starts, the screen will go black, in the log, there is a
message telling me that the device initialization failed.
I can't get the console back either, but emergency sync, ro remount and
poweroff do work.
Before starting X, the driver seems to work fine, only when starting X things
go wrong.
The issue is present with 4.5.0 as well.
Will upload a Xorg log, but it won't be much of a help, because it seems to be
cut off, even though I waited for a long time before sync and unmount.
Also tried to capture dmesg, but got only a partial one as well which was cut
off before things got interesting.
bisect led to (on the 4.4.y branch):
a46a700abc520bfadf5fa1cc371ba07d6d7f9230 is the first bad commit
commit a46a700abc520bfadf5fa1cc371ba07d6d7f9230
Author: Christian König <christian.koenig at amd.com>
Date: Fri Feb 26 16:18:15 2016 +0100
drm/amdgpu: apply gfx_v8 fixes to gfx_v7 as well
····
commit feebe91aa9a9d99d9ec157612a614fadb79beb99 upstream.
····
We never ported that back to CIK, so we could run into VM faults here.
····
Signed-off-by: Christian König <christian.koenig at amd.com>
Reviewed-by: Alex Deucher <alexander.deucher at amd.com>
Signed-off-by: Greg Kroah-Hartman <gregkh at linuxfoundation.org>
:040000 040000 3930bee60c2e64b348ee8e5f618326b5f6141cdc
8501edda2a7d8ee201cde839ac01d943bec84a51 M drivers
Reverting that commit on top of 4.4.6 (or the corresponding one on top of
4.5.0) gets things working again.
--
You are receiving this mail because:
You are watching the assignee of the bug.
More information about the dri-devel
mailing list