[Bug 502193] New: Xen kernel reports to be capable of suspend to RAM, but fails to do so
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.
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 <nice@titanic.nyme.hu> 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.
http://bugzilla.novell.com/show_bug.cgi?id=502193 Zheng Chen <zchen@novell.com> 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.
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 <jbeulich@novell.com> 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.
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 <nice@titanic.nyme.hu> 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.
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 <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nice@titanic.nyme.hu --- Comment #6 from Jan Beulich <jbeulich@novell.com> 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.
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 <nice@titanic.nyme.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nice@titanic.nyme.hu | --- Comment #7 from Tamás Németh <nice@titanic.nyme.hu> 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.
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 <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nice@titanic.nyme.hu --- Comment #8 from Jan Beulich <jbeulich@novell.com> 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.
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 <nice@titanic.nyme.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nice@titanic.nyme.hu | --- Comment #9 from Tamás Németh <nice@titanic.nyme.hu> 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.
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 <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nice@titanic.nyme.hu --- Comment #10 from Jan Beulich <jbeulich@novell.com> 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.
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 <nice@titanic.nyme.hu> 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.
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 <nice@titanic.nyme.hu> 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.
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#c13 --- Comment #13 from Tamás Németh <nice@titanic.nyme.hu> 2009-05-15 07:10:20 MDT --- Created an attachment (id=292457) --> (http://bugzilla.novell.com/attachment.cgi?id=292457) going to S3 Then I issued the 'echo mem > /sys/power/state' command, but this time my machine absolutely failed to reach the S2 state. It stayed powered on, and gave me the attached output. -- 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=502193 Tamás Németh <nice@titanic.nyme.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nice@titanic.nyme.hu | -- 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=502193 User jbeulich@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c14 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |nice@titanic.nyme.hu --- Comment #14 from Jan Beulich <jbeulich@novell.com> 2009-05-18 02:05:53 MDT --- Yes, these assertions are known to exist. You need to either turn PCI MSI off, or switch back to the non-debug hypervisor. -- 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=502193 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c15 --- Comment #15 from Tamás Németh <nice@titanic.nyme.hu> 2009-05-21 09:20:49 MDT --- OK, I switched bac to the non-debug hypervisor. Before suspend I was able to take the console, and the 'd' key worked, too: (XEN) *** Serial input -> Xen (type 'CTRL-a' three times to switch input to DOM0) (XEN) 'd' pressed -> dumping registers (XEN) (XEN) *** Dumping CPU0 host state: *** (XEN) ----[ Xen-3.3.1_18494_03-1.8 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e008:[<ffff828c8013516b>] default_idle+0x2b/0x40 (XEN) RFLAGS: 0000000000000246 CONTEXT: hypervisor (XEN) rax: 0000000000000000 rbx: ffff828c8042ff28 rcx: 0000000000000000 (XEN) rdx: ffff828c80447780 rsi: ffff828c80226560 rdi: 0000000000000000 (XEN) rbp: ffff828c8042ff28 rsp: ffff828c8042fef8 r8: 0000000000000003 (XEN) r9: ffff8300be6fe280 r10: 0000000000000000 r11: ffff8300be6fe288 (XEN) r12: ffff828c801fdfa0 r13: ffff828c80447780 r14: ffff828c80226100 (XEN) r15: 0000000001c9c380 cr0: 000000008005003b cr4: 00000000000026b0 (XEN) cr3: 0000000009a10000 cr2: ffff8800b1076838 (XEN) ds: 002b es: 002b fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) Xen stack trace from rsp=ffff828c8042fef8: (XEN) ffff828c801391c3 0000000000000000 ffff828c80226120 ffff8300be602080 (XEN) ffff8300be602080 0000001397d9ca20 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000001 (XEN) 0000000000000246 0000c6c600000000 0000000000000000 ffff8800b28b8478 (XEN) 0000000000000000 ffffffff802073aa ffff8800b2889f20 0000000000000000 (XEN) 0000000000000001 0000010000000000 ffffffff802073aa 000000000000e033 (XEN) 0000000000000246 ffff8800b2889f08 000000000000e02b 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) ffff8300be602080 (XEN) Xen call trace: (XEN) [<ffff828c8013516b>] default_idle+0x2b/0x40 (XEN) [<ffff828c801391c3>] idle_loop+0xb3/0xd0 (XEN) (XEN) No guest context (CPU0 is idle). (XEN) (XEN) *** Dumping CPU1 host state: *** (XEN) ----[ Xen-3.3.1_18494_03-1.8 x86_64 debug=n Not tainted ]---- (XEN) CPU: 1 (XEN) RIP: e008:[<ffff828c8013516b>] default_idle+0x2b/0x40 (XEN) RFLAGS: 0000000000000246 CONTEXT: hypervisor (XEN) rax: 0000000000000080 rbx: ffff8300beabff28 rcx: 0000000000000000 (XEN) rdx: ffff828c80447780 rsi: ffff828c80228560 rdi: 0000000000002000 (XEN) rbp: ffff8300beabff28 rsp: ffff8300beabfef8 r8: 0000000000000003 (XEN) r9: ffff8300be6fe380 r10: 0000000000000000 r11: ffff8300be6fe398 (XEN) r12: ffff828c801fdfa0 r13: ffff828c80447780 r14: ffff828c80228100 (XEN) r15: 0000000001c9c380 cr0: 000000008005003b cr4: 00000000000026b0 (XEN) cr3: 0000000017907000 cr2: ffff8800a0789eb0 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e010 cs: e008 (XEN) Xen stack trace from rsp=ffff8300beabfef8: (XEN) ffff828c801391c3 0000000000000000 ffff828c80228120 ffff8300bf5fa080 (XEN) ffff8300bf5fa080 000000139f7b28ad 0000000000000000 ffffffff80738a20 (XEN) ffffffff807365f0 ffffffffffffffff 0000000000000000 0000000000000000 (XEN) 0000000000000246 00006a6a80757080 ffffffff80757d80 ffffffff807c5d18 (XEN) 0000000000000000 ffffffff802073aa ffffffff8070bf48 0000000000000000 (XEN) 0000000000000001 0000010000000000 ffffffff802073aa 000000000000e033 (XEN) 0000000000000246 ffffffff8070bf30 000000000000e02b ffffffffffffffff (XEN) 0000000000000000 ffffffffffffffff 0000000000000000 ffffffff00000001 (XEN) ffff8300bf5fa080 (XEN) Xen call trace: (XEN) [<ffff828c8013516b>] default_idle+0x2b/0x40 (XEN) [<ffff828c801391c3>] idle_loop+0xb3/0xd0 (XEN) (XEN) No guest context (CPU1 is idle). (XEN) -- 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=502193 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c16 Tamás Németh <nice@titanic.nyme.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|nice@titanic.nyme.hu | --- Comment #16 from Tamás Németh <nice@titanic.nyme.hu> 2009-05-21 09:29:20 MDT --- 'echo mem > /sys/power/state' also seemed to work: (XEN) Preparing system for ACPI S3 state.Freezing cpus ... (XEN) Prepare to bring CPU1 down... (XEN) Breaking affinity for irq 16 (XEN) Breaking affinity for irq 45 (XEN) Cannot set affinity for irq 224 (XEN) CPU 1 is now offline (XEN) CPU1 is down (XEN) Entering ACPI S3 state. And this happened, when I powered it up, to restore from suspension: (XEN) Finishing wakeup from ACPI S3 state. However, neither Ctrl+A nor the 'd' key worked afterwards. We were trying to get some more feedback via the serial console, and then after a minute or so... The system regained its consciousness somehow, but some kernel subsystems might remained in a broken state, since dmesg was full of "time went backwards" messages, bash was unable to run programs (e.g. when I wanted to issue 'shutdown' or 'less', bash was complaining about some I/O error), 'ls' was amazingly working, but it was unable to gain user/group, MTIME and even permission bit informations for some(!!!) (most) files, and it showed question marks instead. Finally I had to turn off the machine with the unusable system. -- 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=502193 User jbeulich@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c17 --- Comment #17 from Jan Beulich <jbeulich@novell.com> 2009-05-25 01:55:13 MDT --- Did you also try with MSI disabled (msi=0 on the Xen command line), as from your behavioral description I'd assume some device(s) do(es)n't get its(their) interrupts re-setup correctly? Also, your hypervisor seems pretty old (not sure whether a maintenance update for 11.1 was already made available - if not, trying the SLE11 one from http://developer.novell.com/wiki/index.php/Xen_technical_preview might be a good idea too). -- 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=502193 User nice@titanic.nyme.hu added comment http://bugzilla.novell.com/show_bug.cgi?id=502193#c18 --- Comment #18 from Tamás Németh <nice@titanic.nyme.hu> 2009-05-25 10:15:55 MDT --- (In reply to comment #17)
Did you also try with MSI disabled (msi=0 on the Xen command line), as from your behavioral description I'd assume some device(s) do(es)n't get its(their) interrupts re-setup correctly?
Also, your hypervisor seems pretty old (not sure whether a maintenance update for 11.1 was already made available - if not, trying the SLE11 one from
http://developer.novell.com/wiki/index.php/Xen_technical_preview
might be a good idea too).
I tried that new hypervisor AND msi=0, but still didn't work. This time the notebok display remained in the powered down state. Caps lock worked, otherwise keypressings led to beepings. I had to switch of the machine. -- 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=502193 Jason Douglas <jdouglas@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcollingridge@novell.com, | |jdouglas@novell.com QAContact|jdouglas@novell.com |qa@suse.de -- 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=502193 https://bugzilla.novell.com/show_bug.cgi?id=502193#c21 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |nice@titanic.nyme.hu --- Comment #21 from Jan Beulich <jbeulich@novell.com> 2011-01-14 08:06:06 UTC --- Did you ever try 11.3 or one of the 11.4 milestones? I'd generally expect this to work (the raw interface only as was the case with 11.1), and if anything we'd only be likely to look into fixing issues on those newer distros. -- 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=502193 https://bugzilla.novell.com/show_bug.cgi?id=502193#c22 Charles Arnold <carnold@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |CLOSED InfoProvider|nice@titanic.nyme.hu | Resolution| |NORESPONSE --- Comment #22 from Charles Arnold <carnold@novell.com> 2011-02-02 17:09:28 UTC --- Please try upgrading. -- 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