Date: Thu, 5 Feb 2004 14:21:32 -0500 From: Damian Gerow <dgerow@afflictions.org> To: Kirk Strauser <kirk@strauser.com> Cc: freebsd-current@freebsd.org Subject: Re: -CURRENT barfing on UDMA on Via 8233 Message-ID: <20040205192132.GA11676@afflictions.org> In-Reply-To: <87oesdcqcd.fsf@strauser.com> References: <20040126035539.GP1456@sentex.net> <20040127162251.GA90882@afflictions.org> <87oesdcqcd.fsf@strauser.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <VIA 8233 UDMA100 controller> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040205192132.GA11676>