From owner-freebsd-current@FreeBSD.ORG Thu Jan 29 10:17:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E7DC16A50A for ; Thu, 29 Jan 2004 10:17:11 -0800 (PST) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E1C943D5E for ; Thu, 29 Jan 2004 10:17:09 -0800 (PST) (envelope-from kirk@strauser.com) Received: from pooh.strauser.com (pooh.honeypot.net [10.0.5.128]) by kanga.honeypot.net (8.12.10/8.12.10) with ESMTP id i0TIH6gV036430 for ; Thu, 29 Jan 2004 12:17:07 -0600 (CST) (envelope-from kirk@strauser.com) To: freebsd-current@freebsd.org References: <87r7xy5ek2.fsf@strauser.com> From: Kirk Strauser Date: Thu, 29 Jan 2004 12:17:04 -0600 In-Reply-To: <87r7xy5ek2.fsf@strauser.com> (Kirk Strauser's message of "Sat, 17 Jan 2004 17:41:01 -0600") Message-ID: <87znc6bowv.fsf@strauser.com> Lines: 29 X-Mailer: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.65', clamav-milter version '0.60p' Subject: Fixed, indirectly (was Re: ATA still broken, but now differently) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2004 18:17:12 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable At 2004-01-17T23:41:01Z, Kirk Strauser writes: > Well, Thursday's world seems to have broken ATA in a new and interesting > way. Before updating world in mid-September, my drive ran perfectly in > UDMA66 mode. Since that time, the system is absolutely guaranteed to fre= eze > if I run in any mode higher than BIOSPIO. Before two days ago, that meant > getting errors like: > > ad0: TIMEOUT - WRITE_DMA retrying (2 reties left) > ata0: resetting devices > ad0: FAILURE - already active DMA on this device > ad0: setting up DMA failed I eventually found a workaround for the problem that let me run my drive in UDMA66 mode without any crashes: I swapped my Asus P3V4X motherboard with P-2/933 CPU for an Asus A7v motherboard with Thunderbird 1.4 CPU. I kept the same memory, drive, NICs, cables, cases, and everything else, so the mb and CPU were literally the only parts that changed. Anyway, now my system is running perfectly and I'm slowly re-enabling all of the performance options I'd been using before this whole episode started (kern.polling, ATA, "-march" optimization, etc.). =2D-=20 Kirk Strauser "94 outdated ports on the box, 94 outdated ports. Portupgrade one, an hour 'til done, 82 outdated ports on the box." --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAGU4i5sRg+Y0CpvERAv+VAKCizXgTpEI6rUDdNN51XVqC97VpwwCgkzSX VoDyk7/tOBJGc4ogXdnWuXs= =3ztH -----END PGP SIGNATURE----- --=-=-=--