Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933658AbYCFMXe (ORCPT ); Thu, 6 Mar 2008 07:23:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1764162AbYCFMWr (ORCPT ); Thu, 6 Mar 2008 07:22:47 -0500 Received: from E23SMTP05.au.ibm.com ([202.81.18.174]:51460 "EHLO e23smtp05.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763349AbYCFMWq (ORCPT ); Thu, 6 Mar 2008 07:22:46 -0500 Date: Thu, 6 Mar 2008 17:52:43 +0530 From: Gautham R Shenoy To: Oleg Nesterov Cc: Yi Yang , Ingo Molnar , akpm@linux-foundation.org, linux-kernel@vger.kernel.org, "Rafael J. Wysocki" , Thomas Gleixner Subject: Re: [BUG 2.6.25-rc3] scheduler/hotplug: some processes are dealocked when cpu is set to offline Message-ID: <20080306122243.GB23865@in.ibm.com> Reply-To: ego@in.ibm.com References: <1204483329.3607.8.camel@yangyi-dev.bj.intel.com> <20080303153154.GA11288@in.ibm.com> <1204555505.3842.4.camel@yangyi-dev.bj.intel.com> <20080304052613.GA28632@in.ibm.com> <20080304150107.GA564@tv-sign.ru> <20080305100509.GA9265@in.ibm.com> <20080305135314.GA84@tv-sign.ru> <20080306111525.GA23865@in.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080306111525.GA23865@in.ibm.com> User-Agent: Mutt/1.5.15+20070412 (2007-04-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1850 Lines: 55 On Thu, Mar 06, 2008 at 04:45:25PM +0530, Gautham R Shenoy wrote: > On Wed, Mar 05, 2008 at 04:53:14PM +0300, Oleg Nesterov wrote: > > On 03/05, Gautham R Shenoy wrote: > > > > > > On Tue, Mar 04, 2008 at 06:01:07PM +0300, Oleg Nesterov wrote: > > > > On 03/04, Gautham R Shenoy wrote: > > > > > > > > > > So at times, the callback thread is blocked on kthread_stop(k) in > > > > > softlockup.c, while other time, it was blocked in > > > > > cleanup_workqueue_threads() in workqueue.c. > > > > > > > > >From another message: > > > > > > > > > > However, it remains in R< state > > > > > > > > What about cwq->thread? Was it TASK_RUNNING too? > > > > > > No, it was in TASK_UNINTERRUPTIBLE state. The last thing it ever > > > executed was the wait_for_completion in flush_cpu_workqueue() > > > > You misunderstood ;) The task doing _cpu_down() hang in flush_cpu_workqueue(), > > because cwq->thread doesn't want to die. But what was cwq->thread->state? > > > > Yup, sorry for that stupid reply. > > > Could you try the patch? Yi constantly sees the tasks in R< state. > > I am starting to suspect some scheduling issue. > > Me too. With your patch applied there were quite a few tasks in the > running state which didn't get the cpu for more than 120 seconds. > > I could be a scheduler problem which CPU-Hotplug is able to catch more > easily. Will try a git bisect. BTW, with your patch, I get the "task can't get CPU for more than 120 seconds" message even while running a kernbench on 2.6.25-rc2. > > > > > > Oleg. > > -- > Thanks and Regards > gautham -- Thanks and Regards gautham -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/