From: Felipe W Damasio <felipewd@terra.com.br>
To: Josh Brooks <user@mail.econolodgetulsa.com>
Cc: Billy Rose <billyrose@billyrose.net>,
bp@dynastytech.com, linux-kernel@vger.kernel.org
Subject: Re: CPU failures ... or something else ?
Date: Thu, 26 Dec 2002 02:05:39 +0000 [thread overview]
Message-ID: <3E0A63F3.8020705@terra.com.br> (raw)
In-Reply-To: <20021225200357.U6873-100000@mail.econolodgetulsa.com>
Josh Brooks wrote:
> Understood. Thank you for that diagnosis.
>
> usually it says proc #1 in the error, but the first time it said proc #0 -
> is that interesting ?
It is.
This would be a stronger evidence of bad RAM, since the instruction
fetch error occured "randomly" on both processors.
Either that or both your processors are going bad :)
Please run memtest86 to be sure it's a bad RAM problem.
Kind Regards,
Felipe
next prev parent reply other threads:[~2002-12-26 4:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-26 4:03 CPU failures ... or something else ? Billy Rose
2002-12-26 4:04 ` Josh Brooks
2002-12-26 2:05 ` Felipe W Damasio [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2002-12-26 4:21 Billy Rose
2002-12-26 4:48 ` Josh Brooks
2002-12-26 3:50 Billy Rose
2002-12-26 3:54 ` Josh Brooks
2002-12-26 3:31 Billy Rose
2002-12-26 3:38 ` Josh Brooks
2002-12-26 3:13 Ro0tSiEgE
2002-12-26 3:22 ` Josh Brooks
2002-12-26 6:08 ` Joseph D. Wagner
2002-12-26 1:53 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
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
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=3E0A63F3.8020705@terra.com.br \
--to=felipewd@terra.com.br \
--cc=billyrose@billyrose.net \
--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