All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 208179] New: [amdgpu] black screen after exiting X
Date: Mon, 15 Jun 2020 07:59:38 +0000	[thread overview]
Message-ID: <bug-208179-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=208179

            Bug ID: 208179
           Summary: [amdgpu] black screen after exiting X
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.7.2
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: shlomo@fastmail.com
                CC: daniel@ffwll.ch, dri-devel@lists.freedesktop.org
        Regression: Yes

After exiting X on a virtual terminal that isn't tty1, the screen becomes all
black instead of showing the text tty. Keyboard input still goes to the text
tty, but I can't see what I'm typing.

After this happens, a workaround is to switch to a different virtual terminal
(with Ctrl+Alt+FN) that is in text mode (not running X) and then switch back.
Then the text tty is visible and works normally.

Switching to a different virtual terminal that is running X and then switching
back doesn't help. The problematic virtual terminal is still all black.

My graphics card is Gigabyte Radeon RX VEGA 56 GAMING OC 8G. (amdgpu)

The bug appeared after upgrading Arch linux 5.6.15.arch1-1 to 5.7.2.arch1-1.

The first bad commit is 64914da24ea95d2b2f7017d014d74c26005d8780
(drm/fbdev-helper: don't force restores).
The previous commit e81a2557e0650ee0ce37ba14476ddb709d6daf57 is good.

When testing these two commits, I needed to cherry-pick the following fixes:
a9a3ed1eff3601b63aea4fb462d8b3b92c7c1e7e (x86: Fix early boot crash on gcc-10,
third try)
e33a814e772cdc36436c8c188d8c42d019fda639 (scripts/dtc: Remove redundant YYLOC
global declaration)
df6d4f9db79c1a5d6f48b59db35ccd1e9ff9adfc (x86/boot/compressed: Don't declare
__force_order in kaslr_64.c)
These are needed when compiling with GCC 10 to fix compilation errors and a
hang on boot.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
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:[~2020-06-15  7:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15  7:59 bugzilla-daemon [this message]
2020-06-20 19:02 ` [Bug 208179] [amdgpu] black screen after exiting X bugzilla-daemon
2020-06-23 14:31 ` bugzilla-daemon
2020-06-23 14:54 ` bugzilla-daemon
2020-06-29  6:48 ` bugzilla-daemon
2020-07-03 11:02 ` 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-208179-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.