Subject: Re: hardware test
To: None <port-cobalt@NetBSD.org>
From: Christopher Schultz <christopher.d.schultz@comcast.net>
List: port-cobalt
Date: 05/26/2005 22:41:47
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigD6A6714D337F5593C8C89D8F
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Philip and Jebus,

>> so if the post test was failing how would I know ?
>
> You'd see it on the console at startup.  And I expect your Qube would
> probably refuse to boot.
>
>> and how complete of memory test does the qube do ?
>
> I have no idea. But I would be extremely surprised if your
> segmentation faults had anything to do with the hardware.

Most POST hardware tests are no more in-depth than you could accomplish
by yourself looking at the chips with a magnifying glass. The only time
I have ever seen a POST fail the memory was when a chip was only half
inserted.

I hardly have any experience with Cobalt hardware, but I know that Intel
and particularly AMD hardware have problems like this. (I love AMD but
their chips require so much of the crappy motherboards and RAM that
companies are building these days...).

Anyhow, random segfaults CERTAINLY CAN be a hardware problem. If you
have the ability to do so, try removing one of your RAM chips if you
have two, or trying another chip if you've got one lying around (yeah,
right... Qube memory is far too expensive to have a drawer full of it).
You're likely not to find any problems, though.

With one exception, every time I've had random segfaults in software
that I'm convinced is okay, it ends up being a bad motherboard. For the
Qube, that's pretty much bad news for the whole box, unfortunately. I've
used a tool on x86 hardware called memtest86 (www.memtest86.com) which
is extremely useful in finding hardware problems. Perhaps someone has
something like this for the MIPS architecture? Though I'm not sure how
you would run it, since these kinds of things generally want to be run
without an OS or other programs interfering.

You mentioned that an older version of Apache was working fine.... have
you tried downgrading to that version?

Also, there's a very good posibility that you made a mistake upgrading
your pkgsrc and you hosed an important library. I'm pretty ignorant when
it comes to the whole NetBSD packaging system (I used the restore CD way
back in the day), but I'm guessing that you can really break your system
if you make a wrong move.

-chris


--------------enigD6A6714D337F5593C8C89D8F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFClojr9CaO5/Lv0PARAkISAJ0WfvZtuWsW/cTq6dtR/g5omHhAxgCeNDqq
x6JjLbNAi7S7ovwhiCpzzdQ=
=F8F4
-----END PGP SIGNATURE-----

--------------enigD6A6714D337F5593C8C89D8F--