From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 12:34:06 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 484C116A4CE for ; Thu, 5 Feb 2004 12:34:06 -0800 (PST) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B7A743D81 for ; Thu, 5 Feb 2004 12:33:39 -0800 (PST) (envelope-from dgerow@afflictions.org) Received: from dementia.afflictions.org (dementia [172.16.0.56]) by pandora.afflictions.org (Postfix) with ESMTP id DD77D5D3DB; Thu, 5 Feb 2004 16:02:22 -0500 (EST) Received: by dementia.afflictions.org (Postfix, from userid 1001) id CDF9C6D42B; Thu, 5 Feb 2004 15:33:16 -0500 (EST) Date: Thu, 5 Feb 2004 15:33:16 -0500 From: Damian Gerow To: Kirk Strauser Message-ID: <20040205203316.GB11717@afflictions.org> References: <20040126035539.GP1456@sentex.net> <20040127162251.GA90882@afflictions.org> <87oesdcqcd.fsf@strauser.com> <20040205192132.GA11676@afflictions.org> <87brodco8c.fsf@strauser.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87brodco8c.fsf@strauser.com> X-Operating-System: FreeBSD 5.2-RC on a i386 X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.5.1i 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 20:34:06 -0000 Thus spake Kirk Strauser (kirk@strauser.com) [05/02/04 14:36]: : > 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. I had -RC on this machine, installed from JPSNAP the day before -RELEASE was, well, released. : > 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 boot : > 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 same : > 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. I'm just finishing up a level 0 dump of all filesystems, and I'm running pretty stable. This isn't surprising, and it's in line with what you saw -- running under PIO4 is stable, UDMA100 is not. Would it be worth it to try to force the system into UDMA66 or UDMA33?