https://bugzilla.novell.com/show_bug.cgi?id=264260 ------- Comment #1 from Ulrich.Windl@rz.uni-regensburg.de 2007-04-13 06:08 MST ------- kernel being used is: kernel-default-2.6.18.8-0.1 -- 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=264260 pavel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |seife@novell.com Status|NEW |ASSIGNED ------- Comment #2 from pavel@novell.com 2007-04-17 02:54 MST ------- Can you try both platform and shutdown mode ? (seife knows the details). Did it work before? Does manual suspend work (init=/bin/bash; echo disk > /sys/power/state)? -- 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=264260 ------- Comment #4 from seife@novell.com 2007-04-17 06:16 MST ------- try it from the running system, maybe runlevel 3 (but it should not matter). Edit /etc/suspend.conf, add a line shutdown method = shutdown at the end. Then use "powersave -U" or (as root) simply "pm-hibernate" to suspend to disk. If this works, then it is a problem with platform mode. The problem with /sys/power is new to me. Did you mount /sys manually in init=/bin/bash? You need to: - boot with init=/bin/bash - "mount /proc" - "mount /sys" - "echo shutdown > /sys/power/disk" - "echo disk > /sys/power/state" to try the minimal-boot, kernel-mode suspend. -- 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=264260 ------- Comment #6 from seife@novell.com 2007-04-17 10:34 MST ------- (In reply to comment #5)

A kingdom for good instructions: I had to manually mount /sys, and, more important, I had to activate the swap partition. (Without suspend would resume immediately (without Oops))

Oops. Yes, i forgot the "swapon -a" part.

When trying (no "acpi=force") echo shutdown > /sys/power/disk echo disk > /sys/power/state The suspend to disk seems to work as designed (and the computer turned itself off). Actually I was able to resume from that state with success.

Good. If you could retry the same with "echo platform > /sys/power/disk" instead of "shutdown", then we know that the in-kernel-suspend behaves correctly wrt. platform mode.

/etc/suspend.conf at the moment is all comments.

Which means that the "platform" mode is used. Please add shutdown method = shutdown to the file, and try again.

"powersave -U" would complain about "Connection to dbus not ready"

yes, powersave needs a running dbus and does only work from a fully booted system.

"pm-hibernate" would start a suspend, but it fails (after some disk activity) In "dmesg" I see a kernel Oops then...

ok, so nothing has changed here, but we also have not yet tried "shutdown" mode. -- 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=264260 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |DUPLICATE ------- Comment #8 from seife@novell.com 2007-04-18 05:53 MST ------- (In reply to comment #7)

"echo platform >/sys/power/disk" returns a "bash: echo: write error: Invalid argument" (however I can "echo shutdown" just fine)

Ok, this just means that there is no platform mode (ACPI) on your machine. The check for this was missing in the userspace suspend code which then caused the oops.

With the change to /etc/suspend.conf, pm-hibernate succeeds to dump the state to disk and power off. Resume was also successful and dmesg showed no Oops after that. As the kernel should never Oops, I still think there's a kernel problem somewhere.

yes, there is a kernel problem, and it is fixed for 10.3 already. *** This bug has been marked as a duplicate of bug 230470 *** -- 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.