From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 196563] New: Garbled graphics after resume on an R100-based card
Date: Wed, 02 Aug 2017 07:34:09 +0000 [thread overview]
Message-ID: <bug-196563-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=196563
Bug ID: 196563
Summary: Garbled graphics after resume on an R100-based card
Product: Drivers
Version: 2.5
Kernel Version: 4.11.0-2-686-pae (Debian sid)
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: felix.von.s@posteo.de
Regression: No
When I suspend and then resume my laptop with R100-based graphics, the display
becomes garbled. A single scanline from the video memory is stretched over the
entire height of the screen; this is usually the scanline containing the caret.
Under X11, one can observe the mouse pointer sprite being corrupted as well.
When switching VTs, flashes of the correct, 'intended' screen contents can be
sometimes seen, but the screen instantly reverts to this single stretched
scanline just described.
The issue can be readily worked around via the usual 'vbetool vbestate' hack;
although even then the display contents can appear incorrect after resume, as
if other programs' framebuffers were pasted onto the screen. Moreover, if the
restore part doesn't run soon enough after resuming, the restored screen
becomes glitched with randomly lit pixels. The glitching is more severe the
more time passes between resuming and restoring VBE state; it is as if the
video RAM wasn't being refreshed correctly until the VBE state is restored.
Thus, best results are achieved by storing the VBE state on a tmpfs. But in any
case, it's nothing a temporary VT switch can't fix.
--
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
next reply other threads:[~2017-08-02 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 7:34 bugzilla-daemon [this message]
2017-08-02 7:37 ` [Bug 196563] Garbled graphics after resume on an R100-based card bugzilla-daemon
2017-08-02 7:38 ` bugzilla-daemon
2017-08-02 7:39 ` bugzilla-daemon
2017-08-02 7:40 ` bugzilla-daemon
2017-08-02 7:41 ` bugzilla-daemon
2017-08-02 9:19 ` 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-196563-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.