From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: carlos@fisica.ufpr.br (Carlos Carvalho)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
linux-kernel@vger.kernel.org (Linux Kernel Mailing List)
Subject: Re: CPU error codes
Date: Wed, 7 Feb 2001 08:53:24 +0000 (GMT) [thread overview]
Message-ID: <E14QQLw-00087S-00@the-village.bc.nu> (raw)
In-Reply-To: <14976.24819.276892.26475@hoggar.fisica.ufpr.br> from "Carlos Carvalho" at Feb 06, 2001 06:39:15 PM
> Really? I thought it could be because of RAM. Here's the story:
RAM talks to the chipset so I dont think it could (unless it confused the
chipset)
> CPU 1: Machine Check Exception: 0000000000000004
> Bank 4: b200000000040151<0>Kernel panic: CPU context corrupt
Ok that decodes as:
Status valid
Uncorrect Error
Error Enabled
Processor Context Corrupt
Memory Heirarchy Error
Instruction Fetch
L1 cache
More than that I can't really say. Power and heat problems can certainly
trigger MCE's. I don't know if I/O devices can influence them.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-02-07 8:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-24 19:30 James Simmons
2001-01-25 1:34 ` Alan Cox
2001-01-25 9:14 ` James Sutherland
2001-01-28 21:29 ` H. Peter Anvin
2001-01-31 15:23 ` Alan Cox
2001-01-31 21:24 ` James Sutherland
2001-01-31 21:33 ` Dan Hollis
2001-02-06 20:39 ` Carlos Carvalho
2001-02-07 4:21 ` H. Peter Anvin
2001-02-07 8:53 ` Alan Cox [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=E14QQLw-00087S-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=carlos@fisica.ufpr.br \
--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®