From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83331] New: radeon: Laptop panel out of sync after dpms standby/suspend/off
Date: Wed, 27 Aug 2014 12:11:57 +0000 [thread overview]
Message-ID: <bug-83331-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=83331
Bug ID: 83331
Summary: radeon: Laptop panel out of sync after dpms
standby/suspend/off
Product: Drivers
Version: 2.5
Kernel Version: 3.15.10
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: klaus.kusche@computerix.info
Regression: No
I've a problem on my laptop
(Dell Precision M6700 with AMD Cap Verde graphics, ChipID = 0x6825)
with the radeon driver (radeon-ucode-20140430):
Whenever the X server switches to dpms standby, suspend or off state
(it does so after 5 minutes when I'm on battery and idle)
and then back to dpms on, the internal panel is out of sync:
It is completely unreadable, flashes or shows strange moving patterns.
External displays are fine.
The problem is independent of the radeon powersave mode
(profile or dpm).
The only way to recover is either to power cycle
or to blindly type
xrandr --output eDP --off
xrandr --output eDP --auto
Switching from X to a text (framebuffer) VT does not help:
They are also corrupted.
When initializing radeon during boot, the kernel log says
radeon 0000:01:00.0: Invalid ROM contents
Could that be related?
Everything else looks fine.
When the problem happens, nothing is written to the kernel log.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-08-27 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 12:11 bugzilla-daemon [this message]
2014-08-27 13:30 ` [Bug 83331] radeon: Laptop panel out of sync after dpms standby/suspend/off bugzilla-daemon
2014-08-27 14:00 ` bugzilla-daemon
2014-08-27 14:00 ` bugzilla-daemon
2014-08-27 14:03 ` bugzilla-daemon
2014-09-14 9:43 ` bugzilla-daemon
2014-09-16 23:54 ` bugzilla-daemon
2014-09-17 5:56 ` bugzilla-daemon
2014-09-17 5:59 ` bugzilla-daemon
2014-10-04 12:05 ` 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-83331-2300@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.