public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Nigel Cunningham <ncunningham@cyclades.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: Tue, 23 Aug 2005 21:15:12 -0400	[thread overview]
Message-ID: <20050824011512.GC23171@redhat.com> (raw)
In-Reply-To: <1124830428.4826.0.camel@localhost>

On Wed, Aug 24, 2005 at 06:53:49AM +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

Tainted oopses are completely uninteresting to me.  I see nothing there
at all to go on to investigate any problem in the centrino driver.
That the cpufreq driver & some binary module doesn't play together nicely
isn't news btw, I've heard reports of both of the common binary 3d drivers
locking up when CPU scaling is used, and there is *nothing* we can do to
fix that. If those drivers are making assumptions that the cpu speed
will remain static, they're broken, and unfixable by us.

We have enough problems getting suspend working for users without
binary junk loaded, so as far as I'm concerned.. CLOSED->NOTABUG.

		Dave


  reply	other threads:[~2005-08-24  1:15 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
2005-08-24  1:15           ` Dave Jones [this message]
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=20050824011512.GC23171@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@cyclades.com \
    --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