From owner-freebsd-current@FreeBSD.ORG Sun Sep 14 03:03:27 2003 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 3792416A4BF; Sun, 14 Sep 2003 03:03:27 -0700 (PDT) Received: from ns.altadena.net (ns.altadena.net [207.151.161.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F15D43F93; Sun, 14 Sep 2003 03:03:26 -0700 (PDT) (envelope-from pete@ns.altadena.net) Received: from ns.altadena.net (localhost [127.0.0.1]) by ns.altadena.net (8.12.9/8.12.9) with ESMTP id h8EA3PE1099273; Sun, 14 Sep 2003 03:03:25 -0700 (PDT) (envelope-from pete@ns.altadena.net) Received: (from pete@localhost) by ns.altadena.net (8.12.9/8.12.9/Submit) id h8EA3OfB099272; Sun, 14 Sep 2003 03:03:24 -0700 (PDT) From: Pete Carah Message-Id: <200309141003.h8EA3OfB099272@ns.altadena.net> To: current@freebsd.org Date: Sun, 14 Sep 2003 03:03:24 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit Subject: ATAng vs Aladdin chipset 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: Sun, 14 Sep 2003 10:03:27 -0000 ASUS P5A or P5AB (one of each now) - won't boot without setting hw.ata.ata_dma=0. GEOM recognizes the drive itself but then the reads of the disklabels fail with a message that I can't find in the source, about a DMA failure. System then prompts to mount root and nothing I type works. I see looking at the list archive that I'm not the only one with this problem. The message appears 3 times per drive with some seconds between, implying to me that it is (at least) a missing interrupt (or completely missing operation?). If anyone wants I could take the trouble to set up a serial console and capture the output. I suspect that is already done somewhere though. Approx same cvsup time works fine in my laptop running ICH3 chipset. Then again, Intel != Acer :-) At least I figured out a bypass easily... Makes "make world" lots slower but at least works. Other (unrelated?) minor problem in past (don't know if it's still there); acpi timer doesn't work right on this chipset either (ran clock at approx double rate with lots of "went backwards" messages). Appears better now at least on one example (non-ASUS board, though) - at least ntp is happy. -- Pete