From owner-freebsd-questions@FreeBSD.ORG Thu Apr 13 11:47:20 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3B8B16A409 for ; Thu, 13 Apr 2006 11:47:20 +0000 (UTC) (envelope-from freebsd@hyperconx.com) Received: from front.hyperconx.net (ns1.hyperconx.net [65.74.165.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD6B043D5E for ; Thu, 13 Apr 2006 11:47:19 +0000 (GMT) (envelope-from freebsd@hyperconx.com) Received: from adsl-69-225-224-190.dsl.skt2ca.pacbell.net ([69.225.224.190] helo=Production) by front.hyperconx.net with esmtpa (Exim 4.53) id 1FU0IC-0000fX-Br for freebsd-questions@freebsd.org; Thu, 13 Apr 2006 04:47:20 -0700 From: "Wil Hatfield" To: Date: Thu, 13 Apr 2006 04:47:18 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal In-Reply-To: <200604130228.10172.daeg@houston.rr.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Subject: RE: DMA TIMEOUT X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Apr 2006 11:47:21 -0000 > I had a similar situation under 6.0. My secondary drive would > throw DMA read > errors at bootup, adding several minutes to the boot process, so > I ran it in > PIO mode. The upgrade to 6.1 solved it, both drives work fine as DMA now. Looks like the DMA errors are back in 6.1-RC with ATA or at least similar DMA errors. The new one froze my machine with an error like "Error while performing DMA_WRITE command". A new twist to the WRITE_DMA Timeouts of 5.4. I am starting to think that they aren't going to get the ATA issues all worked out anytime soon so they are changing the errors. ;-) And of course no automatic reboot on panic. -- Wil Hatfield