From: Chris Wilson <chris@chris-wilson.co.uk>
To: Dave Airlie <airlied@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@linux.ie>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
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: Tue, 11 Jan 2011 10:58:39 +0000 [thread overview]
Message-ID: <b7da2f$q3onue@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <AANLkTi=TSWj4TPVbPVxY6BNcnvUA24buZggjCy2xu_83@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2543 bytes --]
On Tue, 11 Jan 2011 14:51:40 +1000, Dave Airlie <airlied@gmail.com> wrote:
> On Tue, Jan 11, 2011 at 2:48 PM, 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?
>
> I've also noticed Chris has some more patches in drm-intel-next I
> haven't got in this pull request.
>
> I don't think he's sent me a pull request though so not telling how
> stable they are.
Yes, there are a few pending fixes. I've been waiting on feedback from
testing for some more before asking for a pull. In part because we have
some more eDP fixes, courtesy of Jesse, that makes everyone but Jim Getty
happy.
However, I've not seen anything like this so I doubt that d-i-n contains
the fix.
Dave, is yours related to the DMAR errors that is plaguing your systems?
Linus, is anything else kicked off upon powersaving? A screen saver or is
it just the blanking that triggers the mess?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-11 10:58 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 22:59 Dave Airlie
2011-01-11 4:16 ` Linus Torvalds
2011-01-11 4:48 ` Dave Airlie
2011-01-11 4:51 ` Dave Airlie
2011-01-11 10:58 ` Chris Wilson [this message]
2011-01-11 6:06 ` Jesse Barnes
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: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:54 ` Dave Airlie
2011-01-11 23:20 ` Christian Borntraeger
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 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-13 17:55 ` James Simmons
2011-01-13 19:53 ` 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 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='b7da2f$q3onue@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=jbarnes@virtuousgeek.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®