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.50) id 1EbR4Y-0006DS-Ll for garchives@archives.gentoo.org; Sun, 13 Nov 2005 23:15:43 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id jADNETTn026555; Sun, 13 Nov 2005 23:14:29 GMT Received: from amun.rz.tu-clausthal.de (amun.rz.tu-clausthal.de [139.174.2.12]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id jADNAZhn007330 for ; Sun, 13 Nov 2005 23:10:35 GMT Received: from amun.rz.tu-clausthal.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 739A12D0949 for ; Mon, 14 Nov 2005 00:10:35 +0100 (CET) Received: from tu-clausthal.de (hathor.rz.tu-clausthal.de [139.174.2.1]) by amun.rz.tu-clausthal.de (Postfix) with ESMTP id 562202D0927 for ; Mon, 14 Nov 2005 00:10:34 +0100 (CET) Received: from energy.heim10.tu-clausthal.de ([139.174.241.94] verified) by tu-clausthal.de (CommuniGate Pro SMTP 4.3.8) with ESMTP id 9155588 for gentoo-user@lists.gentoo.org; Mon, 14 Nov 2005 00:10:34 +0100 From: "Hemmann, Volker Armin" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: [OT] Disable memory Date: Mon, 14 Nov 2005 00:10:33 +0100 User-Agent: KMail/1.8.92 References: <200511132311.02148.peper@aster.pl> <4377BF88.5040205@exceedtech.net> <200511132357.11178.peper@aster.pl> In-Reply-To: <200511132357.11178.peper@aster.pl> 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-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511140010.33285.volker.armin.hemmann@tu-clausthal.de> X-Virus-Scanned: by PureMessage V4.7 at tu-clausthal.de X-Archives-Salt: 19986966-c6b2-4de1-b8ae-5826ee1d0c6f X-Archives-Hash: 786cf12b753a4da2f870a3b825e7c2ec On Sunday 13 November 2005 23:57, Peper wrote: > > LOL. Could it be bad you think?? If you have two sticks of ram, swap > > them around and see if it fails somewhere else then. If it does, bad > > ram, if not, memtest has a bug. > > I'm not sure how to make it not test it all though. I have also never > > had it lock up. I have tested some really old rigs as well as some new > > ones. > > I think you have misunedstood me. My memory is bad for sure, beacause my PC > freezes between-whiles. Memtest does the same during test 5(block move) > when egamining 1st MB of it(you can set which part of memory you want to > check). And my questions is, how can i disable this first MB from being > used by system? I was thinking of setting ramfs in this 1st MB and then not > using it, but is it possible? > no You could switch the ram sticks if you have several and disable everything above a certain size, but when the error is in the first mb, you could also just throw it away. Ram is cheap at the moment, get new one or RMA the old. Since memtest does not find a lot of errors, there is a big chance, that even more of the ram is defective, you should spare you the trouble. -- gentoo-user@gentoo.org mailing list