From owner-freebsd-hackers Wed Mar 17 13:43:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 5B9FB15376 for ; Wed, 17 Mar 1999 13:43:54 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id QAA08106; Wed, 17 Mar 1999 16:43:15 -0500 (EST) Message-Id: <199903172143.QAA08106@cs.rpi.edu> To: sthaug@nethelp.no Cc: crossd@cs.rpi.edu, dcs@newsguy.com, rnordier@nordier.com, dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: KVA size changes in 3.1-stable In-Reply-To: Message from sthaug@nethelp.no of "Wed, 17 Mar 1999 22:33:35 +0100." <9447.921706415@verdi.nethelp.no> Date: Wed, 17 Mar 1999 16:43:15 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I built the 4.0 loader as follows: > > mkdir /tmp/loader > > cd /tmp/loader > > cvs -d /exports/disk1/cvs/FreeBSD/ncvs checkout src/sys > > cd src/sys/boot > > make > > cd i386/loader > > (some of those paths maybe of, I am doing this from memory ;) > > cp /boot/loader /boot/loader.good > > cp loader /boot/loader > > /bin/sync (x3) > > > > I then reboot the system, and it dies as I said. > > > > Some additional information is that I put the new loader on a floppy, and > > booted that. entering "boot disk1s1a:kernel" would give me an error that > > it could not find the file. "boot disk1s1a:COPYRIGHT" gave me the same > > error ;). Eventually I set currdev and rootdev to disk1s1a: and I was able to > > boot the kernel, it got as far as: > > kernel.kva text=.... [......] > > > > and then locked (this time the keyboard did not respond and I needed to hit the > > reset button. when boot/loader came up this time (again off of floppy), I > > told it to boot disk1s1a:boot/loader.good (after setting currdev and rootdev > > again). and from there I told it to boot the old/non-relocated kernel. I > > have been running that kernel since, but I would greatly enjoy running the > > relocated kernel with larger KVA :) > > > > As somone perviously asked, I did read the CVS log, and made changes to the > > listed files (with the exceptions to the ones I could modify with > > 'options "NKPT=17"' and 'options "NKPDE=254"'.) > > 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. I would like to make the request that the KVA changes be brought back into the -stable kerenel :) -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message