From: Shawn Starr <shawn.starr@rogers.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bogus MCE upon resumption of system? - Resolved
Date: Sun, 27 Nov 2005 04:20:11 -0500 [thread overview]
Message-ID: <200511270420.11479.shawn.starr@rogers.com> (raw)
In-Reply-To: <200410201520.46957.shawn.starr@rogers.com>
As of 2.6.15-rc2 (or eariler .15 snapshot) The kernel now enables MCE checking
on resumption from suspend from disk thus there is no more bogus MCEs.
-snip-
[4358769.531000] [nosave pfn 0x3c4]<7>[nosave pfn 0x3c5]<6>[4358769.531000]
Intel machine check architecture supported.
[4358769.531000] Intel machine check reporting enabled on CPU#0.
[4358769.531000] swsusp: Restoring Highmem
Thanks,
Shawn.
On Wednesday 20 October 2004 15:20, Shawn Starr wrote:
> Suspend to RAM, haven't gotten around to rebuilding kernel with USB not
> compiled in.
>
> Can anyone verify this is a bogus MCE? it occurs only after resuming from
> suspend from RAM.
>
> Shawn.
>
> On October 20, 2004 11:48, Pavel Machek wrote:
> > Ahoj!
> >
> > > MCE: The hardware reports a non fatal, correctable incident occurred on
> > > CPU 0. Bank 1: f200000000000105
> > >
> > > Of note, when resume I see this MCE, though i suspect it is bogus upon
> > > resume.
> >
> > You did not tell me if it was suspend-to-disk or -to-RAM. Also you'd
> > better mail lkml... I know a little about MCEs.
> >
> > Pavel
prev parent reply other threads:[~2005-11-27 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200410101932.12431.shawn.starr@rogers.com>
[not found] ` <200410200454.16439.shawn.starr@rogers.com>
[not found] ` <20041020154854.GF26439@elf.ucw.cz>
2004-10-20 19:20 ` Bogus MCE upon resumption of system? Shawn Starr
2005-11-27 9:20 ` Shawn Starr [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=200511270420.11479.shawn.starr@rogers.com \
--to=shawn.starr@rogers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
Powered by JetHome