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: <JMicron> at usbus1
Mar 10 01:24:55 m6500 kernel: umass0: <MSC Bulk-Only Transfer> 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
_______________________________________________
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

Reply via email to