From owner-freebsd-alpha Sun Mar 4 12:53:12 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2C97E37B718 for ; Sun, 4 Mar 2001 12:53:09 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA31822; Sun, 4 Mar 2001 12:53:03 -0800 Date: Sun, 4 Mar 2001 12:53:01 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Soren Schmidt Cc: alpha@FreeBSD.ORG Subject: Re: Ah! Source of ATA-alpha wierdness solved... In-Reply-To: <200103042044.VAA94995@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 4 Mar 2001, Soren Schmidt wrote: > It seems Matthew Jacob wrote: > > > > Then doing an 'init' at the PROM hung, so I needed to power cycle. > > *more sputter*... > > > > Would you consider this an 'alpha' problem? Or would it be reasonable > > after doing the reset for dumping that a shutdown hook for resetting > > completely would be reasonable? > > The ata driver does a reset of all ata/atapi device on boot, so there > is not much more I can do here, the alpha BIOS should have reset/cleared > the chip too shouldn't it ? One would think- boot 'reboot' is considered different than 'boot'. There's some kind of low-level issue here. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message