From: Pavel Machek <pavel@ucw.cz>
To: Josh Brooks <user@mail.econolodgetulsa.com>
Cc: Bubba <bp@dynastytech.com>, linux-kernel@vger.kernel.org
Subject: Re: CPU failures ... or something else ?
Date: Thu, 26 Dec 2002 23:37:43 +0100 [thread overview]
Message-ID: <20021226223743.GA600@elf.ucw.cz> (raw)
In-Reply-To: <20021225190355.Q6873-100000@mail.econolodgetulsa.com>
Hi!
> So you are saying, that yes, it _is_ possible that my equipment is not
> faulty in any way ?
Well, if your machine produces spurious MCE's, you have machine with
*design* bug. That might be slightly better than machine with
overheating or similar problem ;-). Still its buggy machine.
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
next prev parent reply other threads:[~2003-01-01 20:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-26 1:53 CPU failures ... or something else ? Josh Brooks
2002-12-26 1:41 ` Felipe W Damasio
2002-12-26 2:02 ` Bubba
2002-12-26 3:04 ` Josh Brooks
2002-12-26 22:37 ` Pavel Machek [this message]
2002-12-26 3:09 ` Josh Brooks
2002-12-26 3:36 ` J Sloan
2002-12-26 3:39 ` Josh Brooks
2002-12-26 3:20 ` Josh Brooks
2002-12-26 6:03 ` Joseph D. Wagner
2002-12-27 23:30 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-12-26 3:13 Ro0tSiEgE
2002-12-26 3:22 ` Josh Brooks
2002-12-26 6:08 ` Joseph D. Wagner
2002-12-26 3:31 Billy Rose
2002-12-26 3:38 ` Josh Brooks
2002-12-26 3:50 Billy Rose
2002-12-26 3:54 ` Josh Brooks
2002-12-26 4:03 Billy Rose
2002-12-26 4:04 ` Josh Brooks
2002-12-26 2:05 ` Felipe W Damasio
2002-12-26 6:13 ` Joseph D. Wagner
2002-12-26 6:35 ` Josh Brooks
2002-12-26 6:49 ` Joseph D. Wagner
2002-12-26 7:08 ` Felipe W Damasio
2002-12-26 4:21 Billy Rose
2002-12-26 4:48 ` Josh Brooks
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=20021226223743.GA600@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=bp@dynastytech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user@mail.econolodgetulsa.com \
/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