On Tue, Dec 19, 2017 at 02:51:08PM +0100, Oliver Neukum wrote: > Hi Johan, > > I got a report from a user that their device fails with > > > cdc_acm 2-1.2:1.1: acm_start_wb - usb_submit_urb(write bulk) failed: -22 > > cdc_acm 2-1.2:1.1: acm_start_wb - usb_submit_urb(write bulk) failed: -22 > > cdc_acm 2-1.2:1.1: acm_start_wb - usb_submit_urb(write bulk) failed: -22 > > cdc_acm 2-1.2:1.1: acm_start_wb - usb_submit_urb(write bulk) failed: -22 > > in dmesg after switching on runtime PM since their last stable update. What kernel are they using and which version did the update from? > Reverting 140cb81ac8c625942a1d695875932c615767a526 (its stable equivalent) > resolves the issue. > > commit 140cb81ac8c625942a1d695875932c615767a526 > Author: Johan Hovold <jhovold@xxxxxxxxx> > Date: Mon May 26 19:23:38 2014 +0200 > > USB: cdc-acm: fix broken runtime suspend > > As far as I can tell, your patch is correct, but nevertheless, they > see this error. What is to be done? So that commit has been in stable for 3.5 years already. After determining what kernel they are (and were) using, I guess we'll need to try and debug this on a mainline kernel. Johan -- 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
