From owner-freebsd-current@FreeBSD.ORG Thu Dec 28 04:26:41 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D88AB16A407 for ; Thu, 28 Dec 2006 04:26:41 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 772B713C474 for ; Thu, 28 Dec 2006 04:26:41 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 5718 invoked by uid 399); 28 Dec 2006 04:26:39 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 28 Dec 2006 04:26:39 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <4593477D.7020509@FreeBSD.org> Date: Wed, 27 Dec 2006 20:26:37 -0800 From: Doug Barton Organization: http://www.freebsd.org/ User-Agent: Thunderbird 1.5.0.8 (X11/20061215) MIME-Version: 1.0 To: Chuck Swiger References: <459310D6.3070107@FreeBSD.org> <459315F0.3060809@mac.com> In-Reply-To: <459315F0.3060809@mac.com> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, sos@freebsd.org Subject: Re: Lots of READ_BIG errors on my new cd drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 28 Dec 2006 04:26:41 -0000 Chuck Swiger wrote: > Doug Barton wrote: > [ ... ] >> I get a lot of errors that look like this: >> >> acd0: FAILURE - READ_BIG HARDWARE ERROR asc=0x3e ascq=0x02 >> >> On CDs and DVDs that I've recorded on other drives, that I've recorded >> on this drive, and commercial ones. >> >> Any ideas on where to start looking? > > Does toggling: > > hw.ata.ata_dma="0" > > ...in loader.conf make a difference? I think you mean hw.ata.atapi_dma, and no, even with both set to 0, it still gives the same error. > I'd imagine you'd like DMA to work but knowing whether the problem goes > anyway with DMA off is useful to test. For that matter, does a careful > application of compressed air to remove any dust or lint inside the > drive help? It's a brand new laptop, so I can see the lens, and it's not dirty. > Also, is this problem specific to -CURRENT or reproducible elsewhere? I can try 6-stable on the same laptop and get back to you. Doug -- This .signature sanitized for your protection