From owner-freebsd-questions@FreeBSD.ORG Fri Nov 26 15:30:30 2004 Return-Path: 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 56D6816A4CE for ; Fri, 26 Nov 2004 15:30:30 +0000 (GMT) Received: from virtual.micronet.sk (smtp-r.micronet.sk [213.215.96.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EFE343D1D for ; Fri, 26 Nov 2004 15:30:27 +0000 (GMT) (envelope-from danger@wilbury.sk) Received: from danger.dnv.dewnet.sk ([213.215.105.189]) by virtual.micronet.sk (8.12.11/8.12.11) with ESMTP id iAQFTqf6096004; Fri, 26 Nov 2004 16:29:55 +0100 (CET) (envelope-from danger@wilbury.sk) Date: Fri, 26 Nov 2004 16:26:22 +0100 From: DanGer X-Mailer: The Bat! (v3.0.1.33) Professional X-Priority: 3 (Normal) Message-ID: <859059364.20041126162622@wilbury.sk> To: Peter Risdon , questions@freebsd.org In-Reply-To: <41A729E1.1060505@circlesquared.com> References: <000001c4d3af$0dd69240$6500a8c0@jupiter> <41A725C2.30204@circlesquared.com> <41A729E1.1060505@circlesquared.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re[2]: WRITE_DMA failures on 5.3 (but NOT on 4.10) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: DanGer List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 15:30:30 -0000 Hi Peter, Friday, November 26, 2004, 2:04:33 PM, you wrote these comments: >>> >>> WARNING : WRITE_DMA UDMA ICRC ERROR >> FAILURE : WRITE_DMA status = 51... blah >>> this continues until i run out of patience. >> >> >> This is a really major problem that has affected every 5.3 and the more >> recent 5.2.1 machines I've operated with largish [1] hard drives. The >> novelty of losing several tens of gigs of data any time a drive gets >> busy wears off fairly quickly. >> >>> >>> the advice i received was : >> >> >> ... mainly about checking hardware, and this is _not_ the issue. I've >> googled extensively on this and, as you did, replaced every hardware >> component in the IDE lines, including the disk drives, without affecting >> the problem. >> >> So far as I can make out, there was a change to default settings at some >> point (I haven't scoured the CVS repository to find out exactly when) to >> enable DMA because some newer drives require this[2]. >> > No - apologies for wasting bandwidth. I got to this stage of research > very late a couple of nights ago and see I should have stopped a few > hours earlier. Looking again, this: > hw.ata.atapi_dma: 0 > in loader.conf might fix the problem with atapi drives but the > hw.ata.ata_dma: 1 > sysctl setting seems to have been the default in 4.10 too, so that can't > be it. > I think I might try turning off ata dma in a 5.3 system anyway, and > putting a big drive under load to see what happens, but I fear I'm > probably back to square one. > Peter. i have the same issue on brand new 200gb ata maxtor hard drive. i had the same issue on 5.2.1, but when i upgraded to 5.3 i decided to turn on ata dma but after 9 days of uptime it froze..no logs, whatever...so i turned ata dma off for now, and i will stay and watch what will happen.. but there should be some other fix, because i don't want to keep my disc in pio mode :/ -- Best Regards, +----------==/\/\==----------+ (__) FreeBSD | DanGer | \\\'',) The | DanGer@IRCnet ICQ261701668 | \/ \ ^ Power | http://danger.homeunix.org | .\._/_) To +----------==\/\/==----------+ Serve [ "Sometimes out big splashes are just ripples in the pool" ]