Re: umass1: failed to create xfers

[Thomas Klausner <tk%giga.or.at@localhost>]

On Tue, Jul 05, 2016 at 08:27:54PM +0100, Robert Swindells wrote:
> 
> Thomas Klausner <tk%giga.or.at@localhost> wrote:
> >I've updated to a -current from today, and now three USB disks that
> >attached fine a month ago don't provide any sd* devices any longer.
> >
> >All of them say:
> >
> >umass1 at uhub5 port 2 configuration 1 interface 0
> >umass1: (ID of the disk)
> >umass1: using SCSI over Bulk-Only
> >umass1: failed to create xfers
> >
> >Does umass work for anyone right now?
> 
> Only tried a flash drive but it seems fine to me.
> 
> >(7.99.33/amd64)
> 
> Same.
> 
> This is on a machine that has ohci and ehci.

Ok.

My umass is attaching at uhub5

uhub5 at uhub3 port 1: vendor 8087 product 0024, class 9/0, rev 2.00/0.00, addr 2
uhub5: single transaction translator
uhub5: 6 ports with 6 removable, self powered

which is at uhub3

uhub3 at usb0: vendor 8086 EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered

which is at usb0@ehci0:

ehci0 at pci0 dev 26 function 0: vendor 8086 product 1d2d (rev. 0x06)
ehci0: interrupting at ioapic0 pin 23
ehci0: BIOS has given up ownership
ehci0: EHCI version 1.0
usb0 at ehci0: USB revision 2.0


 Thomas