From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 12:12:19 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 34ABC16A4CE for ; Thu, 5 Feb 2004 12:12:19 -0800 (PST) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54A4B43D78 for ; Thu, 5 Feb 2004 12:11:54 -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 i15KA07m091198; Thu, 5 Feb 2004 14:11:00 -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> From: Kirk Strauser Date: Thu, 05 Feb 2004 14:09:55 -0600 In-Reply-To: <40229B2C.1030005@DeepCore.dk> =?iso-8859-1?q?=28S=F8ren?= Schmidt's message of "Thu, 05 Feb 2004 20:36:12 +0100") Message-ID: <87vfmlb84s.fsf@strauser.com> Lines: 30 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:12:19 -0000 --=-=-= Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable At 2004-02-05T19:36:12Z, S=F8ren Schmidt writes: > I do not known that, in fact I know it works on most chipsets... I'm sure it does, but with all respect, several people on the list have experienced similar problems with various unrelated chipsets. In fact, the PR in reference mentions the same issue on a VIA and an Intel controller. > For above PR, please update to an upto date -current and let me know if > you still have problems. If so please try booting without acpi etc etc.. I no longer have the ability to do so. After running in PIO4 from September through last week, I switched from an Asus P3V4X motherboard with a Pentium 3/933 CPU to an Asus A7V with a Thunderbird 1.4GHz CPU, at which point the problems disappeared completely. Note that the motherboard and CPU were, literally, the only components replaced. I kept the same RAM, cables, power supply, drive, case screws - everything but the mb and CPU. However, as of the day I made the switch (January 27) I was still unable to operate the P3V4X in any UDMA mode with ACPI disabled. I had attempted to run a GENERIC kernel and slow add options to match the config I had been using until I could find which options triggered the problem. My first try was to comment INVARIANTS* and WITNESS*, and that was enough to cause the crashes (even with acpi disabled). I never succeeded in building a non-freezing kernel with any combination of options that didn't include those debugging options (which I presume stabilized the system by making it run more slowly, and therefore less likely to overload the ATA code). =2D-=20 Kirk Strauser --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAIqMY5sRg+Y0CpvERAv/MAJ9aWDBTYYV2Aq9nmGylSrtssdhTRwCgphKM GQjtnPAOA4i/UZfAU7oJOxc= =zEja -----END PGP SIGNATURE----- --=-=-=--