[Bug 502193] New: Xen kernel reports to be capable of suspend to RAM, but fails to do so

bugzilla_noreply＠novell.com

8 May 2009 8 May '09

15:29

http://bugzilla.novell.com/show_bug.cgi?id=502193 Summary: Xen kernel reports to be capable of suspend to RAM, but fails to do so Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: nice@titanic.nyme.hu QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; hu-HU; rv:1.9.0.9) Gecko/2009041500 SUSE/3.0.9-0.1.1 Firefox/3.0.9 I run this xen kernel: milleniumfalcon:~ # uname -r 2.6.27.21-0.1-xen milleniumfalcon:~ # cat /proc/cmdline root=/dev/disk/by-id/ata-HTS541010G9SA00_MP2ZX0XLG71D3S-part1 resume=/dev/disk/by-id/ata-HTS541010G9SA00_MP2ZX0XLG71D3S-part2 splash=silent vga=0x31a milleniumfalcon:~ # cat /sys/power/state mem So it reports that its capable of s2ram. KDE 4.2.3 displays the suspend to RAM button indeed (and not a suspend to disk button), but when I try to suspend to RAM by KDE GUI, the suspension process "bounces", that is, my X.org desktop disappears, the system seems to prepare for suspension, but instead of S3 state, the machin continues to run. X.org reappears, and I can work again. Using the s2ram (and s2disk, being curious) commandline utility is also unuccessful: milleniumfalcon:~ # s2ram Switching from vt7 to vt1 /proc/sys/kernel/acpi_video_flags does not exist; you need a kernel >=2.6.16. switching back to vt7 milleniumfalcon:~ # s2disk s2disk: Could not stat the resume device file. Reason: No such file or directory But when I do a 'echo mem > /sys/power/state', the system seem to reach the S3 state: display turns off, caps lock and num lock LEDS blink together once, all fans and drives stop working, and the power LED starts blinking slowly (this is how my Compaq nc6320 behaves during sleeping). However, when I try to wake it up now, the display remains turned off and the system is unaware of the keyboard (no caps lock feedback), however, fans, and HDD are running (HDD LED also indicates some activity). I have to turn it off forcibly. Reproducible: Always Steps to Reproduce: 1. Try to do a suspend (or maybe hibernate too) on a Xen kernel Actual Results: The attemt is either unsuccessful but harmless, or causes the system to hang. Expected Results: I don't know. Maybe Xen kernels shouldn even support suspend ( http://wiki.xensource.com/xenwiki/XenFaq#head-cb7861c9865fc8fbae3bb472f04c5d... ). Or should it ? ( https://bugzilla.novell.com/show_bug.cgi?id=500525#c17 ) -- 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.

Show replies by date

bugzilla_noreply＠novell.com

8 May 8 May

18:27

New subject: [Bug 502193] Xen kernel reports to be capable of suspend to RAM, but fails to do so

http://bugzilla.novell.com/show_bug.cgi?id=502193 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c1 --- Comment #1 from Tamás Németh 2009-05-08 12:27:31 MDT --- (In reply to comment #0)

...

, however, fans, and HDD are running (HDD LED also indicates some activity). I have to turn it off forcibly.

Forget about the HDD LED. I tried it once more but can't remember ny HDD LED activity on the second occassion. Maybe there is no HDD activity at all. -- 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.

bugzilla_noreply＠novell.com

11 May 11 May

08:13

New subject: [Bug 502193] Xen kernel reports to be capable of suspend to RAM, but fails to do so

http://bugzilla.novell.com/show_bug.cgi?id=502193 Zheng Chen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zchen@novell.com AssignedTo|bnc-team-screening@forge.pr |carnold@novell.com |ovo.novell.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.

bugzilla_noreply＠novell.com

12 May 12 May

08:24

New subject: [Bug 502193] Xen kernel reports to be capable of suspend to RAM, but fails to do so

