All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108577] Black X laptop screen with cursor if HDMI not plugged in, bisected
Date: Sun, 28 Oct 2018 01:53:53 +0000	[thread overview]
Message-ID: <bug-108577-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1530 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=108577

            Bug ID: 108577
           Summary: Black X laptop screen with cursor if HDMI not plugged
                    in, bisected
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: blocker
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: duncan_roe@optusnet.com.au

Created attachment 142239
  --> https://bugs.freedesktop.org/attachment.cgi?id=142239&action=edit
Git diff specifying 2 commits (GD is aliased to git diff)

(High severity because laptop is useless when travelling)
With HDMI unplugged, X laptop screen is black with only a cursor. Cursor
changes shape as it moves over xterm windows put there by xinitrc.
Bisecting in git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git finds
2bfb0b678e48dee76543bfa2079b7e42609332fb has the problem but adjacent commit
9c24c10a2c1e1bb478b6bb70612d9e885aee044f does not.
There is an oddity with git diff between these two: git diff <commit1>
<commit2> produces copious output and a git warning (see attachment), but git
checkout <commit2>; git diff <commit1> only shows one patched file (next
attachment). You might want to try this - I re-cloned the repo in case the old
one was corrupted but it made no difference.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3053 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-10-28  1:53 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-28  1:53 bugzilla-daemon [this message]
2018-10-28  1:57 ` [Bug 108577] Black X laptop screen with cursor if HDMI not plugged in, bisected bugzilla-daemon
2018-10-28  2:09 ` bugzilla-daemon
2018-10-28 22:48 ` bugzilla-daemon
2018-10-28 22:50 ` bugzilla-daemon
2018-10-28 22:55 ` bugzilla-daemon
2018-10-28 22:57 ` bugzilla-daemon
2018-10-28 23:00 ` bugzilla-daemon
2018-10-28 23:02 ` bugzilla-daemon
2018-10-28 23:03 ` bugzilla-daemon
2018-10-29 11:28 ` bugzilla-daemon
2018-10-29 21:42 ` bugzilla-daemon
2018-10-30  3:08 ` bugzilla-daemon
2018-10-30 21:18 ` bugzilla-daemon
2018-10-30 21:30 ` bugzilla-daemon
2018-10-30 21:40 ` bugzilla-daemon
2018-10-30 21:42 ` bugzilla-daemon
2018-10-31  0:38 ` bugzilla-daemon
2018-10-31  0:44 ` bugzilla-daemon
2018-11-02  2:31 ` bugzilla-daemon
2018-11-02 15:56 ` bugzilla-daemon
2018-11-02 15:56 ` bugzilla-daemon
2018-11-03  0:23 ` bugzilla-daemon
2018-11-03  0:28 ` bugzilla-daemon
2018-11-03  0:30 ` bugzilla-daemon
2018-11-05 19:27 ` bugzilla-daemon
2018-11-05 21:02 ` bugzilla-daemon
2018-11-06  3:45 ` bugzilla-daemon
2018-11-06  3:50 ` bugzilla-daemon
2018-11-06  6:12 ` bugzilla-daemon
2018-11-06  9:34 ` bugzilla-daemon
2018-11-06 21:43 ` bugzilla-daemon
2018-11-07  8:21 ` bugzilla-daemon
2018-11-07 22:12 ` bugzilla-daemon
2018-11-29 16:26 ` bugzilla-daemon
2018-11-30 11:18 ` bugzilla-daemon
2018-12-03 22:28 ` bugzilla-daemon
2019-01-08  4:07 ` bugzilla-daemon
2019-01-08  4:19 ` bugzilla-daemon
2019-08-05  7:59 ` 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-108577-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.