From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101691] gfx corruption on windowed 3d-apps running on dGPU
Date: Fri, 25 Aug 2017 02:46:49 +0000 [thread overview]
Message-ID: <bug-101691-502-6YfxXxcNME@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101691-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 828 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101691
--- Comment #34 from Ben Widawsky <ben@bwidawsk.net> ---
Just some thoughts...
The corruption are x-tiled cachelines, looks like stale ones. I don't know what
the vertical lines are. It looks to me like the memory is just misbehaving. I
wonder if when you plug in the machine if BIOS tries to crank up DDR, or
Graphics voltage. Is there some BIOS setting or update to tweak what happens on
AC?
Is this desktop environment using sprite planes? If the compositor is using all
one plane (which I think is likely), and display was at fault, everything would
be corrupt.
So please see if there is anything that can be done in BIOS to tell it to not
behave differently when on AC.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1631 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-08-25 2:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-101691-502@http.bugs.freedesktop.org/>
2017-07-29 6:56 ` [Bug 101691] [KBL] gfx corruption on windowed 3d-apps running on dGPU bugzilla-daemon
2017-07-31 3:20 ` bugzilla-daemon
2017-08-16 11:03 ` bugzilla-daemon
2017-08-16 11:14 ` bugzilla-daemon
2017-08-16 11:14 ` bugzilla-daemon
2017-08-16 12:58 ` bugzilla-daemon
2017-08-17 1:51 ` bugzilla-daemon
2017-08-17 2:00 ` bugzilla-daemon
2017-08-18 15:48 ` bugzilla-daemon
2017-08-18 17:36 ` bugzilla-daemon
2017-08-23 7:49 ` bugzilla-daemon
2017-08-23 8:37 ` bugzilla-daemon
2017-08-23 9:02 ` bugzilla-daemon
2017-08-23 9:03 ` bugzilla-daemon
2017-08-23 9:03 ` bugzilla-daemon
2017-08-23 14:29 ` bugzilla-daemon
2017-08-23 14:29 ` bugzilla-daemon
2017-08-24 3:49 ` bugzilla-daemon
2017-08-24 14:35 ` [Bug 101691] " bugzilla-daemon
2017-08-25 2:46 ` bugzilla-daemon [this message]
2017-08-25 8:48 ` bugzilla-daemon
2017-08-25 9:33 ` bugzilla-daemon
2017-08-28 8:41 ` bugzilla-daemon
2017-08-29 8:38 ` bugzilla-daemon
2017-08-29 8:39 ` bugzilla-daemon
2017-08-30 7:08 ` bugzilla-daemon
2017-08-30 7:35 ` bugzilla-daemon
2017-10-17 20:52 ` bugzilla-daemon
2017-10-17 20:52 ` bugzilla-daemon
2017-10-17 21:42 ` bugzilla-daemon
2017-10-18 1:47 ` bugzilla-daemon
2017-10-18 19:19 ` bugzilla-daemon
2017-10-18 22:07 ` bugzilla-daemon
2017-10-18 22:08 ` bugzilla-daemon
2017-10-19 8:39 ` bugzilla-daemon
2017-10-19 17:34 ` bugzilla-daemon
2017-10-19 18:56 ` 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-101691-502-6YfxXxcNME@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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