On Mon, Apr 27, 2009 at 09:46:51AM -0700, Jesse Barnes wrote: > On Sun, 26 Apr 2009 11:46:26 +0200 (CEST) > "Rafael J. Wysocki" <rjw@xxxxxxx> wrote: > > > This message has been generated automatically as a part of a report > > of regressions introduced between 2.6.28 and 2.6.29. > > > > The following bug entry is on the current list of known regressions > > introduced between 2.6.28 and 2.6.29. Please verify if it still > > should be listed and let me know (either way). The problem is still here in 2.6.29-rc3. > I think we had a workaround for this (attached), but it sounds like > Robert has tracked down the root cause (search for "Broken vblanks on > Intel" on dri-devel@xxxxxxxxxxxxxxxxxxxxx). Will try to get the fix http://www.mail-archive.com/dri-devel@xxxxxxxxxxxxxxxxxxxxx/msg39370.html seems to be it. > into the Intel driver soon. Fortunately this doesn't seem to be biting > a lot of people (at least not that I've heard); I certainly have a hard > time reproducing it. The patch that was attached to Jesse's mail seems to resolve the problem... -- Sitsofe | http://sucs.org/~sits/ -- 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
