mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	airlied@linux.ie
Subject: Re: Linux 2.6.33-rc4
Date: Thu, 14 Jan 2010 11:26:18 -0800	[thread overview]
Message-ID: <20100114112618.4304f966@jbarnes-piketon> (raw)
In-Reply-To: <4B4F6D5F.10008@cs.helsinki.fi>

On Thu, 14 Jan 2010 21:15:43 +0200
Pekka Enberg <penberg@cs.helsinki.fi> wrote:

> Jesse Barnes wrote:
> > On Wed, 13 Jan 2010 23:50:52 +0200
> > Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> > 
> >> Jesse Barnes wrote:
> >>> On Wed, 13 Jan 2010 23:03:00 +0200
> >>> Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> >>>
> >>>> On Wed, Jan 13, 2010 at 7:44 AM, Linus Torvalds
> >>>> <torvalds@linux-foundation.org> wrote:
> >>>>> Hmm. Odd release. Something like 40% of the patches are in DRM
> >>>>> (mostly nouveau and radeon, both staging, so it's a bit less
> >>>>> scary than it sounds. But there's a noticeable i915 component
> >>>>> too). That's all pretty unusual, afaik.
> >>>> 2.6.33-rc4 still suffers from an annoying screen flicker with
> >>>> i915 and KMS on my machine. I *think* it started with 2.6.33-rc1
> >>>> but I haven't had the time to dig deeper.
> >>> Does this patch fix it?  If so I'll queue something like this up
> >>> for -rc5.
> >> Yes, it does. Thanks!
> > 
> > Great, thanks for testing.  I'll send Eric a patch to disable this
> > feature more properly.
> 
> OK, I think I am seeing a different kind of flicker now. It doesn't 
> happen anywhere as often as before (which is probably why I missed it 
> last night). The flicker is more like a flash of some other window 
> whereas the flicker before used to "shake" the screen.
> 
> Does this ring a bell?

Sounds separate from the other issue.  Would it be possible to capture
a video of the flicker?  If it's a FIFO underrun, you may be able to
trigger it by running apps in the background that use a lot of memory
bandwidth.

If it's FBC related, it should occur in 15s intervals or so, depending
on whether you have other stuff going on (again would be memory
bandwidth related).

Please file a bug at bugs.freedesktop.org against drm/intel with what
you find.

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2010-01-14 19:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13  5:44 Linus Torvalds
2010-01-13 20:21 ` Linux 2.6.33-rc4, boot regression still exists Gene Heskett
2010-01-13 21:03 ` Linux 2.6.33-rc4 Pekka Enberg
2010-01-13 21:33   ` Jesse Barnes
2010-01-13 21:50     ` Pekka Enberg
2010-01-14  0:55       ` Jesse Barnes
2010-01-14 19:15         ` Pekka Enberg
2010-01-14 19:26           ` Jesse Barnes [this message]
2010-01-14 19:31           ` Nick Bowler
2010-01-14 20:18             ` Pekka Enberg
2010-01-14 20:28               ` Nick Bowler
2010-01-14 20:48                 ` [PATCH] drm/i915: disable LVDS downclock by default Jesse Barnes
2010-01-14 20:58                   ` [Intel-gfx] " Peter Clifton
2010-01-14 21:05                     ` Linus Torvalds
2010-01-14 21:21                       ` Jesse Barnes
2010-01-14 21:16                     ` Nick Bowler
2010-01-14 21:27                       ` Jesse Barnes
2010-01-14 21:25                   ` Pekka Enberg
2010-01-14 21:51                     ` Jesse Barnes
2010-01-15  1:15                   ` Nick Bowler
2010-01-15  8:54                     ` Pekka Enberg
2010-01-15 16:14                       ` Thomas Meyer
2010-01-15 16:21                         ` Pekka Enberg
2010-01-15 16:32                         ` Nick Bowler
2010-01-15 16:46                           ` Linus Torvalds

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=20100114112618.4304f966@jbarnes-piketon \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@linux.ie \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --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®