public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Dave Jones <DaveJ@redhat.com>
Cc: Pavel Machek <pavel@ucw.cz>, Andrew Morton <akpm@zip.com.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] suspend: update warnings
Date: Wed, 24 Aug 2005 06:53:49 +1000	[thread overview]
Message-ID: <1124830428.4826.0.camel@localhost> (raw)
In-Reply-To: <20050823150501.GA23171@redhat.com>

Hi Dave.

On Wed, 2005-08-24 at 01:05, Dave Jones wrote:
> On Tue, Aug 23, 2005 at 10:53:16PM +1000, Nigel Cunningham wrote:
> 
>  > > > - CPU Freq  (improving too)
>  > > > It might be good to mention these areas too.
>  > > Well, right; but those 'only' cause system to crash during suspend. I
>  > > was talking about really dangerous stuff.
>  > > Both usb and cpufreq seems to work okay here.
>  > It depends on what you're using. I believe one of the usb root hub
>  > drivers is okay, the others aren't. Similar for cpufreq.
> 
> If you know a specific cpufreq driver which has problems, I'm all ears.

Here's the report from a user that I'm thinking of:

http://lists.suspend2.net/lurker/message/20050822.140001.6bf4abfe.en.html

Regards,

Nigel
-- 
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.


  reply	other threads:[~2005-08-23 20:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-22  8:15 [patch] suspend: update warnings Pavel Machek
2005-08-22 22:41 ` Jiri Slaby
2005-08-22 23:32 ` Nigel Cunningham
2005-08-23 12:50   ` Pavel Machek
2005-08-23 12:53     ` Nigel Cunningham
2005-08-23 12:58       ` Pavel Machek
2005-08-23 15:05       ` Dave Jones
2005-08-23 20:53         ` Nigel Cunningham [this message]
2005-08-24  1:15           ` Dave Jones
2005-08-23 12:57     ` Christoph Hellwig
2005-08-23 13:00       ` Pavel Machek
2005-08-23 13:02         ` Christoph Hellwig
2005-08-29  5:57         ` Stefan Seyfried

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=1124830428.4826.0.camel@localhost \
    --to=ncunningham@cyclades.com \
    --cc=DaveJ@redhat.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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