[PATCH] Revert "drm/radeon: Try evicting from CPU accessible to inaccessible VRAM first"
michel at daenzer.net
Tue Mar 28 09:36:47 UTC 2017
On 28/03/17 05:24 PM, Julien Isorce wrote:
> Hi Michel,
> About the hard lockup, I noticed that I cannot have it with the
> following conditions:
> 1. soft lockup fix (the 0->i change which avoids infinite loop)
> 2. Your suggestion: (!(rbo->flags & RADEON_GEM_CPU_ACCESS)
> 3. radeon.gartsize=512 radeon.vramlimit=1024 (any other values above do
> not help, for example (1024, 1024) or (1024, 2048))
> Without 1 and 2, but with 3, our test reproduces the soft lockup (just
> discovered few days ago).
> Without 3 (and with or without 1., 2.), our test reproduces the hard
> lockup which one does not give any info in kern.log (sometimes some NUL
> ^@ characters but not always).
What exactly does "hard lockup" mean? What are the symptoms?
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
More information about the amd-gfx