Re: Probable Hardware Failure

2012-01-15 Thread Zane C. B-H.
On Sat, 14 Jan 2012 16:12:24 -0800
Doug Hardie bc...@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.

In regards to the RAM, I would strongly suggest memtest86/memtest86+.
When you begin seeing odd issues like that, it can be a handy tool to
use for a quick RAM check.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Probable Hardware Failure

2012-01-15 Thread Dave
On 14 Jan 2012 at 16:12, Doug Hardie 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.
 

Doug.

First check the Power Supply voltages are correct, and not too noisy.  
You'll need a good DMM, and 'scope for that.

Then, Visually examine the motherboard.  Are any of the round can 
electrolytic cap's Bulging at the top, or showing some brown or green 
gunk leaking out from where they sit on the board.

Likewise, it's often worth checking the low voltage caps in the PSU too.  
CAUTION!  Lots of volts exist in places inside them, take care, leave it 
a few mins after unplugging before taking it apart.

If so, it's not uncommon, you'll need to re-cap the Mobo, and or the PSU.  
Chances are, it's just one particular make/type that has failed, so if 
the others look OK, just change the failed ones.  Get the same value and 
voltage, but if you can from a reputable manufaturer, Panasonic or some 
such.

NOTE!  It's not uncommon either, for some parts to be installed at 
manufature the wrong way round.  It's amazing they last as long as they 
do before letting go.  Also, at least one Mobo maker had the wrong 
polarity markings on the board.  In those cases, you'll need to buzz 
out the associated power rail, comparing the polarity of the suspect 
part, with it's copanions on the same power rail.

For some common Mobo's, if you google the model number, you'll find 
websites selling complete re-cap kits, or offering an exchange service.

This is A LOT more common, than failing RAM, but can present itself in 
many and varied ways, from corrupted display's, to systems that wont 
boot.  Laptops are not immune to this either.

Also, Hard Drives can go funny with age, not failing as such, but the 
surface getting corrupted so that the drives own logic cant always 
unscramble the mess to the OS's satisfaction.

Then, there is the situation (I had one recently) where a failing PSU, 
caused Hard Drive data corruption.

Mr Gibson's product Spinrite is the tool to use to fix that (and it 
did!)  Not free, but more than worth the weight of a CD, Floppy or USB 
stick in Gold!  But you'll need to make sure the Mobo and everything else 
is OK.   It also works on Floppy drives, if you Just HAVE to recover 
that data.   If you have a fleet of machines, you should have your own 
copy.   No affiliation, just a more than happy long term owner/user of 
that tool.   (www.grc.com)

I've resurected more than one Sick PC by following some or all of the  
above, there again, I can wield a soldering iron with the best of them, 
and have the test gear to hand to fault find these things, and a source 
of parts.   But it saves a shed load of money if you can afford the time 
to do it...

Hope something helps.

Best Regards.

Dave B.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Probable Hardware Failure

2012-01-14 Thread Doug Hardie
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.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Probable Hardware Failure

2012-01-14 Thread _
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.

An interesting read on Double Fault is:

http://en.wikipedia.org/wiki/Double_fault

According to it, that would rather point to a software than a hardware
related problem.


On Sun, Jan 15, 2012 at 1:12 AM, Doug Hardie bc...@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.


 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to 
 freebsd-questions-unsubscr...@freebsd.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Probable Hardware Failure

2012-01-14 Thread Doug Hardie

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.
 
 An interesting read on Double Fault is: 
 
 http://en.wikipedia.org/wiki/Double_fault
 
 According to it, that would rather point to a software than a hardware 
 related problem.
 
 
 On Sun, Jan 15, 2012 at 1:12 AM, Doug Hardie bc...@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.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org