[Bug 242113] New: pm-suspend kills machine, S2ram work on ThinkPad Z60m
https://bugzilla.novell.com/show_bug.cgi?id=242113 Summary: pm-suspend kills machine, S2ram work on ThinkPad Z60m Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: axel.braun@gmx.de QAContact: qa@suse.de New installation on a Thinkpad Z60m: When suspended to RAM by calling s2ram (w/o any options), the system goes to sleep and can be resumed using the <Fn> key. This works fine even if it is done multiple times. If suspended with pm-suspend, it shows the same behaviour as under SuSE 10.0: It looks good on the first glance, but on resume the HD-light flashes shortly, and then it hangs. It cant be reached via Network as well. A 'hard' power down with salvaging run is required. pm-hibernate works as under 10.0, although I have the impression that the network manager has a problem on reconnect (I saw this bug already reported). -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 ------- Comment #1 from axel.braun@gmx.de 2007-02-05 04:30 MST ------- z60m:/home/axel # s2ram -n Machine matched entry 88: sys_vendor = 'IBM' sys_product = '2529*' sys_version = '' bios_version = '' Fixes: 0x3 S3_BIOS S3_MODE This machine can be identified by: sys_vendor = "IBM" sys_product = "2529FKG" sys_version = "ThinkPad Z60m" bios_version = "77ET54WW (1.14 )" See http://en.opensuse.org/S2ram for details. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 ------- Comment #2 from axel.braun@gmx.de 2007-02-05 04:44 MST ------- Created an attachment (id=117316) --> (https://bugzilla.novell.com/attachment.cgi?id=117316&action=view) pm-suspend.log -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kernel-maintainers@forge.provo.novell.com |screening@forge.provo.novell| |.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 jeffm@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |pavel@novell.com |maintainers@forge.provo.nove| |ll.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife@novell.com Severity|Major |Normal Status|NEW |ASSIGNED ------- Comment #3 from pavel@novell.com 2007-02-06 16:12 MST ------- So you are complaining that suspend-to-ram triggered by pm-suspend does not work correctly? But direct s2ram will work okay? Does suspend to disk work ok? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |axel.braun@gmx.de -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 axel.braun@gmx.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|axel.braun@gmx.de | ------- Comment #4 from axel.braun@gmx.de 2007-02-07 03:46 MST ------- Yes, Suspend-to-disk works ok (triggered via kpowersave - pm-hibernate I assume), pm-suspend breaks it, and S2ram works OK -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fseidel@novell.com, hmacht@novell.com, | |pavel@novell.com AssignedTo|pavel@novell.com |seife@novell.com ------- Comment #5 from seife@novell.com 2007-02-07 07:14 MST ------- Hm. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 ------- Comment #6 from seife@novell.com 2007-02-07 07:29 MST ------- That comment was a little bit too short :-) We are actually not doing any suspend to RAM related magic in pm-suspend. From the log: ===== Mo 5. Feb 12:35:00 CET 2007: running hook: /etc/pm/hooks/23dock Mo 5. Feb 12:35:00 CET 2007: running thinkpad hooks for event undock. x60 undock /org/freedesktop/Hal/devices/storage_model_DVD_RAM_UJ_830Sx unregistered /sys/block/sr0 ibm_undock hooks/thinkpad/50generic: line 19: echo: write error: Kein passendes Gerät gefunden This is the undock script from dockutils. AFAICT, the "write error" is "mostly harmless" :-) Maybe Holger can tell us something about it. You can disable this one by "chmod -x /etc/pm/hooks/23dock" ===== Mo 5. Feb 12:35:00 CET 2007: running hook: /etc/pm/hooks/30s2disk-check ===== Mo 5. Feb 12:35:00 CET 2007: running hook: /etc/pm/hooks/45pcmcia ejecting PCMCIA cards... Should be harmless, but you can disable it analog to the dock hook ===== Mo 5. Feb 12:35:00 CET 2007: running hook: /etc/pm/hooks/50modules trying to unload: button Should also be harmless, but you can just empty the variable SUSPEND_MODULES in /etc/pm/config ===== Mo 5. Feb 12:35:00 CET 2007: running hook: /etc/pm/hooks/66dummy Oh, this time we're doing a suspend to RAM. Cool! hehe, you actually read my documentation. Thanks :-) Please try if you can find the offending action by disabling the hooks (i would actually start with disabling the button module removal) one after another. If nothing of this helps, try disabling all the other hooks, that did not produce any output (they are still being run). If this still does not help i do not really have an idea where the problem might be. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 ------- Comment #7 from axel.braun@gmx.de 2007-02-11 06:16 MST ------- Sure I read the fine documentation ;-) Well, it looks not that easy anymore, no idea why, but he state is at the moment 'Anything may work or not'. As I was now mentally prepared to crash my main working device by purpose, I noticed that suddenly suspend-to-disk was not working anymore, instead, tons of little colored squares on the screen. I assume an interaction with the lovely ATI graphics driver. Anyway, in runlevel 3, s2ram as well as pm-suspend worked, pm-hibernate crashed (Under SuSE 10.0 it was vice versa, hibernation worked, also with ATI drivers, but suspend to ram crashed. As long as you dont have some useful hints, I will try to come to a state where I can reproduce either a crash or a working system.... -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 ------- Comment #8 from axel.braun@gmx.de 2007-02-13 00:47 MST ------- Created an attachment (id=118779) --> (https://bugzilla.novell.com/attachment.cgi?id=118779&action=view) Log of failed hibernation Here is another log of a failed suspend-to-disk. That was working perfectly in 10.0, but now crashes the system as well. I've tried userspace and kernel for HIBERNATE_METHOD, same result. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 ------- Comment #9 from pavel@novell.com 2007-02-13 04:16 MST ------- One bug per report, please. (And try triggering suspend-to-disk manually, without pm-hibernate; perhaps it really is one bug). -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113
------- Comment #10 from axel.braun@gmx.de 2007-02-14 13:48 MST -------
So....in between I have the feeling that the problem is related to the ATI
driver (8.32.5)
As Pavel suggested, I tried some
echo -n disk > /sys/power/state
and resume= on the kernel boot command line.
Result: Sometimes it worked, sometime not.
With ATI-drivers:
S2ram: sometimes it worked, sometime not (there is a switch from VT1 to VT7 and
back - this seems to hang sometimes)
pm-suspend: works not
pm-hibernate: works mostly not
Then I changed /etc/X11/xorg.conf to use a basic setting (no ATI specific
stuff, removed kernel module and tried again.
Result: All options (s2ram, pm-suspend, pm-hibernate) work as expected!
Beside this, I got the error message:
Feb 14 21:13:02 z60m kernel: mmc0: Got command interrupt even though no command
operation was in progress.
Feb 14 21:13:02 z60m kernel: mmc0: Please report this to
https://bugzilla.novell.com/show_bug.cgi?id=242113 ------- Comment #11 from axel.braun@gmx.de 2007-02-16 02:40 MST ------- Back to start: According to http://en.opensuse.org/S2ram I tried with init=/bin/bash, and in this mode s2ram just *worked*. So I assume it is an interaction with a loaded driver. is fglrx the bad boy? -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 ------- Comment #12 from seife@novell.com 2007-02-16 08:49 MST ------- Probably yes. Reproduce without flgrx, or report it to ATI. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 ------- Comment #13 from axel.braun@gmx.de 2007-02-20 08:29 MST ------- I removed fglrx_7_1_0_SUSE102-8.32.5-1.i386.rpm , rebooted, and up to now I didnt find a configuration that did not work: s2ram & pm-suspend work, pm-hibernate works as well, although the save to disk seems a little slow. Looks like the problem *is* the ATI-driver. I will send them a bug report, but I dont have much hope to get more response than from /dev/nul.... -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=242113 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WORKSFORME ------- Comment #14 from seife@novell.com 2007-02-20 09:07 MST ------- you can also file it here in bugzilla, against component "X 3rd party", then it will be handed over to ATI (if i remember this correctly). For s2ram and pm-utils, i'll close the bug as "worksforme". -- 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, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com