From: Andy Lutomirski <luto@myrealbox.com>
To: Emmanuel Benisty <benisty.e@gmail.com>
Cc: linux-kernel@vger.kernel.org, tiwai@suse.de,
jbarnes@virtuousgeek.org, intel-gfx@lists.freedesktop.org
Subject: Re: 2.6.31 -> 2.6.32 Sound and video regressions
Date: Sat, 05 Dec 2009 09:34:32 -0500 [thread overview]
Message-ID: <4B1A6F78.8010408@myrealbox.com> (raw)
In-Reply-To: <c1f41c620912042148n7d3f6f29h713a2d44369a5810@mail.gmail.com>
Emmanuel Benisty wrote:
> Hi,
>
> I hope I didn't miss something but given the traffic of LKML, that
> could have happened.
>
> 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.
> Xorg.0.log is attached.
> (I've uploaded an utterly crappy mobile phone video if needed but I
> doubt this could be of any help, anyway, it's here
> http://omploader.org/vMngzcA/Xorg.tar.bz2 )
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. (cc added)
--Andy
next prev parent reply other threads:[~2009-12-05 14: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 [this message]
2009-12-05 14:42 ` Emmanuel Benisty
2009-12-05 23:44 ` Darren Salt
2009-12-07 1:32 ` Jesse Barnes
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=4B1A6F78.8010408@myrealbox.com \
--to=luto@myrealbox.com \
--cc=benisty.e@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.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
Powered by JetHome