Subject: Re: [PATCH 2.6.14-rc1-git5] sched: disable preempt in idle tasks
From: Nigel Cunningham <ncunningham@cyclades.com>
Reply-To: ncunningham@cyclades.com
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Li Shaohua <shaohua.li@intel.com>, Andrew Morton <akpm@osdl.org>,
       Srivatsa Vaddagiri <vatsa@in.ibm.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Ian Molton <spyro@f2s.com>
In-Reply-To: <43682878.3040800@yahoo.com.au>
References: <59D45D057E9702469E5775CBB56411F1C19A01@pdsmsx406>
	 <43682878.3040800@yahoo.com.au>
Content-Type: text/plain
Organization: Cyclades
Message-Id: <1130907843.3853.1.camel@localhost>
Mime-Version: 1.0
Date: Wed, 02 Nov 2005 16:04:04 +1100
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1160
Lines: 39

Hi Nick.

On Wed, 2005-11-02 at 13:46, Nick Piggin wrote:
> Hi Shaohua,
> 
> Li, Shaohua wrote:
> 
> > 
> > What's the status of the patch? I didn't see it in base kernel.
> > We found another bug related with this issue. On UP system, if a CPU
> > enters 
> > 'mwait_idle', it never leaves it, as the 'mwait_idle' loop will never
> > end.
> > Disabling preempt fixes the bug. Should I submit a patch just disabling
> > preempt in 'mwait_idle' or wait for your patch?
> > 
> 
> The patch is in Andrew's tree, and it should get merged for 2.6.15.
> If you have verified that disabling preempt in mwait_idle fixes the
> bug, then you may like to send that to the 2.6.14.stable guys.

I sent an email a couple of weeks ago saying that it looked like it did
the trick for me - no problems in two weeks of testing. (I would have
easily seen it within a day or two prior to this).

Regards,

Nigel

> Thanks,
> Nick
-- 


-
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/