From: Nigel Cunningham <ncunningham@cyclades.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
shaohua.li@intel.com, vatsa@in.ibm.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
spyro@f2s.com, Andi Kleen <ak@suse.de>
Subject: Re: [PATCH 2.6.14-rc1-git5] sched: disable preempt in idle tasks
Date: Mon, 26 Sep 2005 09:24:56 +1000 [thread overview]
Message-ID: <1127690695.11522.9.camel@localhost> (raw)
In-Reply-To: <43322445.6050003@yahoo.com.au>
Hi.
On Thu, 2005-09-22 at 13:25, Nick Piggin wrote:
> Andrew Morton wrote:
> > Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> >
> >>This patch should hopefully fix Nigel's bug.
> >>
> >> Split out from sched-resched-opt.patch. Tested on i386 with acpi idle
> >> and poll idle (previous iterations tested on various other architectures).
> >
> >
> > This makes the emt64 machine reboot itself, which iirc was the behaviour in
> > the failing patch from which this one was split out.
> >
> > The machine is using acpi_processor_idle().
> >
>
> OK, thanks. That must be the preempt_disable() being called in
> start_secondary(). Maybe I should have listened to the comment.
>
> Can you try the following patch?
Well, I did manage to reproduce the bug again without Nick's patches. It
seems it only occurs when I really want it to suspend because I'm going
home :). I'll apply Nick's patches now and give it some testing for a
few days.
Regards,
Nigel
next prev parent reply other threads:[~2005-09-25 23:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 15:41 [PATCH 2.6.14-rc1-git5] sched: disable preempt in idle tasks 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 [this message]
2005-10-06 23:03 ` Nigel Cunningham
-- strict thread matches above, loose matches on Subject: below --
2005-11-02 2:33 Li, Shaohua
2005-11-02 2:46 ` Nick Piggin
2005-11-02 5:04 ` 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=1127690695.11522.9.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=ak@suse.de \
--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