From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Jones <davej@redhat.com>
Cc: antispam@absamail.co.za, linux-kernel@vger.kernel.org
Subject: Re: [2.6.1 MCE falseness?] Hardware reports non-fatal error
Date: Wed, 21 Jan 2004 23:13:26 +1100 [thread overview]
Message-ID: <20040121231326.3acd3823.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20040118020301.GA8621@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
On Sun, 18 Jan 2004 02:03:01 +0000 Dave Jones <davej@redhat.com> wrote:
>
> On Sun, Jan 18, 2004 at 03:44:16AM +0200, Niel Lambrechts wrote:
>
> > I get the following problem with 2.6.1 consistently after apm resuming:
> > "ksyrium kernel: MCE: The hardware reports a non fatal, correctable
> > incident occurred on CPU 0.
> >
> > Message from syslogd@ksyrium at Wed Jan 14 13:33:06 2004 ...
> > ksyrium kernel: Bank 1: f2000000000001c5"
>
> As it only happens when you resume from APM, I'm inclined to believe
> its a BIOS bug. With the output of dmidecode, we could blacklist this
> box to not do the nonfatal checking.
My Thinkpad T22 produces a similar warning on resume using APM:
kernel: MCE: The hardware reports a non fatal, correctable incident occurred on CPU 0.
kernel: Bank 1: f200000000000104
dmidecode output starts with:
# dmidecode 2.3
SMBIOS 2.3 present.
46 structures occupying 1585 bytes.
Table at 0x1FFF0000.
Handle 0x0000
DMI type 0, 20 bytes.
BIOS Information
Vendor: IBM
Version: 16ET31WW (1.11 )
Release Date: 03/20/2003
.
.
Handle 0x0001
DMI type 1, 25 bytes.
System Information
Manufacturer: IBM
Product Name: 26475EA
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-21 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 1:44 Niel Lambrechts
2004-01-18 2:03 ` Dave Jones
2004-01-21 12:13 ` Stephen Rothwell [this message]
2004-01-18 13:30 Pedro Larroy
2004-01-18 14:23 ` glee
2004-01-18 20:04 ` Dave Jones
2004-01-20 19:43 Niel Lambrechts
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=20040121231326.3acd3823.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=antispam@absamail.co.za \
--cc=davej@redhat.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
all inboxes | Powered by JetHome®