From: Andy Lutomirski <luto@myrealbox.com>
To: bert hubert <ahu@ds9a.nl>
Cc: Andy Lutomirski <luto@myrealbox.com>, linux-kernel@vger.kernel.org
Subject: Re: [x86_64] how worried should I be about MCEs?
Date: Sat, 30 Apr 2005 14:02:04 -0700 [thread overview]
Message-ID: <4273F24C.3040202@myrealbox.com> (raw)
In-Reply-To: <20050430203723.GA8122@outpost.ds9a.nl>
bert hubert wrote:
> On Sat, Apr 30, 2005 at 01:16:49PM -0700, Andy Lutomirski wrote:
>
>>Every now and then, after rebooting, the kernel notices some MCEs.
>>Should I be worried about this?
>
>
> If these reports are true, they would be worrying. But I find them a bit
> hard to believe - the bit combinations don't appear to make sense.
True.
>
> I have an AMD64 machine which logs 'MCE reported' every once in a while but
> otherwise functions perfectly and I haven't yet coaxed it into telling me
> the content of the errors.
>
> Might there be a bug here? How did you create this log?
This is from mcelog 0.3, dumped with a daily cron job to
/var/log/mcelog. I think it came from 2.6.11-gentoo-r6 (which should be
essentially 2.6.11.7).
The machine is Athlon 64 3200+ (754), on an MSI K8T Neo-FIS2R, running a
moderately old BIOS but one that has erratum #93 (or whatever it was) fixed.
Anything I should attach to provide more info?
I just upgraded to mcelog-0.4, but at this rate I don't expect a new
dump for awhile.
Thanks,
Andy
next prev parent reply other threads:[~2005-04-30 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 20:16 [x86_64] how worried should I be about MCEs? Andy Lutomirski
2005-04-30 20:37 ` bert hubert
2005-04-30 21:02 ` Andy Lutomirski [this message]
2005-04-30 21:41 ` possibly bogus AMD64 MCE reporting bert hubert
2005-05-02 16:49 ` [x86_64] how worried should I be about MCEs? Andi Kleen
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=4273F24C.3040202@myrealbox.com \
--to=luto@myrealbox.com \
--cc=ahu@ds9a.nl \
--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