From owner-freebsd-current@FreeBSD.ORG Fri Sep 4 19:04:29 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C30271065672 for ; Fri, 4 Sep 2009 19:04:29 +0000 (UTC) (envelope-from webmaster@doghouserepair.com) Received: from smtp104.sbc.mail.mud.yahoo.com (smtp104.sbc.mail.mud.yahoo.com [68.142.198.203]) by mx1.freebsd.org (Postfix) with SMTP id 866828FC1F for ; Fri, 4 Sep 2009 19:04:29 +0000 (UTC) Received: (qmail 11158 invoked from network); 4 Sep 2009 19:04:28 -0000 Received: from unknown (HELO soul.local.inet) (webmaster@69.109.45.163 with plain) by smtp104.sbc.mail.mud.yahoo.com with SMTP; 4 Sep 2009 19:04:28 -0000 X-YMail-OSG: sNCwFA0VM1kuE44YsNThAXZq9HoQ4Pg1YH8V.EledKRABSK.vH7Dv7CoGMCzQuv4NaFAdawz_Qe7Y9UC9uV3BqFwXEeZjO407HmDOCUjXZ0misXUxSSpd.zupuuw6ZrHkg5yvtmGWnGWiFRyPbkzBB2nsOqOPdxslR6.XO8.VSqC8wcZM0NlS47ICpdaXm_qpuox6iVdgG5fIQzXZp3iQ4kyJASlIkT.vArPgDjLFeGF59jkDemMctq74G02eOUhp2S0ECo9xbEWt6zApaVj5ACfV7O8nvXRMWdNWuzLvbTsr1Qp1P8- X-Yahoo-Newman-Property: ymail-3 Message-ID: <4AA164B9.6030806@doghouserepair.com> Date: Fri, 04 Sep 2009 12:04:25 -0700 From: Ryan Rogers User-Agent: Thunderbird 2.0.0.23 (X11/20090825) MIME-Version: 1.0 To: Alexander Motin , freebsd-current@freebsd.org References: <4AA03346.5010608@FreeBSD.org> <4AA09FDF.2010307@doghouserepair.com> <4AA0B8C0.90604@FreeBSD.org> In-Reply-To: <4AA0B8C0.90604@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: non aligned DMA transfer attempted 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: Fri, 04 Sep 2009 19:04:29 -0000 Alexander Motin wrote: > Ryan Rogers wrote: >> Alexander Motin wrote: >>> Ryan Rogers wrote: >>>> I'm having a bit of a problem getting my DVD drive(s) to work >>>> correctly. I'm trying to transfer my DVD collection to my media >>>> server, but whenever I run vobcopy, /var/log/messages gets spammed >>>> with: >>>> >>>> acd0: FAILURE - non aligned DMA transfer attempted >>>> acd0: setting up DMA failed >>>> >>>> I added a bit more information to the first message to see if I >>>> could figure out what was actually going on. request->data was >>>> 0xd40e0c37, ch->dma.alignment was 2, and request->bytecount was 2048. >>> >>> Actually I don't understand what for this check was made there. It is >>> busdma infrastructure business to implement buffer bouncing to manage >>> requested alignment. But this check enforces application level to >>> bother with this. Usually it works fine, as memory often allocated >>> aligned. But probably here is some specifics in your application. >>> Could you try to just to comment-out that request->data check? >> >> I commented out that part of the check, and it worked in the sense >> that it didn't spit out any errors at me, but I'm not 100% certain >> that the data isn't getting corrupted. I tried ripping two discs. >> The first is completely corrupted, the second appears to be fine on >> first glance. I'm going to try a couple more discs to see if maybe the >> first one was just bad. > > Please. > >> Also, one other thing that I noticed that seems odd is this: >> >> acd0: DVDR at ata6-master SATA150 >> .... >> cd0: Removable CD-ROM SCSI-0 device >> cd0: 3.300MB/s transfers >> >> I timed how long the first disc took to rip, and it seems to match >> that reported speed. "Working but slow" is certainly better than "not >> working", but my speeds in Windows using DVD Decrypter on the same >> disk are at least 3 times faster, bursting up to about 5 times faster. > > It's just a small atapicam misfeature. It doesn't translates SATA modes > to CAM speeds. It's only cosmetics, it shouldn't be important. > I've ripped a handful of DVDs since my last post, and I haven't had any error messages, and the output appears to be correct. I even re-ripped the one that had originally been corrupted, and it appears to be fine as well. So, it appears removing that part of the check fixed the issue for me. Ryan