suspend: update warnings
PATCH 1/1 suspend: update warnings
Update suspend documentation. Warnings were a bit overstated, and did not point out important stuff.
---
commit 790df7223ac29afec81e7201adc879973311f27e tree 97fa2017f8f5aded0c44cfc75ba4903fbdb7f0a4 parent 63393fcbf056a6fd68142a49ed4e1258560dce2c author <pavel@amd.(none)> Mon, 22 Aug 2005 10:13:51 +0200 committer <pavel@amd.(none)> Mon, 22 Aug 2005 10:13:51 +0200
Documentation/power/swsusp.txt | 60 ++++++++++++++++++++++++++++++++-------- Documentation/power/video.txt | 9 +++++- 2 files changed, 56 insertions(+), 13 deletions(-)
Documentation/power/swsusp.txt +10 -12
@@ -1,22 +1,20 @@ -From kernel/suspend.c: +Some warnings, first. * BIG FAT WARNING ********************************************************* * - * If you have unsupported (*) devices using DMA... - * ...say goodbye to your data. - * * If you touch anything on disk between suspend and resume... * ...kiss your data goodbye. * - * If your disk driver does not support suspend... (IDE does) - * ...you'd better find out how to get along - * without your data. - * - * If you change kernel command line between suspend and resume... - * ...prepare for nasty fsck or worse. + * If you do resume from initrd after your filesystems are mounted... + * ...bye bye root partition. + * [this is actually same case as above] * - * If you change your hardware while system is suspended... - * ...well, it was not good idea. + * 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. * * (*) suspend/resume support is needed to make it safe.
Signature · 1 line
if you have sharp zaurus hardware you don't need... you know my address
Pavel Machek napsal(a):
Quoted 3 lines
+ * but it wil probably only crash.
... it will ... :)
Quoted 4 lines
*
* (*) suspend/resume support is needed to make it safe.
Hi.
Quoted 37 lines · Pavel Machek
Update suspend documentation. Warnings were a bit overstated, and did not point out important stuff.
---
commit790df7223ac29afec81e7201adc879973311f27etree97fa2017f8f5aded0c44cfc75ba4903fbdb7f0a4parent63393fcbf056a6fd68142a49ed4e1258560dce2cauthor <pavel@amd.(none)> Mon, 22 Aug 2005 10:13:51 +0200 committer <pavel@amd.(none)> Mon, 22 Aug 2005 10:13:51 +0200Documentation/power/swsusp.txt | 60 ++++++++++++++++++++++++++++++++-------- Documentation/power/video.txt | 9 +++++- 2 files changed, 56 insertions(+), 13 deletions(-)Documentation/power/swsusp.txt +3
-10@@ -1,22 +1,20 @@ -From kernel/suspend.c: +Some warnings, first. * BIG FAT WARNING ********************************************************* * - * If you have unsupported (*) devices using DMA... - * ...say goodbye to your data. - * * If you touch anything on disk between suspend and resume... * ...kiss your data goodbye. * - * If your disk driver does not support suspend... (IDE does) - * ...you'd better find out how to get along - * without your data. - * - * If you change kernel command line between suspend and resume... - * ...prepare for nasty fsck or worse. + * If you do resume from initrd after your filesystems are mounted... + * ...bye bye root partition.
Documentation/power/swsusp.txt line 17
Quoted 10 lines
Documentation/power/swsusp.txt +7
-2+ * [this is actually same case as above] * - * If you change your hardware while system is suspended... - * ...well, it was not good idea. + * 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.
Perhaps the 'changing your hardware' could mention that replacing faulty hardware may be safe.
Regards,
Nigel
Quoted 3 lines
Documentation/power/swsusp.txt +0
-0* * (*) suspend/resume support is needed to make it safe.
Signature · 4 lines
Evolution. Enumerate the requirements. Consider the interdependencies. Calculate the probabilities.
Hi!
Quoted 15 lines
Quoted 6 lines
+ * 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)
Quoted 1 line
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.
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
Quoted 2 lines
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.
Pavel
Signature · 1 line
if you have sharp zaurus hardware you don't need... you know my address
Hi.
Quoted 17 lines · Pavel Machek
Hi!
Quoted 15 lines
Quoted 6 lines
+ * 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)
Quoted 6 lines
Quoted 1 line
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.
Quoted 20 lines
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
Quoted 5 lines
Quoted 2 lines
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
Signature · 4 lines
Evolution. Enumerate the requirements. Consider the interdependencies. Calculate the probabilities.
Hi!
Quoted 17 lines
Quoted 17 lines
Quoted 16 lines
Quoted 6 lines
+ * 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.
Quoted 8 lines
Quoted 4 lines
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.
Do you remember which one is it? I have UHCI here, and it seems to work okay. powernow-k8 and cpufreq-centrino also seems to behave ok.
Pavel
Signature · 1 line
if you have sharp zaurus hardware you don't need... you know my address
Quoted 7 lines · Nigel Cunningham
Quoted 5 lines
Quoted 2 lines
- 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.
Dave
Hi Dave.
Quoted 11 lines · Dave Jones
Quoted 7 lines · Nigel Cunningham
Quoted 5 lines
Quoted 2 lines
- 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
Signature · 4 lines
Evolution. Enumerate the requirements. Consider the interdependencies. Calculate the probabilities.
Quoted 5 lines · Nigel Cunningham
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
- 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.
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
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
Quoted 2 lines · Pavel Machek
- 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.
Hi!
Quoted 6 lines
Quoted 2 lines
- 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
Signature · 1 line
if you have sharp zaurus hardware you don't need... you know my address
Quoted 11 lines · Pavel Machek
Hi!
Quoted 6 lines
Quoted 2 lines
- 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.
I think we made it pretty clear that people with binary modules should sodd off. Feel free to use banner for a big "sod off as usual" warning for all binary module user idiots.
Quoted 3 lines · Pavel Machek
"Known problematic" modules are; be sure to unload them before suspend:
- DRI being used (3D acceleration)
sometimes, not always. Also, this equals "reboot instead of suspend, please" since if i have to restart X i'd rather reboot instead. Many people are successfull in using DRI with suspend, even running 3D Apps while suspend works now. Of course, for troubleshooting it is ok to keep DRI off the picture, but usually suspend works fine with DRI
Quoted 2 lines
- Firewire
- SCSI
Signature · 3 lines
Stefan Seyfried \ "I didn't want to write for pay. I QA / R&D Team Mobile Devices \ wanted to be paid for what I write." SUSE LINUX Products GmbH, Nürnberg \ -- Leonard Cohen