summaryrefslogtreecommitdiffstats
path: root/drivers/usb/misc/usblcd.c
diff options
context:
space:
mode:
authorMark Lord2007-05-15 01:48:02 +0200
committerGreg Kroah-Hartman2007-07-13 01:29:48 +0200
commit55e5fdfa541ec7bf1b1613624ed4dd8cdacaa841 (patch)
tree236f91853b65f9edfc3014451ffd516275e8a676 /drivers/usb/misc/usblcd.c
parentUSB: add USB_DEVICE_AND_INTERFACE_INFO for device matching (diff)
downloadkernel-qcow2-linux-55e5fdfa541ec7bf1b1613624ed4dd8cdacaa841.tar.gz
kernel-qcow2-linux-55e5fdfa541ec7bf1b1613624ed4dd8cdacaa841.tar.xz
kernel-qcow2-linux-55e5fdfa541ec7bf1b1613624ed4dd8cdacaa841.zip
USB: hub.c loops forever on resume from ram due to bluetooth
Okay, found it. The root cause here was a missing CONFIG_USB_SUSPEND=y, which means the hci_usb device never got marked as USB_STATE_SUSPENDED, which then caused the loop to go on forever. The system works fine now with CONFIG_USB_SUSPEND=y in the .config. Here's the patch to prevent future lockups for this or other causes. I no longer need it, but it does still seem a good idea. Signed-off-by: Mark Lord <mlord@pobox.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/usb/misc/usblcd.c')
0 files changed, 0 insertions, 0 deletions