From owner-freebsd-hackers Wed Mar 17 16:55: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ceia.nordier.com (m2-2-dbn.dial-up.net [196.34.155.66]) by hub.freebsd.org (Postfix) with ESMTP id A6197152B7 for ; Wed, 17 Mar 1999 16:54:57 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id CAA03803; Thu, 18 Mar 1999 02:51:32 +0200 (SAT) From: Robert Nordier Message-Id: <199903180051.CAA03803@ceia.nordier.com> Subject: Re: KVA size changes in 3.1-stable In-Reply-To: <199903172143.QAA08106@cs.rpi.edu> from "David E. Cross" at "Mar 17, 99 04:43:15 pm" To: crossd@cs.rpi.edu (David E. Cross) Date: Thu, 18 Mar 1999 02:51:30 +0200 (SAT) Cc: sthaug@nethelp.no, crossd@cs.rpi.edu, dcs@newsguy.com, rnordier@nordier.com, dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > My experience, after trying this today: It worked fine here. What I did, > > on a 3.1-STABLE system (Compaq Proliant 3000), was: > > > > - Use the dg patched conf/Makefile.i386 conf/kernel.script include/pmap.h > > from 4.0-CURRENT. > > - Build new kernel, attempt to boot. Stops in loader with an error message > > I didn't write down, unfortunately. (But this was expected - dg's commit > > message explicitly mentioned the need for new boot blocks.) > > - Install boot1 boot2 loader from a 4.0-CURRENT system - these had been > > generated during a "make buildworld" on March first. > > > > And presto, it booted. Been running fine for 6 hours so far. The reason > > I wanted the larger KVA is that this machine has 576 MB memory, and I'm > > wondering if some unexplained hangs and reboots we've had could be due > > to the KVA size. > > Ok... I think I will stop causing spam to -hackers over this. I had been using > 3.1-stable's boot1/boot2 with the 4.0 boot loader (and assumed it was OK, I > thought once /boot/loader took over, it was working). I will pound on this > myself for awhile and see where it goes. Just as info: there are absolutely no differences (source code or binaries) between the -stable and -current boot1/boot2. I've been keeping the code identical deliberately. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message