All of lore.kernel.org
 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 09:25:22 +0000	[thread overview]
Message-ID: <bug-112921-2300-iStaPrQxK4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-112921-2300@https.bugzilla.kernel.org/>

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

Jean Delvare <jdelvare@suse.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Regression|No                          |Yes

--- Comment #1 from Jean Delvare <jdelvare@suse.de> ---
I compared the boot messages from kernels v4.3.5 and v4.4.2. The only
difference is the following error in v4.3.5 which is no longer present in
v4.4.2:

[drm:btc_dpm_set_power_state [radeon]] *ERROR* rv770_set_sw_state failed

I have no idea if this is related.

-- 
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-02-23  9:25 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 ` bugzilla-daemon [this message]
2016-02-23  9:28 ` [Bug 112921] " bugzilla-daemon
2016-02-23  9:30 ` bugzilla-daemon
2016-02-23 15:19 ` bugzilla-daemon
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-iStaPrQxK4@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.