[Bug 548644] New: suspend2ram does not resume
http://bugzilla.novell.com/show_bug.cgi?id=548644 Summary: suspend2ram does not resume Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: koenig@linux.de QAContact: qa@suse.de Found By: --- Lenovo T61p: after update from 11.1 to 11.2 RC2 wakeup from suspend2ram does not work anymore, the screen screen stays blank and CAPSLOCK etc. does not react. I'm using the "nv" X11 driver right now, with 11.1 I was using binary-only "nvidia" driver. I don't know if suspend/resume with "nv" in 11.1 worked... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=548644 Stephan Binner <binner@kde.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Other |Mobile Devices AssignedTo|bnc-team-screening@forge.pr |mobile-bugs@forge.provo.nov |ovo.novell.com |ell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=548644 User koenig@linux.de added comment http://bugzilla.novell.com/show_bug.cgi?id=548644#c1 --- Comment #1 from Harald Koenig <koenig@linux.de> 2009-10-21 15:16:34 MDT --- (In reply to comment #0) next try: switched to runlevel 3 before suspend so that X11 is not running. notebook again does not resume [correctly] -- I had to power off again:-( -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=548644 User koenig@linux.de added comment http://bugzilla.novell.com/show_bug.cgi?id=548644#c2 --- Comment #2 from Harald Koenig <koenig@linux.de> 2009-10-24 08:10:18 MDT --- (In reply to comment #1)
(In reply to comment #0)
next try: switched to runlevel 3 before suspend so that X11 is not running. notebook again does not resume [correctly] -- I had to power off again:-(
more tests: I did boot with "vga=normal" into runlevel 3, so no X11 driver or frame buffer involved at all. still same problem: the system dies in resume, not even CAPSLOCK or ALT-SYSRQ-B still works:-( even worse: suspend2disk does not work at all: see Bug 549856. so right now there is no way to suspend my notebook, thus I can't use 11.2 out of office for further testing (next week I'm in Dresden for the Linux-Kongress)... FYI: from 11.0 s2ram problems (bug 415105) I still have this config file which was no problem with 11.1: harald > cat /etc/pm/config.d/s2ram-t61p S2RAM_OPTS="-f" next suspend try will be without that file (I hope this should not be needed anymore ?!) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=548644 User hmacht@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=548644#c3 Holger Macht <hmacht@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hmacht@novell.com --- Comment #3 from Holger Macht <hmacht@novell.com> 2009-10-27 03:36:56 MDT --- When you're using the nv driver, you most likely will need that file. Maybe with different options you might be able to figure out with following the steps from http://en.opensuse.org/S2ram#My_machine_is_not_in_the_whitelist.2C_what_can_... However, this is not really supported if it works with the binary nvidia driver. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=548644 User koenig@linux.de added comment http://bugzilla.novell.com/show_bug.cgi?id=548644#c4 --- Comment #4 from Harald Koenig <koenig@linux.de> 2009-10-27 10:24:11 MDT --- as mentioned before, the old "-f" setting does not work anymore even with vga=normal (text mode) and runlevel 3, so no X11 invlolved at all. I tried all s2ram option combinations mentioned in your URL above with init=/bin/bash and vga=0x37d (1920x1200 fb). results: blocks at resume , but suspend led ("Moon") goes off: -f -f -a 2 -f -m -f -s -f -p blocks at resume , but suspend led ("Moon") stays on(!!) : -f -a 3 -f -a 1 -f -a 1 -m -f -a 1 -s resume works: -f -p -m -f -p -s BUT: using those "working" options in /etc/pm/config.d/s2ram-t61p with full runlevel 5 and "nv" X11 driver still hangs at resume :-((((( next try at suspend/resume(kill?) will be "-f -p -m -s" ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=548644 User koenig@linux.de added comment http://bugzilla.novell.com/show_bug.cgi?id=548644#c5 --- Comment #5 from Harald Koenig <koenig@linux.de> 2009-11-10 09:05:55 MST --- some more testing & tracing: if I run sudo s2ram -f -p -m -s in X11 (nv driver) suspend *and8 resume works fine, no problem. BUT if I run "powersave -u" then the system hangs quite early in resume :-( /var/log/pm-suspend.log shows that s2ram is called with correct options (plus some extra "set -x" debug output): + get_s2ram_opts + '[' -n '-f -p -m -s' ']' + echo 'INFO: using user-supplied options: S2RAM_OPTS='\''-f -p -m -s'\'' for suspending.' INFO: using user-supplied options: S2RAM_OPTS='-f -p -m -s' for suspending. + return + '[' -x /usr/sbin/s2ram ']' + set -x + /usr/sbin/s2ram -f -p -m -s Allocated buffer at 0x11000 (base is 0x0) ES: 0x1100 EBX: 0x0000 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=548644 User koenig@linux.de added comment http://bugzilla.novell.com/show_bug.cgi?id=548644#c6 --- Comment #6 from Harald Koenig <koenig@linux.de> 2009-11-10 10:25:20 MST --- (In reply to comment #5)
some more testing & tracing:
found problem and "fix" -- after some more testing/suspending/booting: I've disabled all scripts in /usr/lib/pm-utils/sleep.d/ (then resume works) and enabled them one by one: 45pcmcia causes the resume hang! reason: I have a D-Link DFE-660 pcmcia ethernet card installed in my Lenovo T61p notebook (which workds and suspends/resumes fine in 11.1 which uses the same 45pcmcia script...). reality check #1) removing the pcmcia card makes resume work fine! reality check #2) the mini-patch below "fixes" my resume problem too, "powersave -u" now works (for now;).... any bells ringing when you read PCMCIA and 11.2 ?! or D-link and 11.2 ?!? this is my "fix": --- /usr/lib/pm-utils/sleep.d/45pcmcia~ 2009-10-24 04:55:47.000000000 +0200 +++ /usr/lib/pm-utils/sleep.d/45pcmcia 2009-11-10 18:07:04.000000000 +0100 @@ -1,5 +1,6 @@ #!/bin/bash +exit 0 case "$1" in hibernate|suspend) if [ -x "/sbin/pccardctl" ]; then -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=548644 User koenig@linux.de added comment http://bugzilla.novell.com/show_bug.cgi?id=548644#c7 --- Comment #7 from Harald Koenig <koenig@linux.de> 2009-11-10 10:27:59 MST --- and one more information: just running /sbin/pccardctl eject /sbin/pccardctl insert manually at runlevel 5 is no problem, no hanging. the kernel messages for this sequence are: [ 2682.652401] pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0 [ 2682.684506] tulip 0000:16:00.0: PCI INT A disabled and [ 2691.548137] pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0 [ 2691.548257] pci 0000:16:00.0: reg 10 io port: [0xf7f3ec00-0xf7f3ec7f] [ 2691.548284] pci 0000:16:00.0: reg 14 32bit mmio: [0xf7fe6c00-0xf7fe6fff] [ 2691.548398] pci 0000:16:00.0: reg 30 32bit mmio: [0xedf00000-0xedf3ffff] [ 2691.557187] tulip 0000:16:00.0: enabling device (0000 -> 0003) [ 2691.557239] tulip 0000:16:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 2691.557321] tulip 0000:16:00.0: setting latency timer to 64 [ 2691.647642] tulip1: EEPROM default media type Autosense. [ 2691.647670] tulip1: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block. [ 2691.672301] tulip1: MII transceiver #0 config 3000 status 7809 advertising 01e1. [ 2691.675197] eth1: Digital DS21142/43 Tulip rev 65 at Port 0x8000, 00:50:ba:79:e2:ea, IRQ 16. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=548644 https://bugzilla.novell.com/show_bug.cgi?id=548644#c8 Uwe Drechsel <uwedr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |WONTFIX --- Comment #8 from Uwe Drechsel <uwedr@suse.com> 2011-08-26 12:52:59 CEST --- The lifecycle of openSUSE 11.2 ended on May 12th 2011. I'm closing this bug to make it easier to focus on upcoming releases. Thank you for reporting this issue and we are sorry that we have not be able to fix it before this version reached its end of life. If you would still like to see this bug fixed and are able to reproduce it against a maintained version, please reopen this bug and change the 'version' of this bug to the applicable version. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=548644 https://bugzilla.novell.com/show_bug.cgi?id=548644#c9 --- Comment #9 from Uwe Drechsel <uwedr@suse.com> 2011-08-26 12:57:36 CEST --- The lifecycle of openSUSE 11.2 ended on May 12th 2011. I'm closing this bug to make it easier to focus on upcoming releases. Thank you for reporting this issue and we are sorry that we have not be able to fix it before this version reached its end of life. If you would still like to see this bug fixed and are able to reproduce it against a maintained version, please reopen this bug and change the 'version' of this bug to the applicable version. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com