From owner-freebsd-alpha Sun Mar 4 12:39:21 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 79FCD37B719 for ; Sun, 4 Mar 2001 12:39:18 -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 MAA31780; Sun, 4 Mar 2001 12:39:16 -0800 Date: Sun, 4 Mar 2001 12:39:14 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Soren Schmidt Cc: alpha@FreeBSD.ORG Subject: Ah! Source of ATA-alpha wierdness solved... In-Reply-To: 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 This happens after a panic which had reset the ad device to be PIO4... the reboot that followed probed: ... ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x10280 ata0: mask=03 status0=50 status1=00 ata0: mask=03 ostat0=50 ostat2=00 ata0-master: ATAPI probe a=00 b=00 ata0-slave: ATAPI probe a=00 b=00 ata0: mask=03 status0=50 status1=00 ata0-master: ATA probe a=01 b=a5 ata0: devices=01 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x10288 ata1: mask=00 status0=ff status1=ff ata1: probe allocation failed Trying Read_Port at 203 .... but got ata0-master: ata_command: timeout waiting for intr ata0-master: identify failed instead of the expected: ata0-master: success setting WDMA2 on CMD chip Creating DISK ad0 Creating DISK wd0 ad0: ATA-4 disk at ata0-master ad0: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 ad0: 3098MB [6296/16/63] at ata0-master WDMA2 which, ho ho ho, caused the root filesystem to be mounted from da0 instead of ad0 so things look 'almost' okay (but I'm now running my -current instead of -stable system...) *sputter*.... 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? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message