From owner-freebsd-questions@FreeBSD.ORG Fri Apr 22 17:50:43 2005 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 C37FC16A4CE for ; Fri, 22 Apr 2005 17:50:43 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DF2543D3F for ; Fri, 22 Apr 2005 17:50:43 +0000 (GMT) (envelope-from zettabyte@gmail.com) Received: by rproxy.gmail.com with SMTP id z35so768779rne for ; Fri, 22 Apr 2005 10:50:42 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HH+SjqO6rTXU80HIxvdzPEqROfVNnFVvrlCiKC+nxmVkYaqQonNIr2WQlvjnXxWmxnAucHCzJedGnGr4GtzoQx7u6vA/9NRNQuL4rC0RGqNfdz9hEoQlUcvZ4Po4UWkKn9AN5Gdm1uyP0I6bGnTZEV/D/vhB0E34U+4UYazn/U4= Received: by 10.38.92.65 with SMTP id p65mr3775953rnb; Fri, 22 Apr 2005 10:50:42 -0700 (PDT) Received: by 10.38.181.29 with HTTP; Fri, 22 Apr 2005 10:50:42 -0700 (PDT) Message-ID: <86ba954f05042210506af5395b@mail.gmail.com> Date: Fri, 22 Apr 2005 11:50:42 -0600 From: Kendall Gifford To: freebsd-questions@freebsd.org In-Reply-To: <966265278.20050422121620@arax.md> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1212701106.20050421194847@arax.md> <193906655.20050421220412@wanadoo.fr> <966265278.20050422121620@arax.md> Subject: Re: Re[2]: WRITE_DMA problem again X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Kendall Gifford List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 17:50:43 -0000 On 4/22/05, arax wrote: >=20 > Oh, no. Hope that's not true. I jsut finished installing and configure > all the software, it would be a big pain starting over again. So, as > far as I get it, there isn't a definite answer to this issue. You're > suggesting that it's the drive, I saw some threads in the archives > suggesting to apply some patches but they are still under development. > I saw a lot of complaints regarding this write_dma thing, is it > possible that all those people have problems with drives? Who knows? > Maybe. Howdy, I may, or may not, be experiencing the same problem as you. I recently posted on freebsd-hardware yesterday but since I haven't received any response yet, and since I noticed your post, I thought I'd post here as well. In my experience, my drives are fine (in addition to my drives, cables, and motherboard being new, working fine with the FreeBSD 4.x branch, being fine according to smartmontools, they're also fine according to Maxtor's disk diagnostic utility). My previous post gives the details of my situation if you're interested in comparing (or if anyone has info for me): http://groups-beta.google.com/group/muc.lists.freebsd.hardware/browse_threa= d/thread/4fbe97ece78c6d78/55635dcc817dc4c6?rnum=3D1&hl=3Den#55635dcc817dc4c= 6 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=20 hw.ata.ata_dma=3D"0" in /boot/loader.conf . So, from doing a search on the problem, apparently there are those who have hardware at fault and those of us who don't seem to have hardware problems, but who know (I don't). If someone with more knowledge would like to elighten us, it would be much appreciated. -- Kendall Gifford