public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <lkml@rtr.ca>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Regression: USB is nfg after suspend/resume(RAM) cycle on Intel chipset
Date: Tue, 29 May 2007 14:28:58 -0400	[thread overview]
Message-ID: <465C70EA.9020300@rtr.ca> (raw)
In-Reply-To: <465C6E9B.2040605@rtr.ca>

Mark Lord wrote:
> Linus Torvalds wrote:
..
>> There's a different (but related to all the same freezer problems) 
>> patch by Rafael Wysocki <rjw@sisk.pl>:
>>
>>     Re: [RFC][PATCH][EXPERIMENTAL] Make kernel threads nonfreezable by 
>> default
>>     Message-Id: <200705291415.31970.rjw@sisk.pl>
> 
> I'll hunt for Rafael's patch next.

Mmm.. Rafael's patch appears to be part of a large series of 15 patches,
and it's not totally clear to me how to test just that part of it,
so I think I'll leave things as is (working!) for now.

Here's my current fix:

-- snip --

Regarding commit 7ed92f1a149dddc3cb537ccd7441e98adac12c3e
"USB: make the autosuspend workqueue thread freezable":

This commit causes USB lockups on resume from Suspend-to-RAM
on my Core2duo notebook.  Applying the patch below to revert
the commit fixes the problem for me in 2.6.22-rc3.

Signed-off-by:  Mark Lord <mlord@pobox.com>
---
--- b0rken/drivers/usb/core/usb.c	2007-05-29 13:32:32.000000000 -0400
+++ linux/drivers/usb/core/usb.c	2007-05-29 13:27:10.000000000 -0400
@@ -205,11 +205,7 @@
 
 static int ksuspend_usb_init(void)
 {
-	/* This workqueue is supposed to be both freezable and
-	 * singlethreaded.  Its job doesn't justify running on more
-	 * than one CPU.
-	 */
-	ksuspend_usb_wq = create_freezeable_workqueue("ksuspend_usbd");
+	ksuspend_usb_wq = create_singlethread_workqueue("ksuspend_usbd");
 	if (!ksuspend_usb_wq)
 		return -ENOMEM;
 	return 0;

  reply	other threads:[~2007-05-29 18:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 16:35 Regression: USB is nfg after suspend/resume(RAM) cycle on Intel chipset Mark Lord
2007-05-29 16:46 ` Linus Torvalds
2007-05-29 17:00   ` Mark Lord
2007-05-29 17:04     ` Mark Lord
2007-05-29 17:07       ` Nish Aravamudan
2007-05-30  7:02         ` Regression: USB is nfg after suspend/resume(RAM) cycle onIntel chipset Romano Giannetti
2007-05-29 17:06     ` Regression: USB is nfg after suspend/resume(RAM) cycle on Intel chipset Nish Aravamudan
2007-05-29 17:47       ` Linus Torvalds
2007-05-29 19:32         ` J. Bruce Fields
2007-05-29 17:42     ` Linus Torvalds
2007-05-29 17:19   ` Mark Lord
2007-05-29 17:37     ` Mark Lord
2007-05-29 17:54       ` Linus Torvalds
2007-05-29 18:19         ` Mark Lord
2007-05-29 18:28           ` Mark Lord [this message]
2007-05-29 18:41       ` Alan Stern
2007-05-29 19:11         ` Mark Lord
2007-05-29 19:22           ` Linus Torvalds
2007-05-29 20:34             ` [PATCH] USB: replace flush_workqueue with cancel_sync_work Alan Stern
2007-05-29 21:19               ` Mark Lord
2007-05-29 20:12           ` Regression: USB is nfg after suspend/resume(RAM) cycle on Intel chipset Alan Stern
2007-05-29 17:03 ` Nish Aravamudan
2007-05-29 17:06   ` Mark Lord

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=465C70EA.9020300@rtr.ca \
    --to=lkml@rtr.ca \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rjw@sisk.pl \
    --cc=stern@rowland.harvard.edu \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox