The patch titled
usb/core/hub.c loops forever on resume from ram due to bluetooth
has been removed from the -mm tree. Its filename was
usb-core-hubc-loops-forever-on-resume-from-ram-due-to.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: usb/core/hub.c loops forever on resume from ram due to bluetooth
From: Mark Lord <[EMAIL PROTECTED]>
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]>
Cc: Greg KH <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
drivers/usb/core/hub.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
diff -puN
drivers/usb/core/hub.c~usb-core-hubc-loops-forever-on-resume-from-ram-due-to
drivers/usb/core/hub.c
---
a/drivers/usb/core/hub.c~usb-core-hubc-loops-forever-on-resume-from-ram-due-to
+++ a/drivers/usb/core/hub.c
@@ -403,9 +403,10 @@ static void hub_tt_kevent (struct work_s
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;
_
Patches currently in -mm which might be from [EMAIL PROTECTED] are
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
