On Thu, 3 Feb 2011 19:44:12 +0100 Nico Schottelius <nico-kernel-20110117@xxxxxxxxxxxxxxx> wrote: > Jesse Barnes [Thu, Feb 03, 2011 at 10:11:11AM -0800]: > > On Thu, 3 Feb 2011 00:31:29 +0100 (CET) > > "Rafael J. Wysocki" <rjw@xxxxxxx> wrote: > > > > > This message has been generated automatically as a part of a summary report > > > of recent regressions. > > > > > > The following bug entry is on the current list of known regressions > > > from 2.6.37. Please verify if it still should be listed and let the tracking team > > > know (either way). > > > > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=28102 > > > Subject : New display errors in 2.6.38-rc2-00175-g6fb1b30 > > > Submitter : Nico Schottelius <nico-kernel-20110117@xxxxxxxxxxxxxxx> > > > Date : 2011-01-28 20:29 (6 days old) > > > Message-ID : <20110128202905.GB3395@xxxxxxxxxxxxxxx> > > > References : http://marc.info/?l=linux-kernel&m=129624657425949&w=2 > > > > Does this also occur with the drm-intel-next branch? > > Didn't try this one, went back to 2.6.37-rc4-00292-g3c8cdf9 now. > > I thought about following the bisect way, should I go a different > one better? Bisect would also be fine. > > Do you have a picture of the corruption? > > Not yet, can do one next time. Though I found one that looks > very similar to my corruption: > > http://i759.photobucket.com/albums/xx239/ericfx1984/DSCF2469.jpg Interesting, ok. -- Jesse Barnes, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
