2017-11-02 18:18 GMT+01:00 Mathias Nyman <mathias.ny...@linux.intel.com>: > On 02.11.2017 16:31, Juan Simón wrote: >> >> Hi, >> This is the trace output: https://pastebin.com/apt56yGe > > > Thanks > xhci logs look pretty good to me. A interrupt transfer TRB is queued > asking for 32 bytes from the mouse, and mouse replies with 15 bytes. > After this and we immediately queue the next TRB. > > Are you sure this generates the "WARN TRB for slot x ep with no TDs queued"? > can you check dmesg if those really appear? > In the logs we always have a TRB (TD) queued when we receive events. > > The mouse is however constantly responding with 15 bytes of data, > as if it's constantly moving, sending data. > > Not sure how HID devices normally behave, but my guess is that they would > respond with a NAK to the interrupt transfer if no data is pending. > > git bisect would show when it stopped working, could be a change > somewhere else as well, hid maybe? > > -Mathias >
Solved, FYI: https://bbs.archlinux.org/viewtopic.php?pid=1739030#p1739030 https://bugzilla.redhat.com/show_bug.cgi?id=1497861 https://www.spinics.net/lists/kernel/msg2571180.html It seems the problem is in PEAQ_WMI module. I hope it will be resolved in the 4.14 kernel version. Thank you too much for your help. Regards. NOTE: I forward it because the previous one I forgot to send in text format. :-( -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
