From owner-freebsd-usb@FreeBSD.ORG Mon Feb 9 21:31:39 2015 Return-Path: Delivered-To: usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0E77F646 for ; Mon, 9 Feb 2015 21:31:39 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DB670215 for ; Mon, 9 Feb 2015 21:31:38 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-54-116-245.nwrknj.fios.verizon.net [173.54.116.245]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id F080FB926; Mon, 9 Feb 2015 16:31:37 -0500 (EST) From: John Baldwin To: Hans Petter Selasky Subject: Re: r276717 causes problems Date: Mon, 09 Feb 2015 16:31:32 -0500 Message-ID: <4020134.66atlK9cJ0@ralph.baldwin.cx> User-Agent: KMail/4.14.2 (FreeBSD/10.1-STABLE; KDE/4.14.2; amd64; ; ) In-Reply-To: <54D92612.6000207@selasky.org> References: <20150209183648.7825eee5@ernst.home> <54D92612.6000207@selasky.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 09 Feb 2015 16:31:38 -0500 (EST) Cc: usb@freebsd.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 21:31:39 -0000 On Monday, February 09, 2015 10:26:42 PM Hans Petter Selasky wrote: > Hi John, > > Do all PCI busses support 64-bit DMA busmaster? Do we reflect this in > the busdma tags passed down to device drivers? Yes, barring weird quirks. Even pre-PCI-e had a way to support 64-bit addresses for cards on a 32-bit bus using dual address cycles. Gary, do you only have problems with xhci and not other PCI devices in your system? > --HPS > > On 02/09/15 18:36, Gary Jennejohn wrote: > > r276717 breaks access to my 4-disk external USB3 (XHCI) enclosure. > > > > The symptom is that only the first of the threee disks is found. > > > > r276716 sees all the disks immediately. > > > > This is the output for the bridge chip: > > > > umass0: > 2> on usbus0 > > > > The problem seems to be mainly due to setting dma_bits to 64. It's > > true that the chip on the controller board supports 64 bit DMA, but the > > JMicron seems to have a real crisis when that setting is used, although > > I don't know why. > > > > Note that the nice output above was obtained after hard coding dma_bits > > to 32 in xhci_init(). With 64 bits I see this: > > > > umass0: > > on usbus0 > > > > probably because reading the strings from the device fails. > > > > Anyway, it would be nice to have a sysctl to force dma_bits to 32. > > > > Unfortunately, I still have a problem with my enclosure with more > > current versions of HEAD. The rather questionable practice of > > always doing a multi LUN enquiry using the SCSI-3 CDB byte 0xa0 > > also causes problems. Considering that most of these bridge > > chips can barely emulate SCSI-2 it seems rather foolish to try to > > jam SCSI-3 CDB bytes down their throats. > > > > But that's a different story. -- John Baldwin