From owner-freebsd-current@FreeBSD.ORG Wed Jan 25 22:15:32 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A111D16A420 for ; Wed, 25 Jan 2006 22:15:32 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id E979E43D48 for ; Wed, 25 Jan 2006 22:15:31 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id k0PMFUdv017133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 26 Jan 2006 01:15:30 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id k0PMFUW2017132; Thu, 26 Jan 2006 01:15:30 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Thu, 26 Jan 2006 01:15:29 +0300 From: Gleb Smirnoff To: Peter Jeremy Message-ID: <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> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20060125220900.GJ25397@cirb503493.alcatel.com.au> User-Agent: Mutt/1.5.6i Cc: Max Laier , freebsd-current@FreeBSD.org Subject: Re: CURRENT incredibly slow X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2006 22:15:32 -0000 On Thu, Jan 26, 2006 at 09:09:00AM +1100, Peter Jeremy wrote: P> > Since P> >that time it can lose half of its RAM, and I need to disassmble it and P> >push RAM harder into the slot. P> P> More likely, there's some semi-conductive gunge left behind. You P> probably need to disassemble it and give it a good scrub with (eg) P> iso-propyl alcohol. I washed it with ethanol thoroughly the day the wine was poured in. I think that the problem is not in gunge, but in corroded contacts in slot and on RAM. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE