From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: CaT <cat@zip.com.au>, Andi Kleen <ak@muc.de>,
Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Use correct x86 reboot vector
Date: 11 May 2003 12:01:57 -0600 [thread overview]
Message-ID: <m1bry9746i.fsf@frodo.biederman.org> (raw)
In-Reply-To: <1052578182.16166.6.camel@dhcp22.swansea.linux.org.uk>
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Sad, 2003-05-10 at 04:35, CaT wrote:
> > On Sat, May 10, 2003 at 04:56:34AM +0200, Andi Kleen wrote:
> > > Extensive discussion by various experts on the discuss@x86-64.org
> > > mailing list concluded that the correct vector to restart an 286+
> > > CPU is f000:fff0, not ffff:0000. Both seem to work on current systems,
> > > but the first is correct.
> >
> > Could this bug, by any chance, cause a system to shutdown instead of
> > rebooting? This is what happens to me at the moment but not each and
> > every time.
>
> Unlikely. But try it and see 8)
>
> At least some SMP boxes freak if you do a poweroff request on CPU != 0
As per the MP spec. The system should reboot on the bootstrap cpu.
smp_processor_id() == 0 on x86. apicid??
I have a patch for this as part my kexec stuff as the kernel freaks
when it doesn't start up on the bootstrap cpu as well. I am busily
cleaning it up so it works in interrupt context as well.
Alan if you want it holler and I can send it to you as well.
Eric
next prev parent reply other threads:[~2003-05-11 17:52 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 2:56 [PATCH] Use correct x86 reboot vector Andi Kleen
2003-05-10 3:35 ` CaT
2003-05-10 3:58 ` H. Peter Anvin
2003-05-10 14:49 ` Alan Cox
2003-05-10 16:17 ` Jamie Lokier
2003-05-10 18:47 ` Jos Hulzink
2003-05-11 18:01 ` Eric W. Biederman [this message]
2003-05-11 17:24 ` Alan Cox
2003-05-11 19:04 ` Eric W. Biederman
2003-05-12 5:48 ` [PATCH] always shutdown on the bootstrap processor Eric W. Biederman
2003-05-10 16:15 ` [PATCH] Use correct x86 reboot vector Jamie Lokier
2003-05-10 17:09 ` Randy.Dunlap
2003-05-10 19:41 ` Jos Hulzink
2003-05-10 18:10 ` Jamie Lokier
2003-05-10 20:55 ` Jos Hulzink
2003-05-11 3:50 ` Linus Torvalds
2003-05-11 9:37 ` Jos Hulzink
2003-05-11 14:01 ` Jamie Lokier
2003-05-11 17:38 ` Davide Libenzi
2003-05-11 17:56 ` Eric W. Biederman
2003-05-11 18:23 ` Davide Libenzi
2003-05-11 19:12 ` Eric W. Biederman
2003-05-12 15:36 ` Maciej W. Rozycki
2003-05-13 6:35 ` H. Peter Anvin
2003-05-11 18:38 ` Linus Torvalds
2003-05-11 19:00 ` Matt Mackall
2003-05-11 19:16 ` Eric W. Biederman
2003-05-12 1:07 ` H. Peter Anvin
2003-05-11 19:10 ` Eric W. Biederman
2003-05-11 18:43 ` Christer Weinigel
2003-05-11 20:22 ` wingel
2003-05-11 20:26 ` Davide Libenzi
2003-05-11 17:54 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 12:49 Chuck Ebbert
2003-05-13 18:45 ` H. Peter Anvin
2003-05-13 19:04 ` Richard B. Johnson
2003-05-13 19:27 ` H. Peter Anvin
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=m1bry9746i.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=ak@muc.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cat@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.