From: "Billy Rose" <billyrose@billyrose.net>
To: user@mail.econolodgetulsa.com
Cc: bp@dynastytech.com, linux-kernel@vger.kernel.org, felipewd@terra.com.br
Subject: Re: CPU failures ... or something else ?
Date: Wed, 25 Dec 2002 23:21:23 -0500 [thread overview]
Message-ID: <E18RPWN-0001xf-00@host.ehost4u.biz> (raw)
> 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 ?
youre welcome :)
if youre hanging on to that box, remove the memory from banks 3 and 4
and it should be ok. if my memory serves me right, you cant have only 3
banks of memory (hence removing bank 3 also), the motherboard is
configured to handle 1, 2, or 4 populated banks. it you leave bank 3
in while removing bank 4, it will beep at you when you power it on and
do nothing. with a gig of ram, it should still be plenty useful.
billy
=====
"there's some milk in the fridge that's about to go bad...
and there it goes..." -bobby
next reply other threads:[~2002-12-26 4:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-26 4:21 Billy Rose [this message]
2002-12-26 4:48 ` CPU failures ... or something else ? Josh Brooks
-- strict thread matches above, loose matches on Subject: below --
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: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=E18RPWN-0001xf-00@host.ehost4u.biz \
--to=billyrose@billyrose.net \
--cc=bp@dynastytech.com \
--cc=felipewd@terra.com.br \
--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