Re: SCO crash
From: Bill Vermillion (bv_at_wjv.comREMOVE)
Date: 04/30/04
- Next message: FyRE: "Re: Mount linux filesystem"
- Previous message: Bill Vermillion: "Re: The reason Baystar wants its money back from SCOG"
- In reply to: Tomek: "Re: SCO crash"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 30 Apr 2004 02:35:01 GMT
In article <c6rmkm$1sd$1@portraits.wsisiz.edu.pl>,
Tomek <trurka@polbox.com> wrote:
>>
>> Typically the 0x0000000E indicates a hardware issue/failure. Possibly
>> a memory problem?
>>
>> >
>>
>> A fairly comprehensive list of things to look into:
>> http://aplawrence.com/Unixart/trape.html
>Thanks for help
>I saw it few weeks ago and I tested the RAM by diagtool (it's hp
>netserver) and there was no error. I think i will try to change
>RAM. Maybe this will work.
Over the years I've noticed that the only real way to test RAM and
be sure is to pull it and put it in a hardware tester.
I have seen a few good SW testers, but few of us have the time to
let them run for the many hours to test all failure modes.
If the memory test runs in under a 1/2 hour it would only find the
most egegious errors.
-- Bill Vermillion - bv @ wjv . com
- Next message: FyRE: "Re: Mount linux filesystem"
- Previous message: Bill Vermillion: "Re: The reason Baystar wants its money back from SCOG"
- In reply to: Tomek: "Re: SCO crash"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|