All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107928] Screen regularly turns black, reboot needed
Date: Wed, 17 Oct 2018 22:35:21 +0000	[thread overview]
Message-ID: <bug-107928-502-sQsp5KVYzq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107928-502@http.bugs.freedesktop.org/>


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

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

--- Comment #10 from Matthew Vaughn <nethershaw@gmail.com> ---
I've determined that the deadlock and stack trace found in my dmesg logs is
emitted precisely when I attempt to wake the machine's display from sleep by
touching the keyboard or mouse, and not before.

If I leave the machine on a terminal console instead of in a running X session,
the display never sleeps, and the deadlock never occurs.

The first instance of the deadlock on my machine occurred during a session
following an upgrade of the xf86-video-amdgpu drivers from version 18.0.1 to
18.1.0, and simultaneously, of Mesa to a checkout of the master branch ca.
commit 0d495bec25bd7584de4e988c2b4528c1996bc1d0, or approximately 2018-09-26
04:16 UTC. I am attempting now to revert both of these upgrades one at a time
in order to determine whether either of them is implicated.

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

[-- Attachment #1.2: Type: text/html, Size: 1767 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

  parent reply	other threads:[~2018-10-17 22:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14  9:44 [Bug 107928] Screen regularly turns black, reboot needed bugzilla-daemon
2018-09-14  9:51 ` bugzilla-daemon
2018-09-14 10:01 ` bugzilla-daemon
2018-10-07 15:48 ` bugzilla-daemon
2018-10-07 21:10 ` bugzilla-daemon
2018-10-07 22:16 ` bugzilla-daemon
2018-10-08 22:02 ` bugzilla-daemon
2018-10-14 14:16 ` bugzilla-daemon
2018-10-14 14:16 ` bugzilla-daemon
2018-10-14 17:26 ` bugzilla-daemon
2018-10-17 22:35 ` bugzilla-daemon [this message]
2018-10-19  0:51 ` bugzilla-daemon
2018-10-19  7:23 ` bugzilla-daemon
2018-10-19 16:07 ` bugzilla-daemon
2018-11-05 20:12 ` bugzilla-daemon
2018-11-06 18:56 ` bugzilla-daemon
2019-11-19  8:55 ` 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-107928-502-sQsp5KVYzq@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.