[git pull] drm for rc1
airlied at gmail.com
Mon Jan 10 22:28:08 PST 2011
On Tue, Jan 11, 2011 at 4:06 PM, Jesse Barnes <jbarnes at virtuousgeek.org> wrote:
> "Dave Airlie" <airlied at gmail.com> wrote:
>>On Tue, Jan 11, 2011 at 2:16 PM, Linus Torvalds
>><torvalds at linux-foundation.org> wrote:
>>> On Mon, Jan 10, 2011 at 2:59 PM, Dave Airlie <airlied at linux.ie>
>>>> core/drivers: add support for high precision vblank timestamps
>>>> radeon: pageflipping support, Gen2 PCIE support
>>>> nouveau: reworked VRAM and VM support
>>>> intel: better ILK/SNB powersaving support, Full GTT support
>>> Lowlights: it's broken.
>>> I get millions of messages like:
>>> [ 8482.000414] [drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck
>>> timer elapsed... render ring idle [waiting on 30938, at 30938],
>>> [ 8485.918124] [drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck
>>> timer elapsed... render ring idle [waiting on 31068, at 31068],
>>> [ 8487.926963] [drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck
>>> timer elapsed... render ring idle [waiting on 31129, at 31129],
>>> and everything is very choppy. I assume it's the power saving thing
>>> that broke again, but that's just a total random guess, I have
>>> to actually back that up with.
>>> It worked fine after boot, but those problems began at 8287.139375
>>> (about two hours after boot - it may have coincided with screen
>>> but who knows?) and have been happening constantly since. The
>>> is not really usable, I'm writing this with annoying 2-second pauses
>>> every once in a while.
>>Okay I'll try and reproduce and curse Chris and Jesse, does booting
>>i915.powersave=0 help any?
> Arg. It's been ok on my ILK systems, but Chris has found some issues with out watermarking code iirc; apparently we're underflowing the display FIFO, causing all sorts of trouble. If it works before the pull of Dave's tree, can you bisect?
I think he'd fixed them in the tree I pulled locally to test, I'm
guessing this might be that we are running the Fedora userspace driver
and you guys are all on master or something, which would mean some ABI
guarantee got busted.
I'm going to try a local test upgrade to 2.14.0 just to see.
More information about the dri-devel