Josip, this is a different issue from the one addressed with the patch. 1) Can you try it on a 3.2 kernel ? 2) The problem you describe, does it happen all the time ?
Thanks, Nestor. On Sun, Sep 23, 2012 at 12:23 PM, Josip Rodin <j...@debbugs.entuzijast.net>wrote: > On Fri, Sep 21, 2012 at 12:21:34PM +0200, Nestor Lopez Casado wrote: > > This patch fixes an issue introduced after commit 4ea5454203d991ec > > > > After that commit, hid-core silently discards any incoming packet > > that arrives while any hid driver's probe function is being executed. > > I managed to test this now, on top of Linux 3.5, but it didn't fix my > keyboard. I still get the same sequence of messages with hid.debug=1: > > +usb 5-2: new full-speed USB device number 3 using ohci_hcd > +drivers/hid/usbhid/hid-core.c: HID probe called for ifnum 0 > +drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 0 > +drivers/hid/hid-logitech-dj.c: logi_dj_probe: ignoring ifnum 0 > +drivers/hid/usbhid/hid-core.c: HID probe called for ifnum 1 > +drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 1 > +drivers/hid/hid-logitech-dj.c: logi_dj_probe: ignoring ifnum 1 > +drivers/hid/usbhid/hid-core.c: HID probe called for ifnum 2 > +drivers/hid/hid-logitech-dj.c: logi_dj_probe called for ifnum 2 > +drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report > wValue=0x0110 wIndex=0x0002 wLength=7 > +drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report > wValue=0x0111 wIndex=0x0002 wLength=20 > +drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report > wValue=0x0120 wIndex=0x0002 wLength=15 > +drivers/hid/usbhid/hid-core.c: submitting ctrl urb: Get_Report > wValue=0x0121 wIndex=0x0002 wLength=32 > +logitech-djreceiver 0003:046D:C52B.0005: claimed by neither input, hiddev > nor hidraw > +logitech-djreceiver 0003:046D:C52B.0005: logi_dj_probe:hid_hw_start > returned error > > -- > 2. That which causes joy or happiness. >
