From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 11:39:43 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 0BD4716A4CE for ; Thu, 5 Feb 2004 11:39:43 -0800 (PST) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AB7C43D6D for ; Thu, 5 Feb 2004 11:39:38 -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 i15Jas7m089874; Thu, 5 Feb 2004 13:37:55 -0600 (CST) (envelope-from kirk@strauser.com) To: Damian Gerow References: <20040126035539.GP1456@sentex.net> <20040127162251.GA90882@afflictions.org> <87oesdcqcd.fsf@strauser.com> <20040205192132.GA11676@afflictions.org> From: Kirk Strauser Date: Thu, 05 Feb 2004 13:36:51 -0600 In-Reply-To: <20040205192132.GA11676@afflictions.org> (Damian Gerow's message of "Thu, 5 Feb 2004 14:21:32 -0500") Message-ID: <87brodco8c.fsf@strauser.com> Lines: 30 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' cc: freebsd-current@freebsd.org Subject: Re: -CURRENT barfing on UDMA on Via 8233 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, 05 Feb 2004 19:39:43 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable At 2004-02-05T19:21:32Z, Damian Gerow writes: > My original post stated that this was working on 5.2-R. This machine was > also working at various points up to 5.1-R, at 5.1-R, and various points > from 5.1-R to 5.2-R. It's just after updating 5.2-R to -CURRENT that it's > been broken. Mine had been working from 5.0-something to about mid-September, then it quit working permanently. I only "fixed" the problem by swapping in a new motherboard/CPU. > The PR (at quick glance) seems to bring up issue with 5.2-RC. It also > states that PIO4 mode doesn't work. At the end, PIO4 was in fact working and solid. It was pretty flaky at the time I filed the PR, but stabilized somewhat afterward. > While my problem is still definitely with ATAng, I'm seeing very different > behaviour, and at different points in the tree, than you. I can't even b= oot > in UDMA, but booting in PIO4 works just fine, even in a heavy load -- load > average at about 6, compiling jdk14, X11-4-libraries, and world at the sa= me > time. My gold standard was running Amanda backup. During regular operation, when in a UDMA mode, I'd see a few intermittent warnings and a rare crash. When I ran Amanda, my system would freeze - every time, guaranteed. The same operations in PIO4 were slow but completely successfully. =2D-=20 Kirk Strauser --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAIptW5sRg+Y0CpvERAtbvAJ9zFpFEYY30l4HaAyCEk1lrvbWmegCghWm+ KOBR6m9wKS5uvHy3dZ5oktY= =77v9 -----END PGP SIGNATURE----- --=-=-=--