From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 10 06:20:59 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A557616A4CE for ; Tue, 10 Aug 2004 06:20:59 +0000 (GMT) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E20E43D1F for ; Tue, 10 Aug 2004 06:20:59 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1BuQ0H-00003A-V7; Tue, 10 Aug 2004 09:20:57 +0300 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: "Julian Stacey" In-reply-to: Your message of Mon, 09 Aug 2004 21:05:19 +0200 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Aug 2004 09:20:57 +0300 From: Danny Braniss Message-Id: <20040810062059.5E20E43D1F@mx1.FreeBSD.org> cc: hackers@freebsd.org Subject: Re: how to logically disable memory X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Aug 2004 06:20:59 -0000 > Reference: > > From: Danny Braniss > > Date: Mon, 09 Aug 2004 12:43:24 +0300 > > Message-id: <20040809094325.6F8D443D1F@mx1.FreeBSD.org> > > Danny Braniss wrote: > > hi, > > is there an 'easy' way to mark some memory as unusable? > > thanks, > > danny > > You'll hopefully get a better answer than mine, but in case you don't > & need to start hacking code ... > > Way back on 2.2.8 I disabled all above 16M 'cos one certain manufacturers > mboard failed to cache & board went slower with more ram ! > > Can't remember much now, & doubtless patch doesnt apply now (& that > 486 board not in service regularly) but it might give a clue where > to look, looking at > > http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/gen/sys/i386/i386/machdep.c.maxmem.diff.ignore > > back then it seemed to be MAXMEM in sys/i386/i386/machdep.c Hi, The short version: I need to disable 'some' physical memory, it's bad, and so far can't find it to change it :-). The long version: this is an IBM Thinkpad X40, quiet new, that lost it's warranty because somehow 'some liquid' was spilled on the keyboard. It seems to have some 512M of memory on the motherboard, which after an almost total dissasembly could not find. Windows crashes too often, but FreeBSD is doing fine. So if i can just disable parts of it (memtest has found the bad memory) then this is a neat notebook. danny