From owner-freebsd-alpha  Tue Sep  5 11: 2:14 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id 9CE7137B43E
	for <alpha@FreeBSD.ORG>; Tue,  5 Sep 2000 11:02:12 -0700 (PDT)
Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71])
	by feral.com (8.9.3/8.9.3) with ESMTP id LAA19351;
	Tue, 5 Sep 2000 11:02:07 -0700
Date: Tue, 5 Sep 2000 10:58:38 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: John Baldwin <jhb@pike.osd.bsdi.com>,
	Doug Rabson <dfr@nlsystems.com>, alpha@FreeBSD.ORG
Subject: Re: what was the last patch you sent out?
In-Reply-To: <14773.13354.558395.851135@grasshopper.cs.duke.edu>
Message-ID: <Pine.LNX.4.21.0009051057290.11930-100000@zeppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


This kind of stuff is tough to debug- it's just a the point
where things are getting rewired, so even printfs are problematic.

Since the '-fl' argument is broken, and BREAKS don't work to get you out of
where you are, it's a lot of getting up and hitting the reset button.


> 
> Matthew Jacob writes:
>  > > Matthew Jacob wrote:
>  > > > 
>  > > > Thanks... I'll be doing some cleanups && testing today && tomorrow for pci164
>  > > > (so I can get farrago booting again), rawhide && turbolaser...
>  > > 
>  > > Hmm, Peter said last night that his PC164 was booting fine under current
>  > > -current.
>  > 
>  > Gee, I dunno. I just updated to top of tree and it's still broken for me.
> 
> Does Peter have 164LX, 164SX.  Or does he have a 164<flat> like Matt?
> 
> Drew
> 
> 



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