From owner-freebsd-stable@FreeBSD.ORG Wed Jul 23 23:28:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C17DD106566B for ; Wed, 23 Jul 2008 23:28:23 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: from ibctech.ca (v6.ibctech.ca [IPv6:2607:f118::b6]) by mx1.freebsd.org (Postfix) with SMTP id 6F5F58FC2C for ; Wed, 23 Jul 2008 23:28:23 +0000 (UTC) (envelope-from steve@ibctech.ca) Received: (qmail 87233 invoked by uid 89); 23 Jul 2008 23:32:36 -0000 Received: from unknown (HELO ?IPv6:2607:f118::5?) (steve@ibctech.ca@2607:f118::5) by 2607:f118::b6 with ESMTPA; 23 Jul 2008 23:32:36 -0000 Message-ID: <4887BEA9.7060900@ibctech.ca> Date: Wed, 23 Jul 2008 19:28:41 -0400 From: Steve Bertrand User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: ian j hart , freebsd-stable@freebsd.org References: <200807221659.20396.ianjhart@ntlworld.com> <200807232123.52186.ianjhart@ntlworld.com> <20080723220638.GF2010@lava.net> In-Reply-To: <20080723220638.GF2010@lava.net> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: unable to use gmirror on supermicro 5015b-mt X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jul 2008 23:28:23 -0000 Clifton Royston wrote: > On Wed, Jul 23, 2008 at 09:23:52PM +0100, ian j hart wrote: > ... >> As I suspected, no takers :) >> >> "Fix". >> >> In /boot/loader.conf >> >> hw.ata.atapi_dma="0" >> >> This allows kldload without hang. I'm sure that this fix will allow me to >> configure a mirror. I'll post back if I'm wrong. > > OK, but *probably* this is an indicator that you need to either > replace the cable (think you said you've tried that) or replace the > motherboard. If the cable is known-good and the other components are > known-good, and it won't run with DMA on supported hardware, something > is seriously wrong with this particular board and odds are too high > that it will die horribly later. (Not to mention that you'll be > hammering your CPU just to get lousy throughput out of it.) This was the same issue I experienced with the NVidia board that I mentioned in the 'taskqueue timeout' thread last week. As I mentioned thereafter, I used my workstation board (Intel), and everything worked fine (ZFS). I tried then to set up my Windows workstation on the NVidia board, and thereafter found out that it would ONLY operate in PIO(4), no matter what I did. Needless to say, the board was RMA'd, and I have a new Intel board on its way to handle the ZFS file system. > As you said in the other post, you've already spent hours of your > life you won't get back - do you want to sign up for some more hours > further down the road? IMHO, just replace the board. If you are not able to acquire DMA on the disk subsystem, you've lost already. > -- Clifton (suddenly questioning why I'm spending hours on mailing lists today) ...because your systems are running so smoothly, you have to be typing something to justify your office space? ;) Steve