From: Nigel Cunningham <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>
Subject: Re: [PATCH 2.6.14-rc1-git5] sched: disable preempt in idle tasks
Date: Wed, 02 Nov 2005 16:04:04 +1100 [thread overview]
Message-ID: <1130907843.3853.1.camel@localhost> (raw)
In-Reply-To: <43682878.3040800@yahoo.com.au>
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
--
next prev parent reply other threads:[~2005-11-02 5:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 2:33 [PATCH 2.6.14-rc1-git5] sched: disable preempt in idle tasks Li, Shaohua
2005-11-02 2:46 ` Nick Piggin
2005-11-02 5:04 ` Nigel Cunningham [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-21 15:41 Nick Piggin
2005-09-21 21:43 ` Nigel Cunningham
2005-09-22 1:31 ` Andrew Morton
2005-09-22 3:25 ` Nick Piggin
2005-09-22 9:03 ` Andi Kleen
2005-09-25 23:24 ` Nigel Cunningham
2005-10-06 23:03 ` Nigel Cunningham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1130907843.3853.1.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=shaohua.li@intel.com \
--cc=spyro@f2s.com \
--cc=vatsa@in.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox