From owner-freebsd-alpha Sun Mar 4 12:57:38 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2655237B726 for ; Sun, 4 Mar 2001 12:57:35 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA98240; Sun, 4 Mar 2001 21:57:30 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200103042057.VAA98240@freebsd.dk> Subject: Re: Ah! Source of ATA-alpha wierdness solved... In-Reply-To: from Matthew Jacob at "Mar 4, 2001 12:53:01 pm" To: mjacob@feral.com Date: Sun, 4 Mar 2001 21:57:30 +0100 (CET) Cc: alpha@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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. I'm not sure I parse that sentence correctly, but there is not much I can do from the driver if the device hasn't been setup correctly by the BIOS, be it soft of hard reset.. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message