From owner-freebsd-questions@FreeBSD.ORG Fri Apr 14 10:05:22 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 0221B16A400 for ; Fri, 14 Apr 2006 10:05:22 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out5.blueyonder.co.uk (smtp-out5.blueyonder.co.uk [195.188.213.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2182243D45 for ; Fri, 14 Apr 2006 10:05:21 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.146] (helo=anti-virus03-09) by smtp-out5.blueyonder.co.uk with smtp (Exim 4.52) id 1FULAl-0001eG-TJ; Fri, 14 Apr 2006 11:05:03 +0100 Received: from [80.192.25.195] (helo=[192.168.0.2]) by asmtp-out1.blueyonder.co.uk with esmtp (Exim 4.52) id 1FULAl-0008Rm-9p; Fri, 14 Apr 2006 11:05:03 +0100 Message-ID: <443F73CE.8060502@dial.pipex.com> Date: Fri, 14 Apr 2006 11:05:02 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.12) Gecko/20060305 X-Accept-Language: en MIME-Version: 1.0 To: Anish Mistry References: <200604131154.07097.mistry.7@osu.edu> In-Reply-To: <200604131154.07097.mistry.7@osu.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org 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: Fri, 14 Apr 2006 10:05:22 -0000 Anish Mistry wrote: >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? > > > Will such a backtrace actually help resolve the no reboot problem? Or will it just provide information about the panic? --Alex