From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 29 16:57:43 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC2D816A4CE for ; Fri, 29 Oct 2004 16:57:43 +0000 (GMT) Received: from beer.ux6.net (beer.ux6.net [64.62.253.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id C797943D2D for ; Fri, 29 Oct 2004 16:57:43 +0000 (GMT) (envelope-from miha@ghuug.org) Received: from [64.62.253.84] (helo=m) by beer.ux6.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CNa4H-000I9K-PK for freebsd-hackers@freebsd.org; Fri, 29 Oct 2004 09:57:41 -0700 From: "Mikhail P." To: freebsd-hackers@freebsd.org Date: Fri, 29 Oct 2004 16:57:33 +0000 User-Agent: KMail/1.7 References: <200410081937.15068.miha@ghuug.org> <200410291044.34973.soralx@cydem.org> <200410291650.27058.miha@ghuug.org> In-Reply-To: <200410291650.27058.miha@ghuug.org> Organization: Ghana Unix Users Group MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410291657.33606.miha@ghuug.org> X-Spam-Score: -4.9 (----) X-Spam-Report: Spam detection software, running on the system "beer.ux6.net", hasmessageblock similar future email. If you have any questions, see the administrator of that system for details.>with > FreeBSD4 do work well together without a glitch. Actually not only seagates.. similar happened on a 200GB Western Digital drive to me, FreeBSD-5.3. [...] Content analysis details: (-4.9 points, 6.0 required) pts rule name description --------------------------------------------------1% [score: 0.0000] Subject: Re: ad0: FAILURE - WRITE_DMA X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: miha@ghuug.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 16:57:44 -0000 On Friday 29 October 2004 16:50, Mikhail P. wrote: > Perhaps it is only Seagate <-> FreeBSD5-related. Same drives, but with > FreeBSD4 do work well together without a glitch. Actually not only seagates.. similar happened on a 200GB Western Digital drive to me, FreeBSD-5.3. regards, M.