linux-kernel - Re: Linux 2.6.33-rc4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <84144f021001141218pa3cd71co76165532618145a8@mail.gmail.com>
Date:	Thu, 14 Jan 2010 22:18:00 +0200
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Pekka Enberg <penberg@...helsinki.fi>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	airlied@...ux.ie
Subject: Re: Linux 2.6.33-rc4

On Thu, Jan 14, 2010 at 9:31 PM, Nick Bowler <nbowler@...iptictech.com> wrote:
> On 21:15 Thu 14 Jan     , Pekka Enberg wrote:
>> 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?
>
> Your symptoms sound identical to mine on my ThinkPad T500 laptop, as
> described in http://bugs.freedesktop.org/show_bug.cgi?id=25809.
>
> This is the patch I am currently applying locally which solves all my
> problems.
>
> diff --git a/drivers/gpu/drm/i915/intel_lvds.c b/drivers/gpu/drm/i915/intel_lvds.c
> index f4b4aa2..4fb5911 100644
> --- a/drivers/gpu/drm/i915/intel_lvds.c
> +++ b/drivers/gpu/drm/i915/intel_lvds.c
> @@ -914,7 +914,7 @@ static void intel_find_lvds_downclock(struct drm_device *dev,
>        mutex_unlock(&dev->mode_config.mutex);
>        if (temp_downclock < panel_fixed_mode->clock) {
>                /* We found the downclock for LVDS. */
> -               dev_priv->lvds_downclock_avail = 1;
> +               dev_priv->lvds_downclock_avail = 0;
>                dev_priv->lvds_downclock = temp_downclock;
>                DRM_DEBUG_KMS("LVDS downclock is found in EDID. "
>                                "Normal clock %dKhz, downclock %dKhz\n",

Should I try just this or combine it with Jesse's patch?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/