Re: usb issue Macbook Pro VM Fusion

On Friday 27 March 2009, Andreas Tobler wrote:
> Hello,
>
> I run a fbsd current in a vm instance on my MacBook Pro.
>
> Today I did the upgrade to todays sources.
>
> Now I get some annoying warnings from the usb stack:
>
> ----
> FreeBSD 8.0-CURRENT #0 r190475M: Fri Mar 27 22:07:10 CET 2009
>
> andreast_at_deuterium_fbsd.andreas.nets:/export/devel/obj/export/devel/src/sys
>/ANDREAST_amd64 Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: Intel(R) Core(TM)2 Duo CPU     T9300  _at_ 2.50GHz (2496.15-MHz
> K8-class CPU)
>    Origin = "GenuineIntel"  Id = 0x10676  Stepping = 6
>
> Features=0xfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA
>,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS>
> Features2=0x80082201<SSE3,SSSE3,CX16,SSE4.1,<b31>>
>    AMD Features=0x20100800<SYSCALL,NX,LM>
>    AMD Features2=0x1<LAHF>
>    TSC: P-state invariant
> usable memory = 2133323776 (2034 MB)
> avail memory  = 2060926976 (1965 MB)
>
> ...
> uhci0: <Intel 82371AB/EB (PIIX4) USB controller> port 0x2080-0x209f irq
> 18 at device 0.0 on pci2
> uhci0: [ITHREAD]
> usbus0: <Intel 82371AB/EB (PIIX4) USB controller> on uhci0
> ...
> usbus0: 12Mbps Full Speed USB v1.0
> ...
> ugen0.1: <Intel> at usbus0
> uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
> ...
> uhub0: 2 ports with 2 removable, self powered
> ...
> Root mount waiting for: usbus1 usbus0
> Root mount waiting for: usbus1 usbus0
> uhub1: 6 ports with 6 removable, self powered
> Root mount waiting for: usbus0
> usb2_alloc_device:1516: getting device descriptor at addr 2 failed!
> Root mount waiting for: usbus0
> usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed!
> Root mount waiting for: usbus0
> Root mount waiting for: usbus0
> Root mount waiting for: usbus0
> usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed!
> ugen0.2: <> at usbus0 (disconnected)
> uhub_reattach_port:413: could not allocate new device!
> usb2_alloc_device:1516: getting device descriptor at addr 2 failed!
> usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed!
> usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed!
> ugen0.2: <> at usbus0 (disconnected)
> uhub_reattach_port:413: could not allocate new device!
> usb2_alloc_device:1516: getting device descriptor at addr 2 failed!
> usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed!
> usb2_req_re_enumerate:1434: getting device descriptor at addr 2 failed!
> ugen0.2: <> at usbus0 (disconnected)
>
> ----
>
> The last lines above are repeating on the console.
>
> There is no 'known' usb device attached to the port. Means, I have
> nothing attached to the usb ports externally.
>
> If you need the full log, let me know.
>
> What else can I provide to help debugging?

Maybe the VM-ware accidentially reported a USB device and then it removed it. 
I don't know.

There are some sysctl under hw.usb2 which you can turn on.

sysctl hw.usb2 | grep debug

uhub, uhci, and ehci is probably most interesting.

--HPS