From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [Bug #20232] kworker consumes ~100% CPU on HP Elitebook 8540w running 2.6.36_rc6-git4 Date: Mon, 20 Dec 2010 11:35:13 +0100 Message-ID: <1292841313.2708.137.camel@laptop> References: Mime-Version: 1.0 Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , Kernel Testers List , Maciej Rutecki , Florian Mickler , Ozan Caglayan , 2010-04-22-4aM62lgALcCSrlBSqq5r4w@public.gmane.org, Tejun Heo 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 > 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?