From: Nicolas Mailhot <Nicolas.Mailhot@laPoste.net>
To: linux-kernel@vger.kernel.org
Subject: MCE exception advice
Date: 12 Jul 2003 12:09:41 +0200 [thread overview]
Message-ID: <1058004581.6808.10.camel@rousalka.dyndns.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
[ Please CC me on answers since I'm not on the list ]
Hi,
I've been getting MCE's repeatedly today when trying to compile
2.5.75-bk1 on 2.5.75-bk1 (obviously I didn't have them yesterday when I
build my first 2.5.75-bk1 kernel on a 2.4 kernel).
The MCE is always the same (I think) and reads like this :
CPU 0: Machine Check Exception: 0000000000000004
Bank 0: b600000000000135 at 000000000b99b9f0
Kernel panic: CPU context corrupt
Which when decoded with parsemce gives :
[nim@rousalka parse]$ ./parse -i < mce
CPU 0
Status: (4) Machine Check in progress.
Restart IP invalid.
parsebank(0): b600000000000135 @ b99b9f0
External tag parity error
CPU state corrupt. Restart not possible
Address in addr register valid
Error enabled in control register
Error not corrected.
Memory heirarchy error
Request: Generic error
Transaction type : Data
Memory/IO : Reserved
I'd like to have some advice on what to do next. Is this a 2.5 bug ? An
hardware problem only triggered in 2.5 because it exercises the harware
in a different way ? Should I change something in the system ? If so,
should I change memory, cpu, psu, something else ?
I don't usually build 2.5 on 2.5, but again yesterday was very hot and
hardware might have suffered (the best case cooling can not do much with
room temperature = 30+ °C)
Any hint will be welcome - this is my first mce encounter.
Regards,
--
Nicolas Mailhot
[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-07-12 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 10:09 Nicolas Mailhot [this message]
2003-07-12 10:20 ` Nicolas Mailhot
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=1058004581.6808.10.camel@rousalka.dyndns.org \
--to=nicolas.mailhot@laposte.net \
--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®