Commit:     55e5fdfa541ec7bf1b1613624ed4dd8cdacaa841
Parent:     8538f96ae5aada1c04d69a993b20ad160b191d47
Author:     Mark Lord <[EMAIL PROTECTED]>
AuthorDate: Mon May 14 19:48:02 2007 -0400
Committer:  Greg Kroah-Hartman <[EMAIL PROTECTED]>
CommitDate: Thu Jul 12 16:29:48 2007 -0700

    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 <[EMAIL PROTECTED]>
    Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
 drivers/usb/core/hub.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
index f4ef7c2..08f0c22 100644
--- a/drivers/usb/core/hub.c
+++ b/drivers/usb/core/hub.c
@@ -403,9 +403,10 @@ static void hub_tt_kevent (struct work_struct *work)
        struct usb_hub          *hub =
                container_of(work, struct usb_hub, tt.kevent);
        unsigned long           flags;
+       int                     limit = 100;
        spin_lock_irqsave (&hub->tt.lock, flags);
-       while (!list_empty (&hub->tt.clear_list)) {
+       while (--limit && !list_empty (&hub->tt.clear_list)) {
                struct list_head        *temp;
                struct usb_tt_clear     *clear;
                struct usb_device       *hdev = hub->hdev;
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to