Date: Thu, 5 Feb 2004 15:33:16 -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: <20040205203316.GB11717@afflictions.org> In-Reply-To: <87brodco8c.fsf@strauser.com> References: <20040126035539.GP1456@sentex.net> <20040127162251.GA90882@afflictions.org> <87oesdcqcd.fsf@strauser.com> <20040205192132.GA11676@afflictions.org> <87brodco8c.fsf@strauser.com>
index | next in thread | previous in thread | raw e-mail
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?home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040205203316.GB11717>