http://bugzilla.novell.com/show_bug.cgi?id=502193 User jbeulich@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c4 --- Comment #4 from Jan Beulich 2009-05-12 02:24:38 MDT --- Using UI or generic system scripts to invoke this won't work at present - these components simply aren't ready to deal with the Xen specifics here. Directly going through /sys/power/state was reported to work, though, afair. -- 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.

bugzilla_noreply＠novell.com

10:33

New subject: [Bug 502193] Xen kernel reports to be capable of suspend to RAM, but fails to do so

http://bugzilla.novell.com/show_bug.cgi?id=502193 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c5 --- Comment #5 from Tamás Németh 2009-05-12 04:33:37 MDT --- (In reply to comment #4)

...

Using UI or generic system scripts to invoke this won't work at present - these components simply aren't ready to deal with the Xen specifics here. Directly going through /sys/power/state was reported to work, though, afair.

As you can see, the /sys/power/state method didn't work either (at least for me). -- 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.

bugzilla_noreply＠novell.com

14:24

New subject: [Bug 502193] Xen kernel reports to be capable of suspend to RAM, but fails to do so

http://bugzilla.novell.com/show_bug.cgi?id=502193 User jbeulich@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c6 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nice@titanic.nyme.hu --- Comment #6 from Jan Beulich 2009-05-12 08:24:27 MDT --- Oh, sorry, I somehow managed to skip that paragraph when reading. For that case, a combined kernel/hypervisor log (obtained over serial) will be needed, with "loglvl=all guest_loglvl=all" added to the Xen command line, and with 'd' sent from the serial terminal once the box appears to hang after wakeup. -- 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.

bugzilla_noreply＠novell.com

13 May 13 May

13:01

New subject: [Bug 502193] Xen kernel reports to be capable of suspend to RAM, but fails to do so

http://bugzilla.novell.com/show_bug.cgi?id=502193 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c7 Tamás Németh changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nice@titanic.nyme.hu | --- Comment #7 from Tamás Németh 2009-05-13 07:01:40 MDT --- (In reply to comment #6)

...

Oh, sorry, I somehow managed to skip that paragraph when reading. For that case, a combined kernel/hypervisor log (obtained over serial) will be needed, with "loglvl=all guest_loglvl=all" added to the Xen command line, and with 'd' sent from the serial terminal once the box appears to hang after wakeup.

What commandline options do I have to give to xen and the kernel? Fortunately my notebook has a serial port, and I was even able to communicate with my colleague's machine via minicom but I haven't seen the Xen startup messages (and noting else either) on the remote machine so far. I was unsuccessful with these settings: ###Don't change this comment - YaST2 identifier: Original name: xen### title Xen -- openSUSE 11.1 - 2.6.27.21-0.1 root (hd0,0) kernel /boot/xen.gz com1=9600, 8n1 console=com1 loglvl=all guest_loglvl=all module /boot/vmlinuz-2.6.27.21-0.1-xen root=/dev/disk/by-id/ata-HTS541010G9SA00_MP2ZX0XLG71D3S-part1 resume=/dev/disk/by-id/ata-HTS541010G9SA00_MP2ZX0XL1D3S-part2 splash=silent showopts vga=0x31a module /boot/initrd-2.6.27.21-0.1-xen What do I have to change? -- 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.

bugzilla_noreply＠novell.com

13:19

New subject: [Bug 502193] Xen kernel reports to be capable of suspend to RAM, but fails to do so

http://bugzilla.novell.com/show_bug.cgi?id=502193 User jbeulich@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c8 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nice@titanic.nyme.hu --- Comment #8 from Jan Beulich 2009-05-13 07:19:08 MDT --- The options look fine (apart from the stray space after the comma in com1=, which might well be an issue with how you inserted that information here), and there are no kernel options needed for this to work. Does the serial port use the usual port and irq? Btw, while I have no reason to believe this works, I never ran Xen's console at this low a baud rate... -- 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.

bugzilla_noreply＠novell.com

