public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Avuton Olrich <avuton@gmail.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Kernel panic: Machine check exception
Date: Sat, 19 Nov 2005 22:24:17 +0000	[thread overview]
Message-ID: <87ek5ce0oe.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <1132436886.19692.17.camel@localhost.localdomain> (Alan Cox's message of "19 Nov 2005 21:16:21 -0000")

On 19 Nov 2005, Alan Cox stipulated:
> On Sad, 2005-11-19 at 12:54 -0800, Avuton Olrich wrote:
>> Is there a good way to narrow it down? I guess running a badmem
>> program would be good to start with, otherwise ...(?).
> 
> A memory test may be worth doing but most machine checks indicate the
> fault is more serious than bad memory.

Some of them are certainly not very serious in their effects. I get this
persistently, once every couple of months, on one of my machines (an
Athlon 4 with 768Mb of ECC RAM):

kernel: MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.
kernel: Bank 2: 940040000000017a

and I think it *is* a single slightly wobbly bit (the wobble being too
slight for memtest to find).

Nothing discernible has ever gone wrong as a result of that, right down
to repeated GCC enable-checking bootstrap-and-tests completing without
error (well, without any more than the expected XFAILs).

(I'm just *assuming* the `Bank 2' in this message refers to a bank of
RAM. Doubtless this assumption will now be shown to be utterly wrong and
a sign of terminal foolishness on my part... ;) )

-- 
`Y'know, London's nice at this time of year. If you like your cities
 freezing cold and full of surly gits.' --- David Damerell


  reply	other threads:[~2005-11-19 22:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19  9:45 Kernel panic: Machine check exception Avuton Olrich
2005-11-19  9:55 ` Avuton Olrich
2005-11-19 10:02 ` Arjan van de Ven
2005-11-19 10:04   ` Avuton Olrich
2005-11-19 13:24 ` Alan Cox
2005-11-19 20:54   ` Avuton Olrich
2005-11-19 21:48     ` Alan Cox
2005-11-19 22:24       ` Nix [this message]
2005-12-06 11:13       ` Eric W. Biederman
2005-12-06 13:23         ` Avuton Olrich
2005-12-06 19:45         ` Andi Kleen
2005-12-06 18:45           ` Avuton Olrich
2005-12-06 18:47             ` Andi Kleen
2005-12-08  2:46         ` Avuton Olrich

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=87ek5ce0oe.fsf@amaterasu.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=avuton@gmail.com \
    --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