From owner-freebsd-usb@FreeBSD.ORG Sun Mar 11 23:01:06 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 75591106564A; Sun, 11 Mar 2012 23:01:06 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id E685B8FC08; Sun, 11 Mar 2012 23:01:05 +0000 (UTC) Received: by yhgm50 with SMTP id m50so2366372yhg.13 for ; Sun, 11 Mar 2012 16:01:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=g9X9Wp2CdZLKMWbU2wA9shmSYb0RR6aHuOJhtiCr0OU=; b=0QmAgxXeeShLIZ54pbkG3VvQ8zQoagFgAFpvhjOWx7UGIxrkZBkBtR7N/nXnzoqV8B 3outNvo92HfByRHbaVm3WPIUtwjFW/GstWsJntX4IvSjl/jXhW6MbUUReZHLtdBqt/15 /ai93tm9aX/PryQJeiZnX30NsnWZC+eudfpKyOClC2Q8smhyBYSqWPBr+kZurLfuN1NB Sry7KtaquQ3U/JHm0aK7DcvyzH+p6Mdi55uAwUuuhpTA7GC37q0e7FBEpkRUAqomsp7Z CdNRRz61qi86SDHN9sYIkL38+RhYfaRt3ns18G6mnpD6WureAincFiLThFf9iZjhoR5S TD1w== MIME-Version: 1.0 Received: by 10.60.24.9 with SMTP id q9mr4256028oef.4.1331506865404; Sun, 11 Mar 2012 16:01:05 -0700 (PDT) Received: by 10.60.17.10 with HTTP; Sun, 11 Mar 2012 16:01:04 -0700 (PDT) Date: Sun, 11 Mar 2012 18:01:04 -0500 Message-ID: From: Brandon Gooch To: freebsd-usb@freebsd.org Content-Type: multipart/mixed; boundary=e89a8ff1c4e2ba7cf804baff9918 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Alexander Motin , Hans Petter Selasky , Nathan Whitehorn Subject: Ongoing battle with umass(4) and xhci(4) X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Mar 2012 23:01:06 -0000 --e89a8ff1c4e2ba7cf804baff9918 Content-Type: text/plain; charset=ISO-8859-1 So, I have been (off-and-on) trying to debug issues with my XHCI ports, USB flash drives, eternal USB disk enclosures, and external USB (w/ eSATA) hard drive bays. Seems that some devices just work better than others, but even the devices that do work only do so after considerable time waiting for attachment. Here's an example of this, observed only moments ago: (This e-mail message was originally written March 10 at around 1:30 AM CST) Mar 10 01:24:55 m6500 kernel: ugen1.2: at usbus1 Mar 10 01:24:55 m6500 kernel: umass0: on usbus1 Mar 10 01:24:55 m6500 kernel: umass0: SCSI over Bulk-Only; quirks = 0x0100 Mar 10 01:24:55 m6500 kernel: umass0:6:0:-1: Attached to scbus6 Mar 10 01:25:59 m6500 kernel: (probe0:umass-sim0:0:0:0): Down reving Protocol Version from 2 to 0? Mar 10 01:25:59 m6500 kernel: pass3 at umass-sim0 bus 0 scbus6 target 0 lun 0 Mar 10 01:25:59 m6500 kernel: pass3: < > Fixed Direct Access SCSI-0 device Mar 10 01:25:59 m6500 kernel: pass3: Serial Number EA054327FFFF Mar 10 01:25:59 m6500 kernel: pass3: 40.000MB/s transfers Mar 10 01:25:59 m6500 kernel: GEOM: new disk da0 Mar 10 01:25:59 m6500 kernel: da0 at umass-sim0 bus 0 scbus6 target 0 lun 0 Mar 10 01:25:59 m6500 kernel: da0: < > Fixed Direct Access SCSI-0 device Mar 10 01:25:59 m6500 kernel: da0: Serial Number EA054327FFFF Mar 10 01:25:59 m6500 kernel: da0: 40.000MB/s transfers Mar 10 01:25:59 m6500 kernel: da0: 305245MB (625142448 512 byte sectors: 255H 63S/T 38913C) I've also attached two extracted pieces from /var/log/messages demonstrating two different devices behaving very differently (no surprise there) but very badly. Searching through the mailing list has yielded results of showing individuals having issues with devices attaching on XHCI (and even EHCI), with similar output from the kernel (CAM/SCSI-related stuff). As an example, see [1] below. Interestingly, the XHCI ports have no issues with mice, keyboards, or USB serial adapters -- my Android phone unfortunately falls into the umass(4) category -- so it seems that the ports themselves are sound. And I should add that recent Linux distros (and of course Windows 7) handle every single device that I've had issues with in FreeBSD. Is there something fishy happening between the USB stack and CAM? hmmm... -Brandon [1] http://lists.freebsd.org/pipermail/freebsd-usb/2012-February/011064.html --e89a8ff1c4e2ba7cf804baff9918--