From owner-freebsd-questions@FreeBSD.ORG  Sun Apr 24 20:38:08 2005
Return-Path: <owner-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 8996A16A4CE
	for <freebsd-questions@freebsd.org>;
	Sun, 24 Apr 2005 20:38:08 +0000 (GMT)
Received: from mail22.sea5.speakeasy.net (mail22.sea5.speakeasy.net
	[69.17.117.24])	by mx1.FreeBSD.org (Postfix) with ESMTP id 51DCF43D2F
	for <freebsd-questions@freebsd.org>;
	Sun, 24 Apr 2005 20:38:08 +0000 (GMT)
	(envelope-from freebsd-questions-local@be-well.ilk.org)
Received: (qmail 17755 invoked from network); 24 Apr 2005 20:38:08 -0000
Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org)
	([66.92.78.145])
	(envelope-sender <freebsd-questions-local@be-well.ilk.org>)
	by mail22.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP
	for <cezar@arax.md>; 24 Apr 2005 20:38:07 -0000
Received: by be-well.ilk.org (Postfix, from userid 1147)
	id 0FCC754; Sun, 24 Apr 2005 16:38:06 -0400 (EDT)
Sender: lowell@be-well.ilk.org
To: Cezar Fistik <cezar@arax.md>
References: <1212701106.20050421194847@arax.md>
	<193906655.20050421220412@wanadoo.fr>
	<966265278.20050422121620@arax.md>
	<86ba954f05042210506af5395b@mail.gmail.com>
	<843420889.20050424021338@arax.md>
From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
Date: 24 Apr 2005 16:38:06 -0400
In-Reply-To: <843420889.20050424021338@arax.md>
Message-ID: <44is2bzz9t.fsf@be-well.ilk.org>
Lines: 26
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: freebsd-questions@freebsd.org
Subject: Re: Re[4]: WRITE_DMA problem again
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: freebsd-questions@freebsd.org
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Apr 2005 20:38:08 -0000

Cezar Fistik <cezar@arax.md> writes:

> Hello Kendall,
> 
> Friday, April 22, 2005, 8:50:42 PM, you wrote:
> 
> > Anyhow, my understanding is that the current work-around to this
> > problem is to turn DMA off for your ata drives. I guess this can be
> > done manually with the atacontrol command as I've been doing (though
> > as you'll see in my message linked above, I apparently need to do it
> > differently/sooner). I also understand that you can do so by setting
> > hw.ata.ata_dma="0"  in  /boot/loader.conf  .
> 
> Yes, I saw this suggestion in other posts, too. Well, I gave it a try.
> I disabled dma yesterday and today I got the following:
> 
>  Timecounter "TSC" frequency 498669235 Hz quality 800
>  ad0: 8693MB <IBM-DJNA-370910/J74OA30K> [17662/16/63] at ata0-master PIO4
>  ad0: TIMEOUT - WRITE_MUL retrying (2 retries left) LBA=1573151
>  ad0: FAILURE - WRITE_MUL timed out
> 
> That's something completely new. Does anyone know what that means?

Like the symptoms you got with DMA enabled, it *probably* means you
have *some* kind of hardware problem.  The cable would be a likely
candidate, but I'd definitely be making extra backups if I were you.