** Description changed:

  I tried s2ram with all of the arguments listed on the OpenSUSE wiki, and
  none worked.  I guess that is not really a surprise: I am convinced that
  the issue is either my BIOS or the Linux kernel.  I have the latest
  BIOS, and it allows me to suspend and resume in Vista, and suspend in OS
  X but not resume.  In Linux I cannot even suspend.
  
  I also tried the debug method where the log outputs to the RTC, and then
  you get a "magic number" on reboot, but that provided me with no device
  info other than the "magic number" itself.
  
  I guess I could compile a kernel with ACPI_DEBUG, but I've never
  compiled a kernel before.  I read somewhere that the Tecra M4 has some
  issue unloading the ATA driver, but that workaround was supposedly
  integrated into the kernel, and anyway I can't apply it with any recent
  kernel.
  
  This is so annoying!  What can I do...?  Will booting with the options
  noapic or irqpoll help me at all?  Is Legacy USB in the BIOS an issue?
  (it has been on desktops for me for hibernate in Windows...)  What about
  the "Configuration" option in my BIOS?  "All Devices" or "Setup by OS"?
  
  Many thanks!
  
+ [I thought I'd just reiterate that even when I verbosely enter standby
+ from VT1 with small font, there are no messages, nor a kernel panic
+ because the screen goes dark so quickly.  I'm pretty sure it's more than
+ just the backlight going off.  There are no errors or anything.  The
+ system just hangs.  The procession is: some quick messages along the
+ lines of "entering standby..." then the screen goes dark, DVD drive
+ makes its shutdown noise, fan speed goes from low to medium, a bit of
+ disk activity, and then it hangs, failing to enter standby.  No amount
+ of waiting seems to resolve the problem.  I'm sure it's a hang because
+ the CapsLock key never starts flashing, no disk activity, nothing resets
+ the computer except the power button, the fan is on, the power button
+ doesn't start blinking, etc.]
+ 
  ProblemType: KernelOops
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  Architecture: amd64
  DistroRelease: Ubuntu 9.04
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InterpreterPath: /usr/bin/python2.6
  MachineType: TOSHIBA
  NonfreeKernelModules: nvidia
  Package: linux-image-2.6.28-11-generic 2.6.28-11.38
  ProcAttrCurrent: unconfined
  ProcCmdLine: root=UUID=3652bd6f-7399-4355-9e74-a2ef544d43d0 ro quiet splash 
no_console_suspend
  ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
  ProcEnviron: PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 2.6.28-11.38-generic
  SourcePackage: linux
  Tags: resume suspend
  Title: [TOSHIBA] suspend/resume failure [non-free: nvidia]
  UserGroups:

-- 
[TOSHIBA] suspend/resume failure [non-free: nvidia]
https://bugs.launchpad.net/bugs/352917
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to