From owner-freebsd-questions@FreeBSD.ORG Fri Apr 22 09:10:45 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 7DF0A16A4CE for ; Fri, 22 Apr 2005 09:10:45 +0000 (GMT) Received: from mail.arax.md (mail.arax.md [217.26.160.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC0A343D49 for ; Fri, 22 Apr 2005 09:10:44 +0000 (GMT) (envelope-from cezar@arax.md) Received: from qvirtual (helo=mail.arax.md) by mail.arax.md with local-smtp (Exim 4.43 (FreeBSD)) id 1DOuBP-000288-3j for freebsd-questions@freebsd.org; Fri, 22 Apr 2005 12:10:43 +0300 Received: from cezar.arax.md ([217.26.161.51]) by mail.arax.md with esmtp (Exim 4.43 (FreeBSD)) id 1DOuBO-000283-OG for freebsd-questions@freebsd.org; Fri, 22 Apr 2005 12:10:42 +0300 Date: Fri, 22 Apr 2005 12:16:20 +0300 From: arax X-Mailer: The Bat! (v3.0.1.33) Professional X-Priority: 3 (Normal) Message-ID: <966265278.20050422121620@arax.md> To: freebsd-questions@freebsd.org In-Reply-To: <193906655.20050421220412@wanadoo.fr> References: <1212701106.20050421194847@arax.md> <193906655.20050421220412@wanadoo.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re[2]: WRITE_DMA problem again X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: arax List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Apr 2005 09:10:45 -0000 Hello, > arax writes: >> I was just wondering if there's a solution to fix the WRITE_DMA problem. I've >> searched the archives but couldn't find a complete answer to this, >> like why it's happening and what to do about it. I'd appreciate any help. > I had the same problem (same logical device, in fact, and also on > FreeBSD 5.3) and it turned out to be a bad drive. I was able to verify > this by downloading the vendor's standalone test software, booting it on > the server, and running exhaustive tests against the drive. On the full > test, the software hung (whereas it worked fine on the other, identical > drive that I had configured on the system). Since this was a bootable > disk and FreeBSD wasn't even in the system, this ruled out FreeBSD. I > reluctantly replaced the drive (which was only 60 days old or so) with > an identical model, and I've had no problems since. 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. I also remember that some time ago I got into a page, probably at people.freebsd.org where one of the developers stated that there is a problem with ata driver regarding dma on freebsd. It was said there that the workaround is in progress. Unfortunately I forgot where I saw this and can't find it again. I would appreciate any suggestions regarding a workaround of this problem, or at least a confirmation if it is critical or it may be safely ignored. Thanks. -- Regards, Cezar