From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Dave Airlie <airlied@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@linux.ie>,
Chris Wilson <chris@chris-wilson.co.uk>,
Eric Anholt <eric@anholt.net>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm for rc1
Date: Mon, 10 Jan 2011 22:06:29 -0800 [thread overview]
Message-ID: <0aea052d-70ff-41ea-8776-c6d974c10337@email.android.com> (raw)
In-Reply-To: <AANLkTim5oVZqMBtan5_TMOxaWbqkF=aDcBYFNYy55kt_@mail.gmail.com>
"Dave Airlie" <airlied@gmail.com> wrote:
>On Tue, Jan 11, 2011 at 2:16 PM, Linus Torvalds
><torvalds@linux-foundation.org> wrote:
>> On Mon, Jan 10, 2011 at 2:59 PM, Dave Airlie <airlied@linux.ie>
>wrote:
>>> Highlights:
>>> 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],
>missed
>> IRQ?
>> [ 8485.918124] [drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck
>> timer elapsed... render ring idle [waiting on 31068, at 31068],
>missed
>> IRQ?
>> [ 8487.926963] [drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck
>> timer elapsed... render ring idle [waiting on 31129, at 31129],
>missed
>> IRQ?
>> ...
>>
>> 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
>nothing
>> 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
>saver,
>> but who knows?) and have been happening constantly since. The
>machine
>> 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
>with
>i915.powersave=0 help any?
>
>Dave.
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?
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
WARNING: multiple messages have this Message-ID (diff)
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Dave Airlie <airlied@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm for rc1
Date: Mon, 10 Jan 2011 22:06:29 -0800 [thread overview]
Message-ID: <0aea052d-70ff-41ea-8776-c6d974c10337@email.android.com> (raw)
In-Reply-To: <AANLkTim5oVZqMBtan5_TMOxaWbqkF=aDcBYFNYy55kt_@mail.gmail.com>
"Dave Airlie" <airlied@gmail.com> wrote:
>On Tue, Jan 11, 2011 at 2:16 PM, Linus Torvalds
><torvalds@linux-foundation.org> wrote:
>> On Mon, Jan 10, 2011 at 2:59 PM, Dave Airlie <airlied@linux.ie>
>wrote:
>>> Highlights:
>>> 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],
>missed
>> IRQ?
>> [ 8485.918124] [drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck
>> timer elapsed... render ring idle [waiting on 31068, at 31068],
>missed
>> IRQ?
>> [ 8487.926963] [drm:i915_hangcheck_ring_idle] *ERROR* Hangcheck
>> timer elapsed... render ring idle [waiting on 31129, at 31129],
>missed
>> IRQ?
>> ...
>>
>> 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
>nothing
>> 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
>saver,
>> but who knows?) and have been happening constantly since. The
>machine
>> 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
>with
>i915.powersave=0 help any?
>
>Dave.
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?
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2011-01-11 6:06 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 22:59 [git pull] drm for rc1 Dave Airlie
2011-01-11 4:16 ` Linus Torvalds
2011-01-11 4:48 ` Dave Airlie
2011-01-11 4:48 ` Dave Airlie
2011-01-11 4:51 ` Dave Airlie
2011-01-11 10:58 ` Chris Wilson
2011-01-11 10:58 ` Chris Wilson
2011-01-11 6:06 ` Jesse Barnes [this message]
2011-01-11 6:06 ` Jesse Barnes
2011-01-11 6:28 ` Dave Airlie
2011-01-11 6:28 ` Dave Airlie
2011-01-11 7:04 ` Dave Airlie
2011-01-11 10:35 ` Anca Emanuel
2011-01-11 13:33 ` Pavel Machek
2011-01-11 14:14 ` Chris Wilson
2011-02-23 18:53 ` Pavel Machek
2011-01-11 16:01 ` Linus Torvalds
2011-01-11 16:11 ` Anca Emanuel
2011-01-11 16:25 ` Anca Emanuel
2011-01-11 17:58 ` Anca Emanuel
2011-01-11 19:00 ` Linus Torvalds
2011-01-11 19:00 ` Linus Torvalds
2011-01-11 19:12 ` Jesse Barnes
2011-01-11 19:25 ` Linus Torvalds
2011-01-11 19:45 ` Jesse Barnes
2011-01-11 19:53 ` Linus Torvalds
2011-01-11 20:05 ` Chris Wilson
2011-01-11 22:16 ` Linus Torvalds
2011-01-11 22:31 ` Chris Wilson
2011-01-11 23:01 ` Linus Torvalds
2011-01-12 1:36 ` Linus Torvalds
2011-01-12 1:36 ` Linus Torvalds
2011-01-12 1:54 ` Dave Airlie
2011-01-11 23:20 ` Christian Borntraeger
2011-01-11 23:28 ` Linus Torvalds
2011-01-11 23:28 ` Linus Torvalds
2011-01-12 11:21 ` Christian Borntraeger
2011-01-12 12:49 ` James Simmons
2011-01-12 13:03 ` Christian Borntraeger
2011-01-12 13:32 ` James Simmons
2011-01-12 13:45 ` Christian Borntraeger
2011-01-12 15:55 ` Linus Torvalds
2011-01-12 16:39 ` James Simmons
2011-01-12 13:36 ` Anca Emanuel
2011-01-12 13:45 ` James Simmons
2011-01-12 13:55 ` Anca Emanuel
2011-01-12 13:55 ` Anca Emanuel
2011-01-12 14:35 ` Christian Borntraeger
2011-01-12 16:53 ` James Simmons
2011-01-12 15:13 ` Anca Emanuel
2011-01-12 15:25 ` Anca Emanuel
2011-01-12 15:40 ` James Simmons
2011-01-12 15:55 ` Anca Emanuel
2011-01-12 15:55 ` Anca Emanuel
2011-01-13 17:55 ` James Simmons
2011-01-13 19:53 ` Anca Emanuel
2011-01-14 16:29 ` Anca Emanuel
2011-01-14 16:29 ` Anca Emanuel
2011-01-14 16:38 ` James Simmons
2011-01-14 18:22 ` Anca Emanuel
2011-01-14 18:26 ` James Simmons
2011-01-14 18:40 ` Anca Emanuel
2011-01-14 18:40 ` Anca Emanuel
2011-01-14 19:02 ` Anca Emanuel
2011-02-19 15:14 ` Alex Riesen
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=0aea052d-70ff-41ea-8776-c6d974c10337@email.android.com \
--to=jbarnes@virtuousgeek.org \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.