All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: 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 22:53:16 +1000	[thread overview]
Message-ID: <1124801595.4602.18.camel@localhost> (raw)
In-Reply-To: <20050823125017.GB3664@elf.ucw.cz>

Hi.

On Tue, 2005-08-23 at 22:50, Pavel Machek wrote:
> Hi!
> 
> > > + * If you have unsupported (*) devices using DMA, you may have some
> > > + * problems. If your disk driver does not support suspend... (IDE does),
> > > + * it may cause some problems, too. If you change kernel command line 
> > > + * between suspend and resume, it may do something wrong. If you change 
> > > + * your hardware while system is suspended... well, it was not good idea;
> > > + * but it wil probably only crash.
> > 
> > The most common driver issues I see involve:
> > - USB being built in or as modules that are still loaded while
> > suspending (getting better, but not there yet)
> > - DRI being used in X where the drivers don't properly support
> > suspend/resume (NVidia esp)
> > - Firewire
> > - 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. USB certainly
accounts for a high percentage of the failures I see.

> I've added FAQ entry at the end:
> 
> Q: What information is usefull for debugging suspend-to-disk problems?
> 
> A: Well, last messages on the screen are always useful. If something
> is broken, it is usually some kernel driver, therefore trying with as
> little as possible modules loaded helps a lot. I also prefer people to
> suspend from console, preferably without X running. Booting with
> init=/bin/bash, then swapon and starting suspend sequence manually
> usually does the trick. Then it is good idea to try with latest
> vanilla kernel.
> 
> "Known problematic" modules are; be sure to unload them before
> suspend:
> - DRI being used in X where the drivers don't properly support
> suspend/resume (NVidia esp)
> - Firewire
> - SCSI
> 
> 
> > Perhaps the 'changing your hardware' could mention that replacing faulty
> > hardware may be safe.
> 
> I do not want to encourage people to do that. Yep, its probably safe,
> no, I do not want them to know.

:>

Thanks

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


  reply	other threads:[~2005-08-23 12:53 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 [this message]
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
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=1124801595.4602.18.camel@localhost \
    --to=ncunningham@cyclades.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.