On Monday, August 30, 2010, Peter Zijlstra wrote: > On Mon, 2010-08-30 at 01:13 +0200, Rafael J. Wysocki wrote: > > This message has been generated automatically as a part of a report > > of regressions introduced between 2.6.34 and 2.6.35. > > > > The following bug entry is on the current list of known regressions > > introduced between 2.6.34 and 2.6.35. 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=16399 > > Subject : perf failed with kernel 2.6.35-rc > > Submitter : Zhang, Yanmin <yanmin_zhang@xxxxxxxxxxxxxxx> > > Date : 2010-07-13 8:14 (48 days old) > > First-Bad-Commit: http://git.kernel.org/linus/1ac62cfff252fb668405ef3398a1fa7f4a0d6d15 > > Message-ID : <1279008849.2096.913.camel@xxxxxxxxxxxxxxxxxxxx> > > References : http://marc.info/?l=linux-kernel&m=127900880212470&w=2 > > > > > > Should be fixed by: > > commit 351af0725e5222e35741011d1ea62215c1ed06db > Author: Zhang, Yanmin <yanmin_zhang@xxxxxxxxxxxxxxx> > Date: Fri Aug 6 13:39:08 2010 +0800 > > perf, x86: Fix Intel-nhm PMU programming errata workaround > > Fix the Errata AAK100/AAP53/BD53 workaround, the officialy documented > workaround we implemented in: > > 11164cd: perf, x86: Add Nehelem PMU programming errata workaround > > doesn't actually work fully and causes a stuck PMU state > under load and non-functioning perf profiling. > > A functional workaround was found by trial & error. > > Affects all Nehalem-class Intel PMUs. > > Signed-off-by: Zhang Yanmin <yanmin_zhang@xxxxxxxxxxxxxxx> > Signed-off-by: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx> > LKML-Reference: <1281073148.2125.63.camel@xxxxxxxxxxxxxxxxxxxx> > Cc: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx> > Cc: "H. Peter Anvin" <hpa@xxxxxxxxx> > Cc: <stable@xxxxxxxxxx> # .35.x > Signed-off-by: Ingo Molnar <mingo@xxxxxxx> Thanks, closed. Rafael -- 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