On Mon, Oct 15, 2012 at 5:11 PM, Greg KH gre...@linuxfoundation.org wrote:
On Mon, Oct 15, 2012 at 10:11:22AM +0200, Daniel Vetter wrote:
Hi Gregstable-team,
The below patch papers over a graphics corruption issue in 3.5/3.6. The
regression happened due to pwrite tunings in 3.5, which made
Hi Gregstable-team,
The below patch papers over a graphics corruption issue in 3.5/3.6. The
regression happened due to pwrite tunings in 3.5, which made cpu relocations
much more likely.
The issue seems to have disappeared in 3.7-rc1, but it takes a few days to test
a patch, so we haven't
On Mon, Oct 15, 2012 at 10:11:22AM +0200, Daniel Vetter wrote:
Hi Gregstable-team,
The below patch papers over a graphics corruption issue in 3.5/3.6. The
regression happened due to pwrite tunings in 3.5, which made cpu relocations
much more likely.
The issue seems to have disappeared in
On Mon, Oct 15, 2012 at 5:11 PM, Greg KH gre...@linuxfoundation.org wrote:
On Mon, Oct 15, 2012 at 10:11:22AM +0200, Daniel Vetter wrote:
Hi Gregstable-team,
The below patch papers over a graphics corruption issue in 3.5/3.6. The
regression happened due to pwrite tunings in 3.5, which made
On Mon, Oct 15, 2012 at 07:16:26PM +0200, Daniel Vetter wrote:
On Mon, Oct 15, 2012 at 5:11 PM, Greg KH gre...@linuxfoundation.org wrote:
On Mon, Oct 15, 2012 at 10:11:22AM +0200, Daniel Vetter wrote:
Hi Gregstable-team,
The below patch papers over a graphics corruption issue in 3.5/3.6.
They seem to be implicated in render corruptions. And up to now no one
really seems to understand the issue, so let's just disable them for
now. Most of the machines exhibiting this issue have only a 128 gtt
mmio window, so increased pressure on the mappable part (and so higher
chance for cpu
On Wed, 10 Oct 2012 10:06:40 +0200, Daniel Vetter daniel.vet...@ffwll.ch
wrote:
They seem to be implicated in render corruptions. And up to now no one
really seems to understand the issue, so let's just disable them for
now. Most of the machines exhibiting this issue have only a 128 gtt
mmio
