Date: Thu, 26 Jan 2006 12:16:48 +1100 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: Gleb Smirnoff <glebius@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: CURRENT incredibly slow Message-ID: <20060126011648.GL25397@cirb503493.alcatel.com.au> In-Reply-To: <20060125221529.GJ83922@cell.sick.ru> References: <20060125203821.GF83922@FreeBSD.org> <20060125211925.GH83922@FreeBSD.org> <200601252230.14279.max@love2party.net> <20060125213953.GI83922@cell.sick.ru> <20060125220900.GJ25397@cirb503493.alcatel.com.au> <20060125221529.GJ83922@cell.sick.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060126011648.GL25397>