From: Pavel Machek <pavel@ucw.cz>
To: Christoph Hellwig <hch@infradead.org>,
Nigel Cunningham <ncunningham@cyclades.com>,
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 15:00:50 +0200 [thread overview]
Message-ID: <20050823130050.GB3735@elf.ucw.cz> (raw)
In-Reply-To: <20050823125724.GA7341@infradead.org>
Hi!
> > - DRI being used in X where the drivers don't properly support
> > suspend/resume (NVidia esp)
>
> NVidias driver is not support and a copyright violation of the
> copyrights of many of use. It's never supported so please don't
> mention it.
Unfortunately, it is quite common out there. I need to somehow keep
those bug reports off my mailbox.
Okay, this should be enough:
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 (3D acceleration)
- Firewire
- SCSI
--
if you have sharp zaurus hardware you don't need... you know my address
next prev parent reply other threads:[~2005-08-23 13:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 8:15 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
2005-08-23 12:57 ` Christoph Hellwig
2005-08-23 13:00 ` Pavel Machek [this message]
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=20050823130050.GB3735@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@zip.com.au \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@cyclades.com \
/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
all inboxes | Powered by JetHome®