archive mirror
 help / color / mirror / Atom feed
From: Ville Herva <>
To: Alan Cox <>
Subject: Re: 2.2.22 on HP Vectra 90/5: Machine check exception on boot
Date: Thu, 26 Sep 2002 12:59:57 +0300	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Sep 26, 2002 at 05:49:33AM -0400, you [Alan Cox] wrote:
> > CPU0 Machine check exception 0x  10E2C0 (type 0x    09)
> > 2.0.35 does boot just fine.
> MCE comes from the hardware not the OS. You may have another odd box like
> the compaq ones where it seems the external mce trigger isnt wired properly.
> If so boot with "nomce"

(It's actually Vectra XU 5/90, not 90/5 - now that I have physical access to
the box again. The google is full of horror stories about problems with this
particular model ;).

I tried SMP kernel, and it went a little further (no MCE) but it halted
after "Intel old style machine check architecture supported". For some odd
reason, linux says the box has 2 cpu's during boot, but it afaik only has

The I forced mce_disabled to 1 in bluesmoke.c, and the SMP kernel booted.
During init, it oopsed, however.

I then compiled an UP kernel again, with mce_disabled=1 (same as "nomce" I
gather), and it booted.

The 3c509 appears not to work (but was found), scsi cdrom coughs badly but
it did boot :).


-- v --

  parent reply	other threads:[~2002-09-26  9:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 14:55 2.2.22 on HP Vectra 90/5: Machine check exception on boot Ville Herva
     [not found] ` <>
2002-09-26  9:59   ` Ville Herva [this message]
2002-09-26 10:26     ` Serious Problems with diskless clients Marco Schwarz
2002-09-26 11:18       ` Wakko Warner
2002-09-26 20:58         ` Daniel Egger
2002-09-26 17:53       ` Denis Vlasenko
2002-09-26 13:16         ` Marco Schwarz

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).