From owner-freebsd-hackers Wed Mar 17 11:37: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 5B7A114D3A for ; Wed, 17 Mar 1999 11:36:59 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA47616; Wed, 17 Mar 1999 14:34:32 -0500 (EST) Date: Wed, 17 Mar 1999 14:34:32 -0500 (EST) From: Chuck Robey To: Robert Nordier Cc: crossd@cs.rpi.edu, dillon@apollo.backplane.com, freebsd-hackers@FreeBSD.ORG Subject: Re: KVA size changes in 3.1-stable In-Reply-To: <199903171919.VAA00398@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 17 Mar 1999, Robert Nordier wrote: > Chuck Robey wrote: > > > On Tue, 16 Mar 1999, David E. Cross wrote: > > > > > AUGH! > > > > > > I compiled the /boot/loader from the 4.0 tree CVS-ed a couple of hours ago > > > (we have our own copy which periodically syncs with cvsup.freebsd.org). I > > > tell it to boot *any* kernel, and it just *hangs* (caps lock/scroll lock > > > still works, but nothing else.)... Normally a /boot/loader startup looks > > > something like: > > > /-\|kernel /-\|/... etc you get the idea. > > > > > > this one looks like: > > > > > > /-\|/ (and hangs here) > > > > How long since you last used disklabel to update your bootblocks? Old > > ones will do that (they did for me, using 2.2.6 bootblocks a while > > back). > > I'm really skeptical that the loader problems you experienced had > anything directly to do with the 2.2.6 bootblocks. I have a machine > here, still running 2.2.5-RELEASE, and regularly test loader on > it. To double-check, I just upgraded the bootblocks to 2.2.6, and > loader works fine. I'm not an expert on that part, but I followed instructions I had from Mike (I was aware that a screwup could wreck my machine, so I was very careful) and the first time, it refused to boot the elf kernel. I booted the aout one, got more advice, did the disklabel, tried it again with no further changes, and it worked. Perhaps you're right, it's something else, but you can probably see why I think like I do. I'm not going to go stick the old bootblocks back .... is it possible that something since has changed with the bootblocks, so that the failure I saw wouldn't even occur any more? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message