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?
Date: Wed, 20 Oct 2004 15:20:46 -0400 [thread overview]
Message-ID: <200410201520.46957.shawn.starr@rogers.com> (raw)
In-Reply-To: <20041020154854.GF26439@elf.ucw.cz>
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
next prev parent reply other threads:[~2004-10-21 6:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 23:32 [ipw2200]Confirmation of power management problem Shawn Starr
[not found] ` <200410102023.50379.shawn.starr@rogers.com>
[not found] ` <2894.194.77.192.95.1097474839.squirrel@www.mocka.de>
[not found] ` <2894.194.77.192.95.1097474839.squirrel-Iw/ES6IqVGAuZeo0DBJMuQ@public.gmane.org>
2004-10-11 6:38 ` [Ipw2100-devel] " Shawn Starr
[not found] ` <200410101932.12431.shawn.starr-bJEeYj9oJeDQT0dZR+AlfA@public.gmane.org>
2004-10-11 0:16 ` Alejandro Bonilla
2004-10-18 13:35 ` Pavel Machek
[not found] ` <20041018133530.GA17754-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2004-10-21 20:50 ` [Ipw2100-devel] " Shawn Starr
[not found] ` <200410200454.16439.shawn.starr@rogers.com>
[not found] ` <20041020154854.GF26439@elf.ucw.cz>
2004-10-20 19:20 ` Shawn Starr [this message]
2005-11-27 9:20 ` Bogus MCE upon resumption of system? - Resolved Shawn Starr
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=200410201520.46957.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.