From owner-freebsd-usb@FreeBSD.ORG Mon Feb 9 17:36:53 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 373E4495 for ; Mon, 9 Feb 2015 17:36:53 +0000 (UTC) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE32222A for ; Mon, 9 Feb 2015 17:36:52 +0000 (UTC) Received: by mail-wi0-f177.google.com with SMTP id bs8so5777909wib.4 for ; Mon, 09 Feb 2015 09:36:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:reply-to:mime-version:content-type :content-transfer-encoding; bh=O3ZyU1I0tzU9SK31B5+lEi2hnhpamqpFIqp/8AKZkrI=; b=REcjq+RUt7EPZehcasb9+kLWDPOwE0YfgCUeag0/YIq/1JjWJKisbyRVJ72VfjmnUF Pz216g/AywoFZSPz0SkNL5RoukXPJPUJKmexQ62sE6K94y75d506AIK2C0gaAEv74YyK 9pmGIt2y/KIN8Xk+TIpuBBiRb05g9g1g9jgsJO8sY+fjE+HGMN5tihi+w5dPi2jM00xk LcnfkfgUpqkAEP+aSZkRBRF2bhp9iZl5VQJWP5B1a0+qeksHiEPLJ2GVpDK2IXAqHPt4 UEoe2P49pZW7WMFoiYqr3uHu3GZts2bdS1NKKru1crP59qsYc5m7bftpL7LOtGK3vLhk iUmg== X-Received: by 10.180.205.243 with SMTP id lj19mr37741557wic.26.1423503411320; Mon, 09 Feb 2015 09:36:51 -0800 (PST) Received: from ernst.home (p578E2B47.dip0.t-ipconnect.de. [87.142.43.71]) by mx.google.com with ESMTPSA id fm10sm15335058wib.7.2015.02.09.09.36.49 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 09 Feb 2015 09:36:50 -0800 (PST) Date: Mon, 9 Feb 2015 18:36:48 +0100 From: Gary Jennejohn To: usb@freebsd.org Subject: r276717 causes problems Message-ID: <20150209183648.7825eee5@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 17:36:53 -0000 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: 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. -- Gary Jennejohn