From owner-freebsd-stable@FreeBSD.ORG Thu Mar 16 15:55:51 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89E8C16A400 for ; Thu, 16 Mar 2006 15:55:51 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9DC843D6A for ; Thu, 16 Mar 2006 15:55:50 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k2GFtmKs086739; Thu, 16 Mar 2006 08:55:49 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <44198A7F.5030003@samsco.org> Date: Thu, 16 Mar 2006 08:55:43 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rong-En Fan References: <6eb82e0603160732p4bb85504w7d3ef2baec8dd26f@mail.gmail.com> In-Reply-To: <6eb82e0603160732p4bb85504w7d3ef2baec8dd26f@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: stable@freebsd.org Subject: Re: 6.1 ata panic if dma enabled 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: Thu, 16 Mar 2006 15:55:51 -0000 Rong-En Fan wrote: > Hi, > > Recently, we upgrade a 4.11 box to 6.1-BETA2 by reinstall+newfs everything. > After that, we found that if hw.ata.ata_dma=1 at boot, then as soon as it > starts fsck -p, it panics. It happens only if ad0 is setted to UDMA66 or above. > My current solution is set hw.ata.ata_dma=0 in loader.conf and manually > turn DMA on ad0 to UDMA33 and rest ad4~ad7 to UDMA100. In the days of > 4.x, there is something wrong with DMA on ad0, but it will fall back to > PIO4 automatically without problem. We have been tried to 1) change the > cable 2) change from primary ata controller to the second, 3) upgrade to > RELENG_6 as of March 11, but all these are failed. There is no options in > bios to turn off DMA for the onboard ATA controller. Please review the release notes from the 6.1-BETA2 announcement. Fixes went into 6.1 shortly after BETA2 was released, and are in BETA3 and BETA4. Scott