Date: Thu, 18 Mar 1999 02:51:30 +0200 (SAT) From: Robert Nordier <rnordier@nordier.com> To: crossd@cs.rpi.edu (David E. Cross) Cc: sthaug@nethelp.no, crossd@cs.rpi.edu, dcs@newsguy.com, rnordier@nordier.com, dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG Subject: Re: KVA size changes in 3.1-stable Message-ID: <199903180051.CAA03803@ceia.nordier.com> In-Reply-To: <199903172143.QAA08106@cs.rpi.edu> from "David E. Cross" at "Mar 17, 99 04:43:15 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903180051.CAA03803>