diff options
Diffstat (limited to 'Documentation/power')
| -rw-r--r-- | Documentation/power/s2ram.txt | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/Documentation/power/s2ram.txt b/Documentation/power/s2ram.txt index 514b94fc931..1bdfa044377 100644 --- a/Documentation/power/s2ram.txt +++ b/Documentation/power/s2ram.txt | |||
| @@ -49,6 +49,13 @@ machine that doesn't boot) is: | |||
| 49 | device (lspci and /sys/devices/pci* is your friend), and see if you can | 49 | device (lspci and /sys/devices/pci* is your friend), and see if you can |
| 50 | fix it, disable it, or trace into its resume function. | 50 | fix it, disable it, or trace into its resume function. |
| 51 | 51 | ||
| 52 | If no device matches the hash (or any matches appear to be false positives), | ||
| 53 | the culprit may be a device from a loadable kernel module that is not loaded | ||
| 54 | until after the hash is checked. You can check the hash against the current | ||
| 55 | devices again after more modules are loaded using sysfs: | ||
| 56 | |||
| 57 | cat /sys/power/pm_trace_dev_match | ||
| 58 | |||
| 52 | For example, the above happens to be the VGA device on my EVO, which I | 59 | For example, the above happens to be the VGA device on my EVO, which I |
| 53 | used to run with "radeonfb" (it's an ATI Radeon mobility). It turns out | 60 | used to run with "radeonfb" (it's an ATI Radeon mobility). It turns out |
| 54 | that "radeonfb" simply cannot resume that device - it tries to set the | 61 | that "radeonfb" simply cannot resume that device - it tries to set the |