Re: 2.6.33-rc2: Reported regressions from 2.6.32

From: Michael S. Tsirkin
Date: Mon Jan 18 2010 - 06:29:41 EST

On Sun, Jan 17, 2010 at 07:23:35PM +0200, Pekka Enberg wrote:
> On Sun, Jan 17, 2010 at 6:43 PM, Pekka Enberg <penberg@xxxxxxxxxxxxxx> wrote:
> > Hi Florian,
> >
> > (Please don't trim the cc list.)
> >
> > On Sun, Jan 17, 2010 at 5:17 PM, Florian Mickler <florian@xxxxxxxxxxx> wrote:
> >> 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?
> >
> > Like I said, don't read too much into the results but the current
> > situation looks like the regression happened _after_ 2.6.32 but before
> > any of the DRM code was merged to 2.6.33-rc1. I don't think that makes
> > much sense which is why I'm back to testing 2.6.32 more to see if the
> > bug is there already but just harder to trigger for whatever reason.
> OK, confirmed. I can see the "flashing" bug with 2.6.32 as well. It
> just takes more time to trigger than in 2.6.33-rc1. I am going back to
> test 2.6.31 now.

Well, I've been using 2.6.32 day to day since it came out and never saw
this bug there. What do you do to trigger this bug?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at