From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: jmoyer@redhat.com, Arjan van de Ven <arjanv@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: finding out the boot cpu number from userspace
Date: Mon, 02 Aug 2004 19:23:00 +0100 [thread overview]
Message-ID: <1091470979.857.7.camel@localhost.localdomain> (raw)
In-Reply-To: <35890000.1091472541@[10.10.2.4]>
On Llu, 2004-08-02 at 19:49, Martin J. Bligh wrote:
> Ah, OK didn't know that ... however, I'm not convinced that panicing is
> really that useful ... what happens if you proceed? IIRC, this is before
> console_init as well, so people won't even see the error. At least it
> should only do that on machines that are borked in such a fashion - 99% of
> machines will work fine, AFAICS.
The APM power off one is actually very common. Another one the ACPI guys
are now fighting that we also hit with SMM is E750x systems, where both
SMM traps and ACPI appear only to work on the boot CPU.
The panic at least made sure that we didnt end up with random mysterious
later problems that would be "fun" to debug.
(Note btw we sometimes care that kexec runs the new boot code on the
right processor because the 16bit entry points for some things also use
SMM traps on certain bioses in order to get a clean entry/stack/etc)
Alan
next prev parent reply other threads:[~2004-08-02 19:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 12:16 finding out the boot cpu number from userspace Arjan van de Ven
2004-08-02 13:37 ` Dave Jones
2004-08-02 14:13 ` Alan Cox
2004-08-02 14:30 ` Zwane Mwaikambo
2004-08-02 14:46 ` Richard B. Johnson
2004-08-02 15:50 ` Martin J. Bligh
2004-08-02 16:58 ` Jeff Moyer
2004-08-02 17:23 ` Martin J. Bligh
2004-08-02 17:42 ` Alan Cox
2004-08-02 18:49 ` Martin J. Bligh
2004-08-02 18:23 ` Alan Cox [this message]
2004-08-02 20:08 ` Chris Wedgwood
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=1091470979.857.7.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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