From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 12:45:46 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 D125116A4CE for ; Thu, 5 Feb 2004 12:45:45 -0800 (PST) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1336343D2F for ; Thu, 5 Feb 2004 12:45:16 -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 i15Ki67m092481; Thu, 5 Feb 2004 14:45:07 -0600 (CST) (envelope-from kirk@strauser.com) To: =?iso-8859-1?q?S=F8ren_Schmidt?= References: <20040126035539.GP1456@sentex.net> <20040127162251.GA90882@afflictions.org> <87oesdcqcd.fsf@strauser.com> <40229B2C.1030005@DeepCore.dk> <87vfmlb84s.fsf@strauser.com> <4022A77F.7070207@DeepCore.dk> From: Kirk Strauser Date: Thu, 05 Feb 2004 14:44:04 -0600 In-Reply-To: <4022A77F.7070207@DeepCore.dk> =?iso-8859-1?q?=28S=F8ren?= Schmidt's message of "Thu, 05 Feb 2004 21:28:47 +0100") Message-ID: <87k731b6jv.fsf@strauser.com> Lines: 28 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 20:45:46 -0000 --=-=-= Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable At 2004-02-05T20:28:47Z, S=F8ren Schmidt writes: > Excuse my bluntness but it sounds an awfull lot like bad behaving HW to > me, there has been alot of changes that make certain HW fail, ACPI is one > thin APIC is another. I do understand your point. On the other hand, look at the number of groups.google.com hits for "READ_DMA TIMEOUT". Quite a few people seem to have suddenly developed problems with systems that'd been working fine until recently. > Let me rephrase, if ATA had such severe problems noone would be able to > use it. However I'm sure there are corner cases that has problems, there > always will be, and I'll fix them if possible. I've always been very careful to avoid even the appearance of assigning blame in favor of giving factual problem reports. I understand that you can't possibly test every hardware combination being used. However, I do think that the recent rash of ATA-related problems would seem to indicate that there may be a few general issues that aren't directly related to one exact set of hardware. I do appreciate the work you've done, and I certainly don't want to sound like I'm criticizing, but I've been having problems with my system and I've just been trying to report them as accurately as possible. =2D-=20 Kirk Strauser --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAIqsW5sRg+Y0CpvERArwqAJ4/VFRKHzrRafaWTOEEBGuuzyRXOwCgkHVA oTCfjEcIUhXdCPfitbqc25Y= =LoDu -----END PGP SIGNATURE----- --=-=-=--