From owner-freebsd-current Thu Jun 17 13:41:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from par28.ma.ikos.com (par28.ma.ikos.com [137.103.105.228]) by hub.freebsd.org (Postfix) with ESMTP id 6B8A6155A4 for ; Thu, 17 Jun 1999 13:41:41 -0700 (PDT) (envelope-from tich@par28.ma.ikos.com) Received: from [[UNIX: localhost]] ([[UNIX: localhost]]) by par28.ma.ikos.com (8.8.7/8.8.7) id QAA14131; Thu, 17 Jun 1999 16:41:57 -0400 From: Richard Cownie To: "David Schwartz" Subject: RE: 4GB dram Date: Thu, 17 Jun 1999 16:32:12 -0400 X-Mailer: KMail [version 1.1.0] Content-Type: text/plain Cc: References: <000301beb8ff$71b06730$021d85d1@whenever.youwant.to> MIME-Version: 1.0 Message-Id: <99061716415701.14101@par28.ma.ikos.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Jun 1999, David Schwartz wrote: > > It's desperately painful to debug this, because as far as I know the > > only way to get any kernel to boot is to power down the machine, > > physically > > unplug one of the dimms, power up again, install new kernel, power down, > > plug the dimm back in ... If I could fit the kernel on a floppy the > > debugging cycle would be much quicker, but it seems too big for that. > > Setting MAXMEM to 2Gb doesn't allow the kernel to boot? Perhaps there's > something wrong with the way MAXMEM is implemented. > > DS I believe that MAXMEM doesn't work the way it used to - I think the trouble is that getmemsize() now has a nested loop, and the way it looks at Maxmem/MAXMEM doesn't do much to break it out of the outer loop. I would have to try another experiment to be 100% sure that this doesn't work (earlier experiments were confused by the fact that 4 cpu's don't work, so I'm trying to deal with 2 independent problems); and I've given up the machine for now. But I don't think it works. Richard Cownie (tich@ma.ikos.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message