From: Emmanuel Benisty <benisty.e@gmail.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Darren Salt <linux@youmustbejoking.demon.co.uk>,
linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
luto@myrealbox.com, eric@anholt.net
Subject: Re: 2.6.31 -> 2.6.32 Sound and video regressions
Date: Tue, 8 Dec 2009 20:20:07 +0700 [thread overview]
Message-ID: <c1f41c620912080520o7e0a69bdg7b885b4a17c6dbc@mail.gmail.com> (raw)
In-Reply-To: <c1f41c620912070538y4f865cechf21d2802ab237510@mail.gmail.com>
On Mon, Dec 7, 2009 at 8:38 PM, Emmanuel Benisty <benisty.e@gmail.com> wrote:
> On Mon, Dec 7, 2009 at 10:52 AM, Emmanuel Benisty <benisty.e@gmail.com> wrote:
>> On Mon, Dec 7, 2009 at 8:32 AM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>>> 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).
>>
>> It *seems* that we are facing two different issues here (I don't even
>> use S2R and the problem is there since the very first second I start
>> X). Anyway, I have bisected the problem on my box, it turns out to be
>> this one:
>>
>> drm/i915: Fix render reclock availability detection
>>
>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=181a5336d6cc836f05507410d66988c483ad0154
>>
> So, I have reverted this commit and rebuilt 2.6.32. It completely
> solved the issue described in my first post.
>
just FTR, it looks like I'm not alone:
http://forums.gentoo.org/viewtopic-p-6087556.html#6087556
next prev parent reply other threads:[~2009-12-08 13:20 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
2009-12-07 3:52 ` Emmanuel Benisty
2009-12-07 13:38 ` Emmanuel Benisty
2009-12-08 13:20 ` Emmanuel Benisty [this message]
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=c1f41c620912080520o7e0a69bdg7b885b4a17c6dbc@mail.gmail.com \
--to=benisty.e@gmail.com \
--cc=eric@anholt.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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
Powered by JetHome