mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Paul Larson <plars@austin.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.11 APIC problems
Date: Wed, 10 Oct 2001 13:46:34 -0700	[thread overview]
Message-ID: <1994214429.1002721594@mbligh.des.sequent.com> (raw)
In-Reply-To: <1002727820.29151.21.camel@plars.austin.ibm.com>

>  So, I tried inserting the die() like you said without console serial.  I
>  got pagefulls of dumps and pretty soon it rebooted itself.  So, I logged
>  to the serial console again on the next reboot to capture the output. 
>  Looks like we got the "APIC error" message in the log too.  It's a
>  really long log so I attached it rather than putting it inline.

Ick. You need to disable the repeated interrupt. Try this instead of
the die:

cli();
 __asm__ __volatile__ ("hlt");

And if it makes a huge logfile again, just mail the first bit .... I don't
care about huge emails, but others on lkml probably do ;-)

M.

PS. Nor do I care what the die says, I just want to stop the processor.
I want to know what it was doing just before the smp_error_interrupt.
There are more elegant solutions around to stop repeated APIC errors,
but this should be OK for debug.

       reply	other threads:[~2001-10-10 20:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1002727820.29151.21.camel@plars.austin.ibm.com>
2001-10-10 20:46 ` Martin J. Bligh [this message]
2001-10-11  7:37 Roman Kagan
     [not found] <1979423952.1002706803@mbligh.des.sequent.com>
2001-10-10 14:24 ` Paul Larson
  -- strict thread matches above, loose matches on Subject: below --
2001-10-10  9:46 Paul Larson

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=1994214429.1002721594@mbligh.des.sequent.com \
    --to=martin.bligh@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plars@austin.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

all inboxes | Powered by JetHome®