From: Hugh Dickins <hughd@google.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Arnd Bergmann <arnd@arndb.de>, Jiri Olsa <jolsa@redhat.com>,
Chris Clayton <chris2553@googlemail.com>,
Mario Kleiner <mario.kleiner@tuebingen.mpg.de>
Subject: Re: [PATCH] drm/i915,agp/intel: Do not clear stolen entries
Date: Fri, 28 Jan 2011 14:00:07 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.00.1101281347200.1759@sister.anvils> (raw)
In-Reply-To: <849307$b9dvii@azsmga001.ch.intel.com>
Sorry, this is now abount vblank or scanout rather than stolen entries.
On Mon, 24 Jan 2011, Chris Wilson wrote:
> On Sun, 23 Jan 2011 23:40:41 -0800 (PST), Hugh Dickins <hughd@google.com> wrote:
>
> > On this laptop I'm typing from (GM965 with KMS), I've had no trouble
> > getting X up; but when typing in one of the xterms, typed characters
> > often stop echoing, until I shift to a different window, whereupon
> > they appear. This condition cleared (for a while) by switching to
> > VESA fb console and back; no such problem observed on that console.
> >
> > Does that sound familiar? I have no evidence whatever that i915 is
> > to blame here. Several times I tried bisecting last week, but each
> > attempt ended up in a nonsensical place, because the effect does not
> > occur to order. So I'd sometimes mark a bisection point as good when
> > I guess it must actually have been bad. Perhaps it's a matter of
> > timing or an uninitialized variable. But while I'm here, worth asking
> > if that behaviour sounds like anything you might be responsible for?
>
> Sounds suspiciously like the batch buffer is not being dispatched and
> flushed to the scanout. A very similar bug was recently fixed for
> xf86-video-intel 2.14.0 which was causing deferred output.
I made a more patient bisection during the week, on x86_64 which
seemed more consistent than i386, and this time it converged sensibly:
to commit 0af7e4dff50454905092d468e91c1ef92e10e6b4
drm/i915: Add support for precise vblank timestamping (v2)
Which kindly notes in its commit message:
This code has been only tested on a HP-Mini Netbook with
Atom processor and Intel 945GME gpu. The codepath for
(IS_G4X(dev) || IS_GEN5(dev) || IS_GEN6(dev)) gpu's
has not been tested so far due to lack of hardware.
so not surprising that it doesn't work on GM965.
I'm now running with this silly revert:
--- a/drivers/gpu/drm/i915/i915_drv.c 2011-01-18 22:04:29.000000000 -0800
+++ b/drivers/gpu/drm/i915/i915_drv.c 2011-01-24 19:35:51.000000000 -0800
@@ -674,8 +674,8 @@ static struct drm_driver driver = {
.device_is_agp = i915_driver_device_is_agp,
.enable_vblank = i915_enable_vblank,
.disable_vblank = i915_disable_vblank,
- .get_vblank_timestamp = i915_get_vblank_timestamp,
- .get_scanout_position = i915_get_crtc_scanoutpos,
+ .get_vblank_timestamp = NULL /* i915_get_vblank_timestamp */,
+ .get_scanout_position = NULL /* i915_get_crtc_scanoutpos */,
.irq_preinstall = i915_driver_irq_preinstall,
.irq_postinstall = i915_driver_irq_postinstall,
.irq_uninstall = i915_driver_irq_uninstall,
which makes 2.6.38-rc usable; though I do believe that I've seen
the same issue (unflushed text) occur a couple of times since, much
too rare to bisect or get upset by, but indicative of some remaining bug.
Hugh
next prev parent reply other threads:[~2011-01-28 22:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 18:12 [BISECTED] agp/intel: revert "Remove confusion of stolen entries not stolen memory" Arnd Bergmann
2010-12-20 18:53 ` Chris Wilson
2010-12-20 19:47 ` Arnd Bergmann
2010-12-20 19:52 ` Chris Wilson
2010-12-20 20:52 ` Arnd Bergmann
2010-12-20 21:06 ` Chris Wilson
2010-12-20 21:54 ` Arnd Bergmann
2010-12-20 22:08 ` Dave Airlie
2011-01-20 23:24 ` Frederic Weisbecker
2011-01-21 10:58 ` [PATCH] drm/i915,agp/intel: Do not clear stolen entries Chris Wilson
2011-01-21 16:26 ` Jiri Olsa
2011-01-23 1:12 ` Frederic Weisbecker
2011-01-23 11:01 ` Chris Wilson
2011-01-23 17:59 ` Frederic Weisbecker
2011-01-24 7:40 ` Hugh Dickins
2011-01-24 10:10 ` Chris Wilson
2011-01-26 21:39 ` Arnd Bergmann
2011-01-28 22:00 ` Hugh Dickins [this message]
2011-01-29 2:59 ` Mario Kleiner
2011-01-30 0:28 ` Hugh Dickins
2011-01-30 4:13 ` Mario Kleiner
2011-01-30 9:55 ` Chris Wilson
2011-01-31 10:57 ` [PATCH] drm/i915: Suppress spurious vblank interrupts Chris Wilson
2011-02-01 17:34 ` Hugh Dickins
2011-02-01 17:46 ` Chris Wilson
2011-02-01 17:46 ` Jesse Barnes
2011-02-01 18:08 ` Jesse Barnes
2011-02-01 18:46 ` Hugh Dickins
2011-02-01 19:32 ` Jesse Barnes
2011-02-02 3:37 ` Hugh Dickins
2011-02-02 17:18 ` Jesse Barnes
2011-02-08 19:52 ` Hugh Dickins
2011-02-10 10:16 ` [PATCH] drm/i915/tv: Use polling rather than interrupt-based hotplug Chris Wilson
2011-02-11 6:34 ` Hugh Dickins
2011-02-11 18:21 ` [PATCH] drm/i915: Suppress spurious vblank interrupts Mario Kleiner
2011-02-14 17:41 ` Hugh Dickins
2011-06-18 4:40 ` Hugh Dickins
2011-01-30 8:52 ` [PATCH] drm/i915,agp/intel: Do not clear stolen entries Chris Clayton
2011-01-21 16:05 ` [BISECTED] agp/intel: revert "Remove confusion of stolen entries not stolen memory" Jiri Olsa
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=alpine.LSU.2.00.1101281347200.1759@sister.anvils \
--to=hughd@google.com \
--cc=arnd@arndb.de \
--cc=chris2553@googlemail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.kleiner@tuebingen.mpg.de \
/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®