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:19:07 -0400	[thread overview]
Message-ID: <465C6E9B.2040605@rtr.ca> (raw)
In-Reply-To: <alpine.LFD.0.98.0705291048020.26602@woody.linux-foundation.org>

Linus Torvalds wrote:
> 
> On Tue, 29 May 2007, Mark Lord wrote:
>> Okay, just to make it trivial,
>> I've narrowed it down to only this commit from Alan Stern:
>>
>> 7ed92f1a149dddc3cb537ccd7441e98adac12c3e USB: make the autosuspend workqueue
>> thread freezable
> 
> Heh. Have I mentioned how much I *hate* those kernel threads being frozen?
> 
> Just for fun, could you try if the patch that just rips out the freezer 
> calls from the STR code just fixes the problem too (instead of reverting 
> that commit?)
> 
> It was done by Matthew Garrett <mjg59@srcf.ucam.org>, and you should be 
> able to find it in the kernel archives under the subject
> 
> 	Re: pcmcia resume 60 second hang. Re: [patch 00/69] -stable review
> 	Message-ID: <20070527184402.GA21161@srcf.ucam.org>

Okay, I tried that one, but the machine just hung on the VGA console screen
at suspend time.  No alt-sysrq or anything.  Power-cycled it to recover.

> and it would be interesting to hear if that just solves the problem for 
> you too.
> 
> 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.

  reply	other threads:[~2007-05-29 18:19 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 [this message]
2007-05-29 18:28           ` Mark Lord
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=465C6E9B.2040605@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