mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Martin.Bene@KPNQwest.com (Bene, Martin)
Cc: Simon.Richter@phobos.fachschaften.tu-muenchen.de ('Simon
	Richter'),
	linux-kernel@vger.kernel.org ('linux-kernel@vger.kernel.org')
Subject: Re: what causes Machine Check exception? revisited (2.2.18)
Date: Mon, 7 May 2001 14:51:01 +0100 (BST)	[thread overview]
Message-ID: <E14wlPj-0003WB-00@the-village.bc.nu> (raw)
In-Reply-To: <5F6171E541C8D311B9F200508B63D32801C31F52@ntexgvie01> from "Bene, Martin" at May 07, 2001 03:33:54 PM

> You get SIG11 errors when running programs(kernel compile seems to be agood
> example), you get crashing processes, you get all sorts of weird funnies but
> you really shouldn't get machine check exceptions.
> 
> I don't think there is a way a machine check exception can be triggered by
> software - which it would have to be in order to be caused by bad RAMs.

Bad ECC memory and unrecoverable ECC faults can certainly be reported back to
the processor electrically. Also an L2 cache load failing when the RAM fails
to ack the signals is quite visible to a processor.


  reply	other threads:[~2001-05-07 14:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-07 13:33 Bene, Martin
2001-05-07 13:51 ` Alan Cox [this message]
2001-05-07 18:12 ` Simon Richter
  -- strict thread matches above, loose matches on Subject: below --
2001-05-07 14:38 Ricardo Galli
2001-05-07 10:50 Bene, Martin
2001-05-07 13:04 ` Simon Richter
2001-05-07 18:23   ` Dan Hollis
2001-05-07 18:30     ` nick
2001-05-07 18:49     ` Simon Richter
2001-05-07  9:50 Juhan-Peep Ernits
2001-05-07 10:57 ` Alan Cox
2001-05-09  5:41   ` Mike Fedyk

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=E14wlPj-0003WB-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Martin.Bene@KPNQwest.com \
    --cc=Simon.Richter@phobos.fachschaften.tu-muenchen.de \
    --cc=linux-kernel@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 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®