On Monday 23 March 2009, Frans Pop wrote: > Currently if a laptop is suspended e.g. while docked and then resumed > after undocking it, the following errors get generated because the USB > hub in the docking station and the devices connected to it are no > longer available: > pm_op(): usb_dev_resume+0x0/0x10 returns -19 > PM: Device 1-2 failed to resume: error -19 > pm_op(): usb_dev_resume+0x0/0x10 returns -19 > PM: Device 1-2.2 failed to resume: error -19 > pm_op(): usb_dev_resume+0x0/0x10 returns -19 > PM: Device 1-2.3 failed to resume: error -19 > > As the removal of USB devices while a system is suspended is a > relatively common use case and in most cases not an error, just return > success on -ENODEV. The user gets informed anyway as the USB subsystem > generates regular disconnect messages for the devices shortly > afterwards: > usb 1-2: USB disconnect, address 3 > usb 1-2.2: USB disconnect, address 4 > usblp0: removed > usb 1-2.3: USB disconnect, address 5 > > Signed-off-by: Frans Pop <elendil@xxxxxxxxx> > Cc: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> > Cc: Rafael J. Wysocki <rjw@xxxxxxx> Forgot to mention that the patch is intended on top of Rafael's "Rework disabling of interrupts during suspend-resume" series. -- 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
