All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67121] Broken suspend/resume with radeon/KMS on RS482M
Date: Fri, 17 Jan 2014 23:39:10 +0000	[thread overview]
Message-ID: <bug-67121-2300-X0XCL8c8kf@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-67121-2300@https.bugzilla.kernel.org/>

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

--- Comment #7 from Adrian Knoth <adi@drcomp.erfurt.thur.de> ---
Random observation: high CPU usage "uncripples" the video output.

That is: I suspend to RAM, I resume and unplug the AC, causing the screen to be
heavily distorted.

When I blindly start burnK7 (from Debian's cpuburn package), CPU usage on one
of the cores jumps to 100% and I have a wonderful clear and perfect screen. As
soon as I terminate burnK7, the corruption is back. (with AC unplugged all the
time; of course, plugging the AC back in always fixes the corruption).

So it's a power management issue. For some reasons, the radeon driver (or the
hardware) is sensitive to CPU power saving states (idle states?) and the
presence of an external power supply. And all this only happens with KMS, not
with UMS.

So is it an ACPI/PM bug? Or DRI?

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

  parent reply	other threads:[~2014-01-17 23:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 15:14 [Bug 67121] New: Broken suspend/resume with radeon/KMS on RS482M bugzilla-daemon
2013-12-16 15:15 ` [Bug 67121] " bugzilla-daemon
2013-12-16 15:15 ` bugzilla-daemon
2013-12-16 15:16 ` bugzilla-daemon
2013-12-16 15:17 ` bugzilla-daemon
2013-12-16 15:17 ` bugzilla-daemon
2013-12-16 15:18 ` bugzilla-daemon
2014-01-17 23:39 ` bugzilla-daemon [this message]
2014-01-18 17:27 ` bugzilla-daemon
2014-01-18 18:05 ` bugzilla-daemon
2014-01-18 19:03 ` 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-67121-2300-X0XCL8c8kf@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.