On Wed, 24 Feb 2016 14:24:44 -0500 (EST) Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > I intended the patch not to cause any call traces, but it did anyway. > So let's drop the questionable code and try something that will be > completely safe. Ok, here's what I got: Feb 24 19:16:41 tux kernel: [ 717.316048] usb 3-1.6: reset full-speed USB device number 6 using ehci-pci Feb 24 19:16:41 tux kernel: [ 717.406163] hid_start_in: urbin (null) Feb 24 19:16:41 tux kernel: [ 717.406171] usbhid 3-1.6:1.0: post reset hid_start_in -> -22 Feb 24 19:16:41 tux kernel: [ 717.468988] usb 3-1.6: reset full-speed USB device number 6 using ehci-pci Feb 24 19:16:41 tux kernel: [ 717.559668] hid_start_in: urbin (null) Feb 24 19:16:42 tux kernel: [ 717.559672] usbhid 3-1.6:1.0: post reset hid_start_in -> -22 Feb 24 19:16:42 tux kernel: [ 718.647957] usb 3-1.6: reset full-speed USB device number 6 using ehci-pci Feb 24 19:16:42 tux kernel: [ 718.738631] hid_start_in: urbin (null) Feb 24 19:16:42 tux kernel: [ 718.738639] usbhid 3-1.6:1.0: post reset hid_start_in -> -22 Feb 24 19:16:42 tux kernel: [ 718.800906] usb 3-1.6: reset full-speed USB device number 6 using ehci-pci Feb 24 19:16:42 tux kernel: [ 718.891666] hid_start_in: urbin (null) Feb 24 19:16:42 tux kernel: [ 718.891683] usbhid 3-1.6:1.0: post reset hid_start_in -> -22 (...) -- Linux 4.4.2-dirty: Blurry Fish Butt http://exchangewar.info -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
