Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Apr 2007 12:13:20 -0600
From:      Mike Durian <durian@shadetreesoftware.com>
To:        freebsd-usb@freebsd.org
Subject:   umass0: BBB reset failed, TIMEOUT on internal card reader
Message-ID:  <200704191213.21299.durian@shadetreesoftware.com>

next in thread | raw e-mail | index | archive | help
I just installed a Shuttle PC22 "22-in-1 Card Reader" and get
	umass0: BBB reset failed, TIMEOUT
	umass0: BBB bulk-in clear stall failed, TIMEOUT
	umass0: BBB bulk-out clear stall failed, TIMEOUT
errors without any media inserted.

=46rom dmesg:
umass0: USB2.0 CardReader, rev 2.00/91.44, addr 2
da0 at umass-sim0 bus 0 target 0 lun 0
da0: <USB2.0 CF  CardReader 9144> Removable Direct Access SCSI-0 device
da0: 40.000MB/s transfers
da0: Attempt to query device size failed: NOT READY, Medium not present
da1 at umass-sim0 bus 0 target 0 lun 1
da1: <USB2.0 SM  CardReader 9144> Removable Direct Access SCSI-0 device
da1: 40.000MB/s transfers
da1: Attempt to query device size failed: NOT READY, Medium not present
da2 at umass-sim0 bus 0 target 0 lun 2
da2: <USB2.0 SD  CardReader 9144> Removable Direct Access SCSI-0 device
da2: 40.000MB/s transfers
da2: Attempt to query device size failed: NOT READY, Medium not present
da3 at umass-sim0 bus 0 target 0 lun 3
da3: <USB2.0 MS  CardReader 9144> Removable Direct Access SCSI-0 device
da3: 40.000MB/s transfers
da3: Attempt to query device size failed: NOT READY, Medium not present


=46rom usbdevs -v:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000),=20
VIA(0x0000), rev 1.00
 port 1 powered
 port 2 powered
 port 3 powered
 port 4 powered
 port 5 addr 2: high speed, power 500 mA, config 1, CardReader(0x0500), USB=
2.0
(0x07cc), rev 91.44
 port 6 powered
 port 7 powered
 port 8 powered


It looks like the device is using a Carry WIN II chip.  I believe
the part number for this chip is 0639MMTQM03-07G.  There is also a
smaller ST chip on the board.  Otherwise it is just physical
connectors and discretes.

I suspect umass.c needs a umass_devdescrs entry for this device.
How does one go about determining the necessary proto and quirk
values?

mike




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704191213.21299.durian>