Re: 2.6.33-rc2: Reported regressions from 2.6.32
From: Florian Mickler
Date: Sun Jan 17 2010 - 10:18:13 EST
On Sun, 17 Jan 2010 16:18:39 +0200
Pekka Enberg <penberg@xxxxxxxxxxxxxx> wrote:
> On Sun, Jan 17, 2010 at 2:32 PM, Michael S. Tsirkin
> <m.s.tsirkin@xxxxxxxxx> wrote:
> > On Sat, Jan 16, 2010 at 02:04:07PM -0800, Linus Torvalds wrote:
> >> On Sat, 16 Jan 2010, Rafael J. Wysocki wrote:
> >> >
> >> > > Immediately upon startup, screen is flickering (becomes
> >> > > lighter and darker again). The problem occurs with kernels
> >> > > 2.6.33-rc1 to 2.6.33-rc4, but not with kernel 2.6.32 and below.
> >> >
> >> > We've already had several reports like this already.
> >> >
> >> > Care to review the bugs linked to http://bugzilla.kernel.org/show_bug.cgi?id=14885
> >> > and check if none of them matches the problem you describe?
> >> I suspect that should be fixed by commit 33814341f22 ("drm/i915: disable
> >> LVDS downclock by default") that got merged today.
> >> So try current -git.
> >> Linus
> > Tested with 6ccf80eb15ccaca4d3f1ab5162b9ded5eecd9971, still get
> > the flickering effect. so 33814341f22 does not seem to help.
> Yeah, me too which is why I am doing a git bisect here. What's strange
> about it is that the first bisection point seems to suggest that the
> regression happened _before_ the DRM merge to 2.6.33-rc1. I guess it's
> possible that the bug is already in 2.6.32 but I've yet to see the
> flickering effect. Oh well, back to bisect...
on which side of the merge? linus or drm?
i.e. it is to be expected to be before the merge, (but on the drm side)
so don't get confused... or did i misunderstood the situation?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/