[Ubuntu Wiki] Update of "DebuggingKernelSuspendHibernateResume" by brian-murray

Ubuntu Wiki noreply at ubuntu.com
Tue Mar 1 23:40:14 UTC 2011


Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The following page has been changed by brian-murray:
http://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume?action=diff&rev1=15&rev2=16

The comment on the change is:
Removed redundant boot parameter stuff

------------------------------------------------------------------------------
  
  Please indicate in the bug whether it worked, and if so include the contents of /proc/version_signature from that release (or the Ubuntu version number if you do not have it).
  
- === Do you end up with flashing caps-lock or similar? ===
+ === Do you end up with flashing Caps Lock light or similar? ===
  
- If you have flashing caps-lock lights then very likely you are experiencing a kernel panic.
+ If you have a flashing Caps Lock light then very likely you are experiencing a kernel panic.
  
  Please indicate that in the bug.
  
@@ -91, +91 @@

  
  https://help.ubuntu.com/community/EncryptedHome
  
- Users installing from Ubuntu 9.10 and selecting the Encrypted Home option will automatically have encrypted swap space. Other users may have also ran sudo ecryptfs-setup-swap.  It is important to note that Hibernation will not work with an encrypted swap at this time. Actually, hibernation will work just fine, but resume will fail.  There are ways around this, but it involves choosing a password to use for your swap encryption, and entering that password every time you boot your system, and sharing that password with anyone else that might want to resume the system.  This is a known, wishlist issue that we hope to solve for Ubuntu 10.04.  If you happen to report or triage this type of issue, please tag the bug '''encrypted-swap'''. For triagers, posting the following comment to a bug may help:
+ Users installing from Ubuntu 9.10 and selecting the Encrypted Home option will automatically have encrypted swap space. Other users may have also ran sudo ecryptfs-setup-swap.  It is important to note that Hibernation will work with an encrypted swap but resume will fail.  There are ways around this, but theyinvolve choosing a password to use for your encrypted swap and entering that password every time you boot your system, and sharing that password with anyone else that might want to resume the system.  This is a known, wishlist [[ https://bugs.launchpad.net/ecryptfs/+bug/432785 | issue ]] that we hope to solve.  If you happen to report or triage this type of issue, please tag the bug '''encrypted-swap'''. For triagers, posting the following comment to a bug may help:
  
  {{{
- Thank you for taking the time to report this bug and helping to make Ubuntu better.  It is currently a known issue that Hibernation will fail to resume due to an encrypted swap.  Developers are hoping to resolve this issue for the Lucid Lynx 10.04 release.  Please refer to https://help.ubuntu.com/community/EncryptedHome for more information.  We will tag this bug "encrypted-swap" so that we can track this issue going forward and possibly request additional testing.  Thanks in advance for your patience and cooperation. 
+ Thank you for taking the time to report this bug and helping to make Ubuntu better.  It is currently a known issue that Hibernation will fail to resume due to an encrypted swap.  Please refer to https://help.ubuntu.com/community/EncryptedHome for more information.  We will tag this bug "encrypted-swap" so that we can track this issue going forward and possibly request additional testing.  Thanks in advance for your patience and cooperation. 
  }}}
  
  == Hibernating from text mode ==
  
- The first step for debugging hibernate is to determine if the issue occurs when triggered using the pm-hibernate command.  If possible you should reboot the system with the no_console_suspend option (see Note 1 below for help with this).  You should then switch to VT1 by pressing Ctrl-Alt-F1.  Login at the prompt there and then run the following commands:
+ The first step for debugging hibernate is to determine if the issue occurs when triggered using the pm-hibernate command.  If possible you should reboot the system with the '''no_console_suspend''' boot parameter.  See DebuggingKernelBoot for instructions on how to modify boot parameters.  You should then switch to VT1 by pressing Ctrl-Alt-F1.  Login at the prompt there and then run the following commands:
  
      {{{
  setfont /usr/share/consolefonts/Uni1-VGA8.psf.gz
@@ -162, +162 @@

  
  = Notes =
  
- == Note 1: adding and removing options to the kernel command line ==
- 
- Assuming you are using the default boot loader {{{grub}}} you will very likely see the text below straight after the BIOS messages:
- 
-     {{{
- GRUB loading stage 1.5.
- 
- GRUB loading, please wait ...
- Press 'ESC' to enter the menu ...
- }}}
- 
- If you see this you should hit ESC to enter the kernel selection menu.  In some cases GRUB will enter the menu directly, in either case you will see something like this:
- 
-     {{{
- +-------------------------------------------------------------+
- | Ubuntu jaunty (stable), kernel 2.6.28-11-generic            |
- | Ubuntu jaunty (stable), kernel 2.6.28-11-generic (recovery) |
- | Ubuntu jaunty (stable), kernel 2.6.28-8-generic             |
- | Ubuntu jaunty (stable), kernel 2.6.28-8-generic (recovery)  |
- | Ubuntu jaunty (stable), memtest86+                          |
- +-------------------------------------------------------------+
-  Use the ^ and v keys to select which entry is highlighted.
-  Press enter to boot the selected OS, 'e' to edit the
-  commands before booting, or 'c' for a command line.
- }}}
- 
- At this point you should use the up and down cursor keys to select the kernel you normally use (if you do not know leave the cursor where it is).  Next hit 'e' to edit the line.  You will then see something similar to this:
- 
-     {{{
- +-------------------------------------------------------------+
- | uuid  123456789012345678901234567890                        |
- | kernel  /boot/vmlinuz-2.6.28-11-generic root=UUID=12345678> |
- | initrd  /boot/initrd.img-2.6.28-11-generic                  |
- | quiet                                                       |
- ...
- }}}
- 
- At this point you should cursor down until the line which starts kernel is highlighted, and hit 'e' to edit it.  You will then see something like this:
- 
-     {{{
-     [ Minimal BASH-like line editing is supported.   For
-       the first word, TAB lists possible command
-       completions.  Anywhere else TAB lists the possible
-       completions of a device/filename.  ESC at any time
-       exits. ]
- 
- <123456789 ro quiet splash _
- }}}
- 
- You can now cursor about in the line using left and right arrows, use delete to remove things you have been asked to get rid of and simply add new options at the end ensuring there is a space between each option.  If you make a mistake you can abort all edits with ESC.  When you are happy with the new options, hit Return, and then 'b' to boot the system.
- 
  == Battery drained whilst suspended stock reply ==
  {{{
  Thank you for taking the time to report this bug and helping to make Ubuntu better. This report seems to indicate that your battery drained while the machine was suspended. In this case a false bug report is generated, we are therefore closing this bug Invald. Please see https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume#Is%20this%20really%20a%20failure? for more information.
  }}}
   * Set status to Incomplete
  ----
- CategoryKernel
+ CategoryKernel CategoryDebugging
  



More information about the Ubuntu-bugsquad mailing list