On Sun, 2010-12-19 at 13:50 +0100, Rafael J. Wysocki wrote: > This message has been generated automatically as a part of a report > of regressions introduced between 2.6.35 and 2.6.36. > > The following bug entry is on the current list of known regressions > introduced between 2.6.35 and 2.6.36. 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=20232 > Subject : kworker consumes ~100% CPU on HP Elitebook 8540w running 2.6.36_rc6-git4 > Submitter : Ozan Caglayan <ozan@xxxxxxxxxxxxx> > Date : 2010-10-13 06:13 (68 days old) I'd be thinking that kworker going wonky is something for Tejun to have a look at.. Anyway, is it still relevant for current kernels? -- 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
