From owner-freebsd-stable@FreeBSD.ORG Tue Nov 22 04:19:24 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DED2016A41F for ; Tue, 22 Nov 2005 04:19:24 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4519C43D53 for ; Tue, 22 Nov 2005 04:19:23 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp212-204.lns1.adl2.internode.on.net [203.122.212.204]) (authenticated bits=0) by cain.gsoft.com.au (8.13.4/8.13.4) with ESMTP id jAM4JJdk058309 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 22 Nov 2005 14:49:21 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Sean Bruno Date: Tue, 22 Nov 2005 14:49:15 +1030 User-Agent: KMail/1.8.2 References: <1132629660.4202.3.camel@home-desk> <200511221424.54872.doconnor@gsoft.com.au> <1132632286.4202.7.camel@home-desk> In-Reply-To: <1132632286.4202.7.camel@home-desk> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3776466.rzW9nj1IFz"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200511221449.16139.doconnor@gsoft.com.au> X-Spam-Score: 0.05 () FORGED_RCVD_HELO X-Scanned-By: MIMEDefang 2.51 on 203.31.81.10 Cc: freebsd-stable@freebsd.org Subject: Re: VIA 8237 under FreeBSD 4.11 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2005 04:19:25 -0000 --nextPart3776466.rzW9nj1IFz Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 22 Nov 2005 14:34, Sean Bruno wrote: > > In general it will probably work OK until you get an SATA PHY error and > > then the whole PC will lock up because the OS isn't polling the error > > register.. > > Bummer...Is this a general issue of the way 4.X handles SATA? I.e. > Would the ICH5 work any better to your knowledge? 4.x doesn't handle SATA per se, it doesn't really know anything about it=20 unless you try dougb's patches (I think). I would strongly suggest migrating ASAP so you don't get stuck with [more]= =20 poorly supported hardware. Or you could try staying with PATA drives, but it's a losing battle - you w= ill=20 be hard pressed to find a new PC for which the devices are properly=20 supported. (eg stuff like onboard ethernet) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart3776466.rzW9nj1IFz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDgpxE5ZPcIHs/zowRAjcsAKCjKeAt+mkVKAm2oTZYCJsccMERHgCeOTV5 o95ijb0ht3fUr30UeJbSltA= =zEkm -----END PGP SIGNATURE----- --nextPart3776466.rzW9nj1IFz--