From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1E7c3M-0008T6-7s for garchives@archives.gentoo.org; Tue, 23 Aug 2005 16:55:12 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7NGrSVS010890; Tue, 23 Aug 2005 16:53:28 GMT Received: from selket.rz.tu-clausthal.de (selket.rz.tu-clausthal.de [139.174.2.37]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7NGmcWF006292 for ; Tue, 23 Aug 2005 16:48:38 GMT Received: from selket.rz.tu-clausthal.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 44B1C28C935 for ; Tue, 23 Aug 2005 18:49:32 +0200 (CEST) Received: from tu-clausthal.de (hathor.rz.tu-clausthal.de [139.174.2.1]) by selket.rz.tu-clausthal.de (Postfix) with ESMTP id 3736528C8ED for ; Tue, 23 Aug 2005 18:49:25 +0200 (CEST) Received: from energy.heim10.tu-clausthal.de ([139.174.241.94] verified) by tu-clausthal.de (CommuniGate Pro SMTP 4.3.6) with ESMTP id 7268855 for gentoo-user@lists.gentoo.org; Tue, 23 Aug 2005 18:49:24 +0200 From: Volker Armin Hemmann To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] gcc seg faults very often Date: Tue, 23 Aug 2005 18:49:24 +0200 User-Agent: KMail/1.8.2 References: <8f7a9d5805082210274ab0ea25@mail.gmail.com> <8f7a9d580508230603931d8d8@mail.gmail.com> <430B3AA5.4020404@internode.on.net> In-Reply-To: <430B3AA5.4020404@internode.on.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508231849.24563.volker.armin.hemmann@tu-clausthal.de> X-Virus-Scanned: by PureMessage V4.7 at tu-clausthal.de X-Archives-Salt: 91b5b369-e9da-47f9-b1c3-0ef56b856c0f X-Archives-Hash: 09d14b994029760f30abd5e100d08536 On Tuesday 23 August 2005 17:03, Eugene Rosenzweig wrote: > > You can check memory settings in the BIOS, most BIOSes nowadays have > options to change memory timings so you can set more relaxed ones and > see if the errors disappear. Also you can try good oldfashioned > re-seating of the memory modules, take them out and insert them again. > and if the errors stay with new ram, try a new PSU ;) -- gentoo-user@gentoo.org mailing list