On Tue, 23 Feb 2016 11:48:51 -0500 (EST) Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > I don't see any crash in that photo. Sorry. By "crash" I mean "unable to use the keyboard". Maybe I used the wrong term. > Also, it looks like the log results in this run were different from > what you posted before. Earlier you had "usbhid 3-1.6:1.0: post reset > hid_start_in -> -22" but the photo shows "usbhid 3-1.3:1.1: post reset > hid_start_in -> 0" (I think -- the photo is hard to read). > > So either the mouse is plugged into a different port and is behaving > differently, or else the photo shows the results for a different > device, which isn't very useful. Maybe is the mobile phone I left plugged for transferring photos. I'll remove it completely when doing the tests. > Let's forget about trying to trace into the USB core and instead trace > just the usbhid driver. Ok, another Call Trace. These are the best pictures I took (just the second is not so good) and this is the maximum I can go back in the scroll buffer. I hope it's clear enough. You can click on the thumbnail to expand the picture. 1) http://imgur.com/4c5rkex 2) http://imgur.com/vu6xet2 3) http://imgur.com/84aX3IE 4) http://imgur.com/i0p6Uaf 5) http://imgur.com/CnVbGmn -- 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
