Date: Tue, 10 Dec 2013 23:41:57 -0500 From: Eitan Adler <lists@eitanadler.com> To: Hans Petter Selasky <hps@bitfrost.no> Cc: "usb@freebsd.org" <usb@freebsd.org> Subject: Re: Unable to attach USB mouse Message-ID: <CAF6rxgm8rFMzpmUKG%2B9JR3m=%2BH48FLT4o0gTh=jUMj7nv75FZA@mail.gmail.com> In-Reply-To: <CAF6rxgn2uMjs3Y6c-eULJWPCSRrdTw4SdZ6Y6ZtytwmA_FOL4A@mail.gmail.com> References: <CAF6rxgn-LvNMYS8o9q9=3-O01vc92Z8A6nf3%2BMe1NvNiT8sGZA@mail.gmail.com> <52847654.8070501@bitfrost.no> <CAF6rxgndwWtWEXYLmjer-7UYOGQ_TcQ3eywepETGGPjuBxsB%2Bw@mail.gmail.com> <5284EB46.7010903@bitfrost.no> <CAF6rxgmo-NzJRHhFWGzZP8qhXGRQR=ogrRk-9Zj9fWSp5jtuMw@mail.gmail.com> <CAF6rxg=Wq3umRfA2d1N5mVzZUv_jM6xt_gZvkJZo=Ped9fGyrg@mail.gmail.com> <5294461D.2070000@bitfrost.no> <CAF6rxgnwb7kwqRp_RLun5Cvi6M=qfPETv=Ks1JwBCNvSv3WT3g@mail.gmail.com> <5294C10D.4000000@bitfrost.no> <CAF6rxgnawJ0-U7i1qaM5fteWXdFU2DuwnyG6O2hFZjQdpj5K1Q@mail.gmail.com> <52A41AC7.9020007@bitfrost.no> <CAF6rxg=r1PW5DHbaWV7H=0BRH99rY23XUAaT7FSsF3o%2BWomtiQ@mail.gmail.com> <52A6BBD2.9050906@bitfrost.no> <CAF6rxgkpXYEsjnHVecB9R8n-Ac49ezhFVpxLxw%2B3wTu8Z3Trkw@mail.gmail.com> <52A76882.6040003@bitfrost.no> <CAF6rxgmiL1hBVbCe4ynxTR9Av9gvXMNqJG0jW-HEi_ei-KF7cg@mail.gmail.com> <52A77830.4070204@bitfrost.no> <52A77D25.7000206@bitfrost.no> <CAF6rxgn2uMjs3Y6c-eULJWPCSRrdTw4SdZ6Y6ZtytwmA_FOL4A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 10, 2013 at 4:02 PM, Eitan Adler <lists@eitanadler.com> wrote: > On Tue, Dec 10, 2013 at 3:44 PM, Hans Petter Selasky <hps@bitfrost.no> wrote: >> On 12/10/13 21:23, Hans Petter Selasky wrote: >>> >>> On 12/10/13 21:16, Eitan Adler wrote: >>>> >>>> On Tue, Dec 10, 2013 at 2:16 PM, Hans Petter Selasky <hps@bitfrost.no> >>>> wrote: >>>>> >>>>> On 12/10/13 19:47, Eitan Adler wrote: >>>>>> >>>>>> >>>>>> [ moving back to the mailing list ] >>>>>> >> >>> >>> Looks like you traced the wrong endpoint. Should be endpoint 0x83. Could >>> you check the other USB's ? >> >> >> Sorry, it was the right endpoint after all, but I don't see any transfer >> errors, so your device is working I assume. > > [ revision: FreeBSD gravity.local 11.0-CURRENT FreeBSD 11.0-CURRENT #6 > r259023: Mon Dec 9 22:22:57 EST 2013 > eitan@gravity.local:/usr/obj/usr/src/sys/EADLER amd64 ] > > So far, yes, everything is working. However, I've seen the errors > above on this revision. I'm not sure what is the exact reason for > when I see them and when I don't. After leaving the system running for a while I see: [90548] uhub_reattach_port: could not allocate new device [90549] usb_alloc_device: set address 2 failed (USB_ERR_IOERROR, ignored) [90549] usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR [90549] usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored) [90549] usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR [90550] usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored) [90550] usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR [90550] usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored) [90550] usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR [90552] usbd_req_re_enumerate: addr=2, set address failed! (USB_ERR_IOERROR, ignored) [90552] usbd_setup_device_desc: getting device descriptor at addr 2 failed, USB_ERR_IOERROR [90552] ugen0.2: <Unknown> at usbus0 (disconnected) [90552] uhub_reattach_port: could not allocate new device I feel like there is something leaking but I'm not sure what. -- Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgm8rFMzpmUKG%2B9JR3m=%2BH48FLT4o0gTh=jUMj7nv75FZA>