From owner-freebsd-bugs  Sat Mar  6 19:15:42 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from ceia.nordier.com (c2-59-dbn.dial-up.net [196.34.155.187])
	by hub.freebsd.org (Postfix) with ESMTP
	id 078E9152F8; Sat,  6 Mar 1999 19:14:55 -0800 (PST)
	(envelope-from rnordier@nordier.com)
Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id FAA03788; Sun, 7 Mar 1999 05:13:27 +0200 (SAT)
From: Robert Nordier <rnordier@nordier.com>
Message-Id: <199903070313.FAA03788@ceia.nordier.com>
Subject: Re: i386/10433
In-Reply-To: <36E1EA65.73CB0DEB@newsguy.com> from "Daniel C. Sobral" at "Mar 7, 99 11:54:29 am"
To: dcs@newsguy.com (Daniel C. Sobral)
Date: Sun, 7 Mar 1999 05:13:25 +0200 (SAT)
Cc: rnordier@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG, rivers@dignus.com
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-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> I'm not so sure, Robert. The way he described, I think his
> work-around actually means he skips loader, and *that*, not the
> changed irqs, is what let him boots.
> 
> Thomas, if you just enter "0:wd(0,a)/kernel", without configuring
> anything, does it work?
> 
> If, instead, you enter "0:wd(0,a)/boot/loader", does it crashes
> instantly, or does it show any messages first?
> 
> rnordier@FreeBSD.ORG wrote:
> > 
> > Synopsis: After install, can't boot from wd0 - "System halted"
> > 
> > Responsible-Changed-From-To: freebsd-bugs->rnordier
> > Responsible-Changed-By: rnordier
> > Responsible-Changed-When: Sat Mar 6 15:38:09 PST 1999
> > Responsible-Changed-Why:
> > Apparently a new bootblocks problem.

That's a reasonable assumption.  But the register dump shows that
the exception occurred in the function memsize() in boot2.c.

FWIW, there's been what seems to be another instance of the same
bugs reported on -questions ("3.1R install/multiboot problem").

--
Robert Nordier


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message