From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] [RFC] Remove MCA dump?
Date: Wed, 21 Aug 2002 18:30:15 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905971@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905964@msgid-missing>
>>>>> On Wed, 21 Aug 2002 13:38:32 +0100, Matthew Wilcox <willy@debian.org> said:
Matthew> On Wed, Aug 21, 2002 at 02:34:42PM +0200, Andreas Schwab
Matthew> wrote:
>> Matthew Wilcox <willy@debian.org> writes:
>>
>> |> The MCA handler is completely useless. If I crash the machine
>> and |> forget to clear the MCA dump in firmware, at the next boot
>> Linux dumps |> the registers (in a hard-to-understand style) and
>> hangs.
>>
>> I haven't seen such hangs on our machines, except for some old
>> pre-production systems that lack the necessary hardware support.
Matthew> I wonder why not. Here's the code:
Matthew> void init_handler_platform (struct pt_regs *regs) { /* if a
Matthew> kernel debugger is available call it here else just dump
Matthew> the reg isters */
Matthew> show_regs(regs); /* dump the state info */ while
Matthew> (1); /* hang city if no debugger */ }
Matthew> Maybe it only locks up that specific processor so you
Matthew> didn't notice you'd lost a processor on an SMP system?
This endless loop happens only in response to an INIT event. The
boot-time MCA dump does not go through this path.
--david
prev parent reply other threads:[~2002-08-21 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 11:51 [Linux-ia64] [RFC] Remove MCA dump? Matthew Wilcox
2002-08-21 12:34 ` Andreas Schwab
2002-08-21 12:38 ` Matthew Wilcox
2002-08-21 13:04 ` Erich Focht
2002-08-21 14:59 ` Hall, Jenna S
2002-08-21 16:14 ` David Mosberger
2002-08-21 18:30 ` David Mosberger [this message]
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=marc-linux-ia64-105590701905971@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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.