From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 11:23:22 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 F3E8416A4CE for ; Thu, 5 Feb 2004 11:23:21 -0800 (PST) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 073F743D6D for ; Thu, 5 Feb 2004 11:23:03 -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 C37955D546; Thu, 5 Feb 2004 14:50:38 -0500 (EST) Received: by dementia.afflictions.org (Postfix, from userid 1001) id 7A04F6D42B; Thu, 5 Feb 2004 14:21:32 -0500 (EST) Date: Thu, 5 Feb 2004 14:21:32 -0500 From: Damian Gerow To: Kirk Strauser Message-ID: <20040205192132.GA11676@afflictions.org> References: <20040126035539.GP1456@sentex.net> <20040127162251.GA90882@afflictions.org> <87oesdcqcd.fsf@strauser.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87oesdcqcd.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 19:23:22 -0000 Thus spake Kirk Strauser (kirk@strauser.com) [05/02/04 13:51]: : > Okay, it looks like some UDMA stuff broke sometime between 5.2-R and : > current as of two days ago. I couldn't boot into the system unless in : > 'safe mode', so I booted back into 5.2-R, re-sup'ed, rebuilt, and : > rebooted. Same issue as before: : > : > atapci0: port 0xd400-0xd40f at device 17.1 on pci0 : : The ATA system in 5.x is known to be broken on several chipsets - see : http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/60221 for a relevant PR. 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. The PR (at quick glance) seems to bring up issue with 5.2-RC. It also states that PIO4 mode doesn't work. 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. That's not to say the issues aren't related, but at first glance, they don't seem to be.