linux-kernel - Re: [PATCH] drm/i915: disable LVDS downclock by default

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]

Date:	Fri, 15 Jan 2010 18:21:40 +0200
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Thomas Meyer <thomas@...3r.de>
Cc:	Nick Bowler <nbowler@...conx.ca>, linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] drm/i915: disable LVDS downclock by default

Hi Thomas,

On Fri, 2010-01-15 at 17:14 +0100, Thomas Meyer wrote:
> Am Freitag, den 15.01.2010, 10:54 +0200 schrieb Pekka Enberg:
> 
> > So, any suggestions how I should proceed with figuring out the
> > "flashing" problem I still see with Jesse's patch? I can do a full git
> > bisect if it comes to that but it's going to be bit difficult to
> > determine if a commit is good or bad as there seem to be _two_
> > different problems both of which cause screen flickering.
> > 
> > Heelp!
> 
> Does it look like the video in this bug, see attached video in the bug
> report:
> 
> http://bugzilla.kernel.org/show_bug.cgi?id=14670

No, that looks more like the "shaking" problem that's fixed by Nick's
and Jesse's patches. The "flashing" bug I'm talking about looks like I'm
seeing an old frame or something that's partially garbled with normal
output. The bug also appears much more infrequently than what your video
shows.

        		Pekka

--
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/