Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Jan 2012 20:24:11 -0800
From:      Doug Hardie <bc979@lafn.org>
To:        FreeBSD Mailing List <freebsd-questions@freebsd.org>
Subject:   Re: Probable Hardware Failure
Message-ID:  <6E262E0B-B86D-45B6-9DC6-CE56EB2B20FD@lafn.org>
In-Reply-To: <CAKnE0ZuUkBvt29zL%2BYRhbpLkqDPU6u-VkT0odg-G=qd0oCB4Ww@mail.gmail.com>
References:  <C5188F60-2B7B-4AA7-8270-A2153925AD2B@lafn.org> <CAKnE0ZuUkBvt29zL%2BYRhbpLkqDPU6u-VkT0odg-G=qd0oCB4Ww@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On 14 January 2012, at 18:11, _ wrote:

> Memory is a rather broad term. If by memory you mean RAM, you could =
replace your current RAM with another chip, supposing you have one =
around.
>=20
> An interesting read on "Double Fault" is:=20
>=20
> http://en.wikipedia.org/wiki/Double_fault
>=20
> According to it, that would rather point to a software than a hardware =
related problem.
>=20
>=20
> On Sun, Jan 15, 2012 at 1:12 AM, Doug Hardie <bc979@lafn.org> wrote:
> I have a pretty old desktop that has been around quite awhile.  It has =
started periodic crashes.  No log messages.  However, the core status =
files all show "double fault".  I am confident this is a hardware issue, =
but is there any easy way to determine if its power or memory related?  =
Those are the primary candidates although memory is also possible.  We =
really need to replace the entire unit, but that might be a bit more =
salable if I can present convincing evidence of the cause of the =
problem.

I doubt if its a direct software fault.  The system is running 7.2 and =
has been running that for several years without any problems.  Nothing =
has been changed on it.  However, a memory fault could easily end up in =
the kernel thus making it look like a software problem.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6E262E0B-B86D-45B6-9DC6-CE56EB2B20FD>