From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 18 17:46:37 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAF8B16A4CE for ; Thu, 18 Nov 2004 17:46:37 +0000 (GMT) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id B342743D3F for ; Thu, 18 Nov 2004 17:46:36 +0000 (GMT) (envelope-from sean-freebsd@farley.org) Received: from thor.farley.org (6kuwlfjv43igx1no@thor.farley.org [IPv6:2001:470:1f01:290:1::5]) by mail.farley.org (8.13.1/8.13.1) with ESMTP id iAIHkUrR060111; Thu, 18 Nov 2004 11:46:30 -0600 (CST) (envelope-from sean-freebsd@farley.org) Received: from thor.farley.org (localhost [127.0.0.1]) by thor.farley.org (8.13.1/8.13.1) with ESMTP id iAIHkUsq096760; Thu, 18 Nov 2004 11:46:30 -0600 (CST) (envelope-from sean-freebsd@farley.org) Received: from localhost (sean@localhost)iAIHkSi5096757; Thu, 18 Nov 2004 11:46:29 -0600 (CST) (envelope-from sean-freebsd@farley.org) X-Authentication-Warning: thor.farley.org: sean owned process doing -bs Date: Thu, 18 Nov 2004 11:46:28 -0600 (CST) From: Sean Farley X-X-Sender: sean@thor.farley.org To: Sean Welch In-Reply-To: <20041117160137.GA7243@NitroPhys.welchsmnet.net> Message-ID: <20041118114008.H96597@thor.farley.org> References: <20041117160137.GA7243@NitroPhys.welchsmnet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-hackers@freebsd.org Subject: Re: Strange DMA behavior under 5.3-RELEASE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 17:46:37 -0000 On Wed, 17 Nov 2004, Sean Welch wrote: > I originally sent a message about this to the questions list but I've > not received any responses. Possibly the people who could answer my > question do not read that list. Hopefully someone here can help! > > The message in question can be viewed here: > > http://docs.FreeBSD.org/cgi/mid.cgi?20041115000519.GA2127 > > Is anyone else seeing this odd "half way" behavior? The hardware > seems to take the atacontrol command just fine but somehow the mode > isn't being set at boot even though the proper sysctl is set. That is odd. I can see it happening on my old Dell PII. The sysctl only enable DMA capability I believe. It is enabled by default. If you disable it during boot, I would guess you would not be able to set WDMA2 with atacontrol. dmesg: atapci0: port 0x1420-0x142f,0x376,0x170-0x177,0x 3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 atacontrol list: ATA channel 0: Master: ad0 ATA/ATAPI revision 4 Slave: no device present ATA channel 1: Master: acd0 ATA/ATAPI revision 0 Slave: afd0 ATA/ATAPI revision 0 I can later set it to WDMA2 via atacontrol. Also, I get from the Zip drive: ata1-slave: FAILURE - SETFEATURES SET TRANSFER MODE status=1 error=4 Sean -- sean-freebsd@farley.org