14:12

New subject: [Bug 502193] Xen kernel reports to be capable of suspend to RAM, but fails to do so

http://bugzilla.novell.com/show_bug.cgi?id=502193 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c9 Tamás Németh changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nice@titanic.nyme.hu | --- Comment #9 from Tamás Németh 2009-05-13 08:12:06 MDT --- (In reply to comment #8)

...

The options look fine (apart from the stray space after the comma in com1=, which might well be an issue with how you inserted that information here), and there are no kernel options needed for this to work. Does the serial port use the usual port and irq? Btw, while I have no reason to believe this works, I never ran Xen's console at this low a baud rate...

Finally I was successful with these settings: kernel /boot/xen.gz com1=38400,8n1,0x3f8,4 console=com1 loglvl=all guest_loglvl=all I saw a lot of output on the remote machine. Then after booting, I issued the command: echo mem > /sys/power/state The machine went suspended successfully (?), but after turning it on, I saw no messages on the serial console despite that I pressed the d key (on the remote machine, of course). I also pressed enter afterwards but still no results. -- 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.

bugzilla_noreply＠novell.com

14:40

New subject: [Bug 502193] Xen kernel reports to be capable of suspend to RAM, but fails to do so

http://bugzilla.novell.com/show_bug.cgi?id=502193 User jbeulich@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c10 Jan Beulich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nice@titanic.nyme.hu --- Comment #10 from Jan Beulich 2009-05-13 08:40:19 MDT --- Did you make sure input was going to Xen (you'd want to do this probably before suspending the system)? If there's indeed no output *and* no response to 'd' (or any other of the valid keys), then I'm afraid we won't have much to investigate the issue further). One other thing you could try would be to make Xen use *and* keep using (across Dom0 boot) the VGA console (in text mode), and invoke suspend from a console (not from a console window in the GUI), to see if any post-suspend output turns up there. For that, you'd need to modify your Xen command line to kernel /boot/xen.gz com1=38400,8n1,0x3f8,4 console=vga,com1 vga=text-80x25,keep loglvl=all guest_loglvl=all or alternatively, removing the serial stuff altogether kernel /boot/xen.gz console=vga vga=text-80x25,keep loglvl=all guest_loglvl=all -- 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.

bugzilla_noreply＠novell.com

14 May 14 May

08:48

New subject: [Bug 502193] Xen kernel reports to be capable of suspend to RAM, but fails to do so

http://bugzilla.novell.com/show_bug.cgi?id=502193 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c11 --- Comment #11 from Tamás Németh 2009-05-14 02:48:34 MDT --- (In reply to comment #10)

...

Did you make sure input was going to Xen (you'd want to do this probably before suspending the system)?

OK, I will try that today.

...

or alternatively, removing the serial stuff altogether

kernel /boot/xen.gz console=vga vga=text-80x25,keep loglvl=all guest_loglvl=all

I've already tried this one, but the dom0 system didn't boot either. -- 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.

bugzilla_noreply＠novell.com

15 May 15 May

13:08

New subject: [Bug 502193] Xen kernel reports to be capable of suspend to RAM, but fails to do so

http://bugzilla.novell.com/show_bug.cgi?id=502193 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c12 --- Comment #12 from Tamás Németh 2009-05-15 07:08:44 MDT --- Created an attachment (id=292456) --> (http://bugzilla.novell.com/attachment.cgi?id=292456) pressing d (In reply to comment #10)

...

Did you make sure input was going to Xen (you'd want to do this probably before suspending the system)?

Finally, I read this: http://en.opensuse.org/How_to_Capture_Xen_Hypervisor_and_Kernel_Messages_usi... So I switched to /boot/xen-dbg.gz instead of /boot/xen.gz, and I also modified the kernel command line and then pressed ctrl+a six times. This way I connected to Xen from remotely (see the attached message, which is the result of pressing 'd' BEFORE gonig to S3 state). -- 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.