From owner-freebsd-questions@FreeBSD.ORG Thu Apr 13 15:54:04 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 8585416A401 for ; Thu, 13 Apr 2006 15:54:04 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0979743D49 for ; Thu, 13 Apr 2006 15:54:03 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.4) with ESMTP id k3DGA3Ww019053 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Apr 2006 12:10:09 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-questions@freebsd.org Date: Thu, 13 Apr 2006 11:53:57 -0400 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart71620321.zCWceyRl8F"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200604131154.07097.mistry.7@osu.edu> X-Spam-Status: No, score=-5.5 required=5.0 tests=ALL_TRUSTED,BAYES_50, MYFREEBSD2 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88.1/1396/Thu Apr 13 01:39:53 2006 on mail.united-ware.com X-Virus-Status: Clean Cc: 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 15:54:04 -0000 --nextPart71620321.zCWceyRl8F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 13 April 2006 07:47, Wil Hatfield wrote: > > 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. Do you have a backtrace? =2D-=20 Anish Mistry --nextPart71620321.zCWceyRl8F Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEPnQfxqA5ziudZT0RAgdYAJ0S4E3rPgmnbpLv6YdRhum491hnrgCgryzF swFSPvBh6XXcd76rEBf0KB0= =xfF7 -----END PGP SIGNATURE----- --nextPart71620321.zCWceyRl8F--