mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Darren Salt <linux@youmustbejoking.demon.co.uk>
Cc: linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
	luto@myrealbox.com, benisty.e@gmail.com
Subject: Re: 2.6.31 -> 2.6.32 Sound and video regressions
Date: Sun, 6 Dec 2009 17:32:22 -0800	[thread overview]
Message-ID: <20091206173222.4c2d5aaa@jbarnes-piketon> (raw)
In-Reply-To: <50CA8D92EC%linux@youmustbejoking.demon.co.uk>

On Sat, 05 Dec 2009 23:44:55 +0000
Darren Salt <linux@youmustbejoking.demon.co.uk> wrote:

> I demand that Andy Lutomirski may or may not have written...
> 
> > Emmanuel Benisty wrote:
> [snip]
> >> I just wanted to report 2 regressions I am having now with 2.6.32.
> >> Video
> >> Screen is flickering/glitching like crazy in X. It happens whether
> >> randomly or when conky is refreshed, when the mouse cursor moves
> >> and like hell when a page is loading in the browser. Not so easy to
> >> describe this issue.
> [snip]
> 
> > That sounds like FIFO underruns, which (I think) were introduced
> > when self-refresh was enabled but should have been fixed. I
> > personally have no clue how to fix them, but if you told the Intel
> > people what kind of chip you have (lspci output), they can probably
> > fix it.
> 
> It also sounds like what I'm seeing on my EeePC 901. It only happens
> after resume, which makes STR a little less than useful; the display
> will, sooner or later, show a single colour (which is, presumably,
> the result of a display engine hang, as described in the comment
> immediately before intel_calculate_wm) and, seemingly, be stuck like
> that until power-off or reboot.
> 
> Whether it *is* the same problem, I couldn't say.
> 
> Needless to say, this problem goes away if I disable KMS.

Arg, there are a few reports of this now, but I haven't been able to
reproduce it.  I'll try harder...  (FYI the upstream
bugs.freedesktop.org # for it is 24314).

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2009-12-07  1:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-05  5:48 Emmanuel Benisty
2009-12-05  6:05 ` Emmanuel Benisty
2009-12-05 14:34 ` Andy Lutomirski
2009-12-05 14:42   ` Emmanuel Benisty
2009-12-05 23:44   ` Darren Salt
2009-12-07  1:32     ` Jesse Barnes [this message]
2009-12-07  3:52       ` Emmanuel Benisty
2009-12-07 13:38         ` Emmanuel Benisty
2009-12-08 13:20           ` Emmanuel Benisty
2009-12-10 17:54             ` Jesse Barnes
2009-12-11  1:49               ` Emmanuel Benisty
2009-12-17 19:05               ` Jesse Barnes
2009-12-18 17:10                 ` Emmanuel Benisty
2009-12-18 17:16                   ` Jesse Barnes
2009-12-05 14:53 ` Takashi Iwai
2009-12-05 15:07   ` Emmanuel Benisty

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=20091206173222.4c2d5aaa@jbarnes-piketon \
    --to=jbarnes@virtuousgeek.org \
    --cc=benisty.e@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@youmustbejoking.demon.co.uk \
    --cc=luto@myrealbox.com \
    /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®