From: Josh Brooks <user@mail.econolodgetulsa.com>
To: Billy Rose <billyrose@billyrose.net>
Cc: bp@dynastytech.com, <linux-kernel@vger.kernel.org>
Subject: Re: CPU failures ... or something else ?
Date: Wed, 25 Dec 2002 19:38:35 -0800 (PST) [thread overview]
Message-ID: <20021225193618.X6873-100000@mail.econolodgetulsa.com> (raw)
In-Reply-To: <E18ROk3-000117-00@host.ehost4u.biz>
Well actually I ordered a complete replacement system - identical in every
way. So I am getting that on saturday, and presumably that will just be
the big hammer that makes every problem go away.
I am just posting to get a head start on the issue if, for some crazy
reason I replace all hardware and the problem continues. Sounds like that
is a slim to none chance, since I am dealing with good hardware (dell) and
it looks like this is a faulty component at work.
Basically I am just moving the disks from one machine to another on
saturday, and I suspect the problems just disappear when I do that.
Comments on the possibility that the problems continue after moving the
disks to different (but identical) hardware ?
thanks!
On Wed, 25 Dec 2002, Billy Rose wrote:
> > Oh and by the way, this is a dell poweredge 2450, dual 866 p3 cpus,
> > 2gigs ram, and using a PERC 3/D. I have a 2.4.1 system running on
> > _identical_ hardware with no problems, and this system that is
> > MCE'ing is a 2.4.16.
>
> try reseating the cpu's and vrm's. if that doesnt work, remove cpu #2
> and #2 vrm. run it and see if the error occurs. if no error, #2 cpu or
> #2 vrm is bad. if the error still occurs, swap out cpu #1 and #1 vrm
> with cpu #2 and #2 vrm, then run again. if the error still occurs,
> youre SOL.
>
> billy
>
> =====
> "there's some milk in the fridge that's about to go bad...
> and there it goes..." -bobby
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-12-26 3:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-26 3:31 Billy Rose
2002-12-26 3:38 ` Josh Brooks [this message]
-- 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 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 3:50 Billy Rose
2002-12-26 3:54 ` 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=20021225193618.X6873-100000@mail.econolodgetulsa.com \
--to=user@mail.econolodgetulsa.com \
--cc=billyrose@billyrose.net \
--cc=bp@dynastytech.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®