From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97022] Garbage in windows while running a game windowed
Date: Fri, 22 Jul 2016 19:43:34 +0000 [thread overview]
Message-ID: <bug-97022-502-pbM7mzp4NC@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97022-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1674 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97022
--- Comment #8 from Peter Mulholland <peter.mulholland@vpltd.com> ---
Created attachment 125261
--> https://bugs.freedesktop.org/attachment.cgi?id=125261&action=edit
Part of kern.log written during forcing a GPU reset
I've found that force resetting the GPU clears the corruption - using cat
/sys/kernel/debug/dri/0/radeon_gpu_reset
This does not take effect straight away however, I often have to kill Xorg
before it'll happen. There are some errors written to the kernel log - i have
attached those.
Here is lspci output for the card in case it's relevant:
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] [1002:683f] (prog-if
00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Cape Verde PRO [Radeon HD 7750/8740 /
R7 250E] [1043:0427]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 26
Region 0: Memory at d0000000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at fde80000 (64-bit, non-prefetchable) [size=256K]
Region 4: I/O ports at de00 [size=256]
[virtual] Expansion ROM at fde00000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
Kernel modules: radeon
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2679 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:[~2016-07-22 19:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 13:19 [Bug 97022] Garbage in windows while running a game windowed bugzilla-daemon
2016-07-21 13:58 ` bugzilla-daemon
2016-07-21 13:59 ` bugzilla-daemon
2016-07-22 1:56 ` bugzilla-daemon
2016-07-22 9:38 ` bugzilla-daemon
2016-07-22 15:39 ` bugzilla-daemon
2016-07-22 15:40 ` bugzilla-daemon
2016-07-22 15:41 ` bugzilla-daemon
2016-07-22 19:43 ` bugzilla-daemon [this message]
2016-07-30 10:21 ` bugzilla-daemon
2016-07-30 14:33 ` bugzilla-daemon
2016-07-31 20:49 ` bugzilla-daemon
2016-08-09 0:09 ` bugzilla-daemon
2016-08-09 12:02 ` 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-97022-502-pbM7mzp4NC@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