From owner-freebsd-current@FreeBSD.ORG Fri Oct 1 01:14:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D23416A4CE for ; Fri, 1 Oct 2004 01:14:58 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E66EC43D46 for ; Fri, 1 Oct 2004 01:14:57 +0000 (GMT) (envelope-from scottl@FreeBSD.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i911FnY1075011; Thu, 30 Sep 2004 19:15:50 -0600 (MDT) (envelope-from scottl@FreeBSD.org) Message-ID: <415CAF59.5070107@FreeBSD.org> Date: Thu, 30 Sep 2004 19:14:01 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040831 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tristan References: <20041001093515.5cd51b2d@rhino> <20041001005227.GA28811@electra.cse.Buffalo.EDU> <20041001102816.5b14b79f@rhino> In-Reply-To: <20041001102816.5b14b79f@rhino> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@FreeBSD.org Subject: Re: ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=xxx X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Oct 2004 01:14:58 -0000 Tristan wrote: > On Thu, 30 Sep 2004 20:52:27 -0400 > Ken Smith wrote: > >>On Fri, Oct 01, 2004 at 09:35:15AM +0930, Tristan wrote: >> >> >>>FreeBSD 6.0-CURRENT with GENERIC kernel built 27th Sep. >>>On a SunBlade 100 I see these messages regularly when >>>dma is enabled. The messages go away when I either use >>>atacontrol to set the mode to PIO4 or set hw.ata.ata_dma to 0 >>>I do get data corruption on the disk if left in DMA mode. >> >>Just FYI my primary test machine is a SunBlade 100, it seems to >>be doing OK with a kernel built from this morning's source. I've >>been doing most of my builds from an NFS server though, I'll do >>a check with a full buildworld which will use the local drive more. >> >> >>>ad0: 14594MB [29651/16/63] at ata2-master UDMA66 >>>acd0: CDRW at ata2-slave PIO4 >>>ata3-master: DMA limited to UDMA33, non-ATA66 cable or device >>>ad1: 39266MB [79780/16/63] at ata3-master UDMA33 >>>Mounted root from ufs:/dev/ad0a. >> >>Is the data corruption spread across both drives, or just ad1? That >>message about the cable or device being limited could be a clue. > > > nope, its only on ad0. ad1 seems to be fine, however it is hardly used. What happens if you remove the CDROM from the ad0 chain? Scott