Re: CURRENT incredibly slow
- From: Peter Jeremy <PeterJeremy@xxxxxxxxxxxxxxxx>
- Date: Thu, 26 Jan 2006 12:16:48 +1100
On Thu, 2006-Jan-26 01:15:29 +0300, Gleb Smirnoff wrote:
>I washed it with ethanol thoroughly the day the wine was poured in.
A mixture of 11% ethanol, 88% water and 1% natural colourings and
flavourings (or thereabouts) is not the ideal cleaner for electronic
equipment :-)
> I think that the problem is not in gunge, but in corroded contacts in
>slot and on RAM.
It's unlikely that corroded contacts around the RAM would explain a
sudden change of CPU clock rate. That suggests the wine got under
some surface mount components and wasn't washed out thoroughly enough.
Contact cleaner may help, but if there is actually corrosion, you
probably need to mechanically scrub the corrosion off as well (eg with
a soft toothbrush).
Good luck.
--
Peter Jeremy
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: CURRENT incredibly slow
- From: Mark Kirkwood
- Re: CURRENT incredibly slow
- References:
- CURRENT incredibly slow
- From: Gleb Smirnoff
- Re: CURRENT incredibly slow
- From: Gleb Smirnoff
- Re: CURRENT incredibly slow
- From: Max Laier
- Re: CURRENT incredibly slow
- From: Gleb Smirnoff
- Re: CURRENT incredibly slow
- From: Peter Jeremy
- Re: CURRENT incredibly slow
- From: Gleb Smirnoff
- CURRENT incredibly slow
- Prev by Date: Re: [TEST/REVIEW] CPU accounting patches
- Next by Date: HEADS UP: pts code committed
- Previous by thread: Re: CURRENT incredibly slow
- Next by thread: Re: CURRENT incredibly slow
- Index(es):