http://bugzilla.opensuse.org/show_bug.cgi?id=957547 http://bugzilla.opensuse.org/show_bug.cgi?id=957547#c1 --- Comment #1 from Ailin Nemui --- Created attachment 658068 --> http://bugzilla.opensuse.org/attachment.cgi?id=658068&action=edit 4.1.13 kernel boot log -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957547 http://bugzilla.opensuse.org/show_bug.cgi?id=957547#c3 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ailin.nemui@gmail.com, | |tiwai@suse.com Flags| |needinfo?(ailin.nemui@gmail | |.com) --- Comment #3 from Takashi Iwai --- Your system is Tumbleweed? And you can do S4 still with the current system when booting 4.1.13 kernel, right? Do you have 4.2.x kernel before updating 4.3 to test? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957547 http://bugzilla.opensuse.org/show_bug.cgi?id=957547#c5 --- Comment #5 from Takashi Iwai --- So, 4.1.13 still works while 4.3 doesn't with the very same system? It wasn't clear in your description. And is your system Tumbleweed or not? Regarding 4.2 kernel: yes, there are test packages in OBS home:tiwai:kernel:4.2 repo. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957547 http://bugzilla.opensuse.org/show_bug.cgi?id=957547#c7 Ailin Nemui changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ailin.nemui@gmail | |.com) | --- Comment #7 from Ailin Nemui --- 4.0.3: works 4.1.13: works 4.2.5: resume BROKEN 4.3.0: resume BROKEN 4.4.0-rc3: fails to bring up system ;-) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957547 http://bugzilla.opensuse.org/show_bug.cgi?id=957547#c8 --- Comment #8 from Takashi Iwai --- Thanks. I tested the latest TW with KVM here, too, and S4 works there. So S4 isn't broken generally, at least. Just to be sure: you tested with "systemctl hibernate" command? Also, boot 4.3 kernel with no_console_suspend option, go to Linux console (VT1), and run "systemctl hibernate" there. Does it show writing the image? If a hibernation image has been really written, you can inspect it by booting a recovery DVD or USB. Then you can copy the swap partition via dd command. At least, you can copy some first bytes to see whether it has a S4 signature the kernel checks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957547 http://bugzilla.opensuse.org/show_bug.cgi?id=957547#c10 --- Comment #10 from Ailin Nemui --- (I suspect this be system-specific and not generally broken) - I tested with systemctl hibernate - I can see image is being written - I can also see image being loaded after resume - roughly when the image loading is finished, the system resets and I'm back at the uefi boot screen (same as before) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957547 http://bugzilla.opensuse.org/show_bug.cgi?id=957547#c12 Ailin Nemui changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ailin.nemui@gmail | |.com) | --- Comment #12 from Ailin Nemui --- I did zypper rm followed by mkinitrd and several reboots but the problem persists. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957547 http://bugzilla.opensuse.org/show_bug.cgi?id=957547#c14 --- Comment #14 from Ailin Nemui --- Thanks for your help, I understand you cannot support this config. I will report back with 42.1 later -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957547 http://bugzilla.opensuse.org/show_bug.cgi?id=957547#c16 --- Comment #16 from Takashi Iwai --- OK, then confirm whether Leap kernel still works with your new system. Once when it's confirmed, this should be tracked by upstream, as this is likely an upstream kernel regression. Reporting to bugzilla.kernel.org might help. In that case, please take the kernel boot messages again on both kernels, and upload to Bugzilla. Meanwhile, you can try to reduce the component that might break PM. For example, booting with "nomodeset 3" boot option, the graphics will be disabled and doesn't start X. There you can test S4. The screen after the resume will be broken, but you'll see at least whether the system returns. Similarly, you can blacklist the non-mandatory modules (e.g. network, USB, etc) for checking whether it's relevant with the problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957547 Markos Chandras changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mchandras@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957547 http://bugzilla.opensuse.org/show_bug.cgi?id=957547#c19 --- Comment #19 from Takashi Iwai --- (In reply to Markos Chandras from comment #18)

(In reply to Takashi Iwai from comment #17)

...

Also, another thing to be helpful is to check whether the direct S4 also shows the same problem. Try like echo -n disk > /sys/power/state

This will trigger S4 but without systemd hooks. Then you'll have to choose the right kernel in GRUB at resuming, instead of the automatic boot.

I guess this should still show the problem, but just to be sure.

Once when this is confirmed, you can try the test method in pm_test. For example, echo -n freezer > /sys/power/pm_test will test only the freezer and resumes. You can see the available test methods by "cat /sys/power/pm_test". More detailed instruction is found in /usr/src/linux/Documentation/power/basic-pm-debugging.txt.

Hi,

I have the same problem on TW even with the latest 4.4.3 kernel (maybe update the title?) but on a different hardware (Dell Latitude E7450). I tried your direct S4 suggestion and it worked 2 out of 2. Certainly not a definitive result but good enough I suppose. I am not clearing up the needinfo flag because this is different hardware than the original report.

Are your *user space* also TW or Leap? Or is it openSUSE 13.2? If the direct S4 works, it means that the problem isn't in the kernel. Or it's a user-mode S4 that hasn't been tested (and possibly broken) on recent kernels. In anyway, check whether suspend and pm-utils packages are installed on your system. If yes, kill them. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957547 http://bugzilla.opensuse.org/show_bug.cgi?id=957547#c21 --- Comment #21 from Takashi Iwai --- (In reply to Markos Chandras from comment #20)

(In reply to Takashi Iwai from comment #19)

...

(In reply to Markos Chandras from comment #18)

...

(In reply to Takashi Iwai from comment #17)

...

Also, another thing to be helpful is to check whether the direct S4 also shows the same problem. Try like echo -n disk > /sys/power/state

This will trigger S4 but without systemd hooks. Then you'll have to choose the right kernel in GRUB at resuming, instead of the automatic boot.

I guess this should still show the problem, but just to be sure.

Once when this is confirmed, you can try the test method in pm_test. For example, echo -n freezer > /sys/power/pm_test will test only the freezer and resumes. You can see the available test methods by "cat /sys/power/pm_test". More detailed instruction is found in /usr/src/linux/Documentation/power/basic-pm-debugging.txt.

Hi,

I have the same problem on TW even with the latest 4.4.3 kernel (maybe update the title?) but on a different hardware (Dell Latitude E7450). I tried your direct S4 suggestion and it worked 2 out of 2. Certainly not a definitive result but good enough I suppose. I am not clearing up the needinfo flag because this is different hardware than the original report.

Are your *user space* also TW or Leap? Or is it openSUSE 13.2? If the direct S4 works, it means that the problem isn't in the kernel. Or it's a user-mode S4 that hasn't been tested (and possibly broken) on recent kernels.

Yes the entire system is TW.

...

In anyway, check whether suspend and pm-utils packages are installed on your system. If yes, kill them.

None of them is installed

OK, so far, so good. Did you mention that "systemctl hibernate" fails while the direct S4 succeeds? If so, it's a different bug. Please open another bug report instead of hanging here. -- You are receiving this mail because: You are on the CC list for the bug.