From owner-freebsd-amd64@FreeBSD.ORG  Sun Feb  8 20:40:22 2004
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id B240E16A4CE; Sun,  8 Feb 2004 20:40:22 -0800 (PST)
Received: from tor-adm1.nbc.attcanada.ca (tor-adm1.business.allstream.net
	[207.181.89.5])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 601DF43D1D; Sun,  8 Feb 2004 20:40:22 -0800 (PST)
	(envelope-from taob@risc.org)
Received: from tor-adm1.nbc.attcanada.ca (localhost [127.0.0.1])
	i194eLwH027931;	Sun, 8 Feb 2004 23:40:21 -0500 (EST)
Received: from localhost (ncc0070@localhost)i194eLxB027928;
	Sun, 8 Feb 2004 23:40:21 -0500 (EST)
X-Authentication-Warning: tor-adm1.nbc.attcanada.ca: ncc0070 owned process
	doing -bs
Date: Sun, 8 Feb 2004 23:40:20 -0500 (EST)
From: Brian Tao <taob@risc.org>
X-Sender: ncc0070@tor-adm1.nbc.attcanada.ca
To: James Van Artsdalen <james-freebsd-amd64@jrv.org>
In-Reply-To: <200402081846.i18IkA81000259@bigtex.jrv.org>
Message-ID: <Pine.GSO.4.21.0402082338380.7631-100000@tor-adm1.nbc.attcanada.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-amd64@freebsd.org
Subject: Re: SiImg 3114 was: (FWD) FreeBSD 5.2.1-RC available
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Feb 2004 04:40:22 -0000

On Sun, 8 Feb 2004, James Van Artsdalen wrote:
> 
> Is anyone else having trouble with this?
> 
> The 3114 is found no problem but the drive is not seen.
> The culprit may be this code in ata_reset().

    I haven't had much time to look into this yet, but the i386 port
of 5.2.1-RC2 panics when it attempts to probe the S-ATA devices on my
motherboard (Tyan Tiger K8W S2875).  I haven't tried the amd64 port
yet.
-- 
Brian Tao (BT300, taob@risc.org)
"Though this be madness, yet there is method in't"