dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 112921] Lock-up after screensaver on radeon
Date: Tue, 23 Feb 2016 15:19:20 +0000	[thread overview]
Message-ID: <bug-112921-2300-KkXoKu7VfO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-112921-2300@https.bugzilla.kernel.org/>

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

Alex Deucher <alexdeucher@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alexdeucher@gmail.com

--- Comment #4 from Alex Deucher <alexdeucher@gmail.com> ---
This looks like the vblank regression bug.  See this thread for more info:
https://lists.freedesktop.org/archives/dri-devel/2016-January/098823.html
and the fdo bug:
https://bugs.freedesktop.org/show_bug.cgi?id=93746

-- 
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

  parent reply	other threads:[~2016-02-23 15:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23  9:23 [Bug 112921] New: Lock-up after screensaver on radeon bugzilla-daemon
2016-02-23  9:25 ` [Bug 112921] " bugzilla-daemon
2016-02-23  9:28 ` bugzilla-daemon
2016-02-23  9:30 ` bugzilla-daemon
2016-02-23 15:19 ` bugzilla-daemon [this message]
2016-02-25  7:22 ` bugzilla-daemon
2016-02-27 12:09 ` bugzilla-daemon
2016-02-29  1:20 ` bugzilla-daemon
2016-03-06  8:08 ` bugzilla-daemon
2016-03-09 11:24 ` bugzilla-daemon
2016-03-09 11:24 ` [Bug 112921] [radeon] Lock-up after screensaver 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-112921-2300-KkXoKu7VfO@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;
as well as URLs for NNTP newsgroup(s).