To possibly clear up any confusion - the i915 driver will generate
uevents (see the tool's udev listener for an example). These events are
signs of parity errors in a specific part of the GPU's L3 cache. The
tool itself allows remapping these bad locations.
At a high level, it could work like:
1.
(In reply to comment #19)
On Wed, Jun 26, 2013 at 11:04:43PM +, bugzilla-dae...@freedesktop.org
wrote:
https://bugs.freedesktop.org/show_bug.cgi?id=64073
--- Comment #18 from Ben Widawsky b...@bwidawsk.net ---
If someone can reproduce this, can they read back register 0x20f4?
(In reply to comment #17)
I can confirm that I did see strange white corruption when playing the
game, but I thought it was unrelated or an application error.
Unfortunately, I don't have access to the hardware anymore so I cannot
further test anything. However, given that the hangs happened
This looks weird to me:
0x5a58: 0x1101: MI_LOAD_REGISTER_IMM
0x5a5c: 0x00012044:dword 1
0x5a60: 0x0043b625:dword 2
0x5a64: 0x1101: MI_LOAD_REGISTER_IMM
0x5a68: 0x00022040:dword 1
0x5a6c: 0x0043b625:dword 2
0x5a70:
(In reply to comment #27)
The only interesting patch I can suggest atm is
commit 31643d54a739382626c27c0f2a12b3bbc22d1a38
Author: Ben Widawsky b...@bwidawsk.net
Date: Wed Sep 26 10:34:01 2012 -0700
drm/i915: Workaround to bump rc6 voltage to 450
BIOS should be
5 matches
Mail list logo
