USB mouse not working on 8.0-RELEASE

[Hans Petter Selasky]

On Monday 23 November 2009 19:04:22 Ondřej Majerech wrote:
> Hello,
>
> I've just upgraded my box to 8.0-RELEASE (FreeBSD starlight
> 8.0-RELEASE FreeBSD 8.0-RELEASE #9: Mon Nov 23 17:52:12 CET 2009
> root at starlight:/usr/obj/usr/src/sys/STARLIGHT  i386) via csup'ing to
> RELENG_8_0 and the usual suite of buildworld, buildkernel,
> installkernel, mergemaster -p, installworld, mergemaster.
>
> My USB mouse doesn't work now.  While booting, I can see error
> messages from the USB part of the kernel; the same messages also
> reappear when I disconnect and reconnect the thing.  They read the
> following: (Grabbed from /var/log/messages after having dis- and
> re-connected the mouse.)
>
> Nov 23 18:54:19 starlight kernel: usb_alloc_device:1586: set address 2
> failed (USB_ERR_TIMEOUT, ignored)
> Nov 23 18:54:20 starlight kernel: usb_alloc_device:1624: getting
> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
> Nov 23 18:54:21 starlight kernel: usbd_req_re_enumerate:1539: addr=2,
> set address failed! (USB_ERR_TIMEOUT, ignored)
> Nov 23 18:54:22 starlight kernel: usbd_req_re_enumerate:1553: getting
> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
> Nov 23 18:54:24 starlight kernel: usbd_req_re_enumerate:1539: addr=2,
> set address failed! (USB_ERR_TIMEOUT, ignored)
> Nov 23 18:54:25 starlight kernel: usbd_req_re_enumerate:1553: getting
> device descriptor at addr 2 failed, USB_ERR_TIMEOUT!
> Nov 23 18:54:25 starlight kernel: ugen0.2: <(null)> at usbus0
> (disconnected) Nov 23 18:54:25 starlight kernel: uhub_reattach_port:435:
> could not allocate new device!
>
> The mouse was working without any problems whatsoever on 8.0-RC3 and
> all older FBSD versions that I used.
>
> Other USB devices work as they should, without producing anything
> unusual in dmesg.
>
> So, what's up?  Any clues?

Hi,

This looks like a regression issue. There has been some changes with regard to 
USB legacy support handling. Try disabling USB legacy support in the BIOS or 
try to see if the problem is present in a 9-current kernel.

Thanks for reporting your issue!

--HPS