dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 115251] New: amdgpu: Black screen + hang with Kaveri
Date: Thu, 24 Mar 2016 19:40:36 +0000	[thread overview]
Message-ID: <bug-115251-2300@https.bugzilla.kernel.org/> (raw)

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@kernel-bugs.osdl.org
          Reporter: linux@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@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@amd.com>
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@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.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-03-24 19:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 19:40 bugzilla-daemon [this message]
2016-03-24 19:52 ` [Bug 115251] amdgpu: Black screen + hang with Kaveri bugzilla-daemon
2016-03-26  7:59 ` bugzilla-daemon
2016-04-21  4:55 ` bugzilla-daemon
2016-04-21 13:52 ` bugzilla-daemon
2016-06-03  5:19 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-115251-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox