Bug 703137

Summary: [qxl] linux guest can't get into s3 state
Product: Red Hat Enterprise Linux 6 Reporter: Lubos Kocman <lkocman>
Component: xorg-x11-drv-qxlAssignee: Gerd Hoffmann <kraxel>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: acathrow, alevy, amit.shah, areis, dblechte, michen, mkenneth, mkrcmari, rhod, sandmann, uril, vbenes
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-27 09:24:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 761491, 912287    
Attachments:
Description Flags
console-output (suspended from xorg) none

Description Lubos Kocman 2011-05-09 12:15:01 UTC 
Created attachment 497776 [details]
console-output (suspended from xorg)

Description of problem:

I'm unable to suspend (trough pm-suspend) rhel6x64 guest with qxl driver. Guest is in RHEVM 3.0 (ic116) environment => libvirt managed

It does not seem to be bios related issue (see last line in additional info)

I have also found similar bug at https://bugzilla.redhat.com/show_bug.cgi?id=595647

Version-Release number of selected component (if applicable):

Host:
vgabios-0.6b-3.6.el6.noarch
libvirt-0.8.7-18.el6.x86_64
qemu-kvm-0.12.1.2-2.161.el6.x86_64
vdsm-4.9-64.el6.x86_64
[root@hyper03 qemu]# rpm -qa vgabios qemu-kvm libvirt vdsm seabios
vgabios-0.6b-3.6.el6.noarch
libvirt-0.8.7-18.el6.x86_64
seabios-0.6.1.2-3.el6.x86_64
qemu-kvm-0.12.1.2-2.161.el6.x86_64
vdsm-4.9-64.el6.x86_64


How reproducible:

(Reproducible always)

Steps to Reproduce:
1. Boot qemu-kvm guest (rhel6x64/qxl) (booted trough rhevm in my case)
2. pm-suspend from Xorg (see output of the screenshot)

or

2. pm-suspend from VT => returns me back to shell => Ctrl+Alt+F1 => Xorg is frozen.
  
Actual results:

INFO: task jbd2/vda-1-8.405 blocked for more than 120 seconds
"echo 0 > /proc/sys/kernel/hung_task_temout_secs" disables this message
....
....


Expected results:

In case that S3 is not supported by guest shouldn't be able to proceed pm-suspend and there shouldn't be anything like frozen Xorg. Otherwise suspend should not fail.


Additional info:

qemu_command_line:

/usr/libexec/qemu-kvm -S -M rhel6.0.0 -cpu Conroe -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name RHEL61x64-lk -uuid 390f5002-e6d4-4550-b12e-deeea5b16719 -smbios type=1,manufacturer=Red Hat,product=RHEL,version=6Server-6.1.0.2.el6,serial=33313934-3432-5A43-3230-32343752314C_78:e7:d1:df:9d:30,uuid=390f5002-e6d4-4550-b12e-deeea5b16719 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/RHEL61x64-lk.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2011-05-09T10:26:16 -boot cn -device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 -drive file=/rhev/data-center/40410305-9123-4918-ba0c-07448ebab2ab/f7be7c19-1408-469b-a0df-770c16c70f85/images/f42c6bbd-fe96-42b4-a526-447bd1d61e2e/1b84edea-bd18-45a6-be4c-3c73b7b6445f,if=none,id=drive-virtio-disk0,format=qcow2,serial=b4-a526-447bd1d61e2e,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0 -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=25 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=00:1a:4a:22:3a:00,bus=pci.0,addr=0x3 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/RHEL61x64-lk.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 -usb -spice port=5900,tls-port=5901,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=inputs -k en-us -vga qxl -global qxl-vga.vram_size=67108864 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0


bios debug messages:

handle_dev_destroy_surfaces:
In resume (status=254)
In 32bit resume
Running option rom at c000:0003
VGABios $Id: vgabios.c,v 1.67 2008/01/27 09:44:12 vruppert Exp $^M
VBE Bios $Id: vbe.c,v 1.60 2008/03/02 07:47:21 vruppert Exp $
^MJump to resume vector (2000)
Comment 1 Lubos Kocman 2011-05-09 12:28:59 UTC 
I found out that Xorg crashes only on my localhost where libvirt is not involved.

In libvirt/rhevm env:

1. pm-suspend from console => displays output as it is on screenshot
2. ctrl+alt+f1 returns me back to xorg (xorg is not frozen) ...

But pm-suspend is still running
Comment 6 Suzanne Logcher 2012-02-14 23:09:33 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 7 Amit Shah 2013-02-18 13:16:41 UTC 
Does this reproduce with latest RHEL bits?
Comment 8 Andrew Cathrow 2013-03-10 16:24:12 UTC 
Adding 6.5.0? pending needinfo response
Comment 11 Ronen Hod 2013-03-18 08:38:37 UTC 
Lets assume that this bug will not be fixed in RHEL6.5
Can we support S3/S4 without the fix? Are there workarounds and/or technical-notes that we need to publish, such as alternatives to pm-suspend?
Comment 12 Amit Shah 2013-03-18 08:43:14 UTC 
(In reply to comment #11)
> Lets assume that this bug will not be fixed in RHEL6.5

I'm not sure it'll even reproduce -- this was filed before we did all the work on getting S3/S4 working.

We'd need at least a RHEL 6.3 guest to verify.
Comment 13 Ronen Hod 2013-03-21 09:06:47 UTC 
QE,

Can you please try to reproduce it. There were too many changes since the bug was reported, so let's make sure that it is still valid.
Comment 14 Marian Krcmarik 2013-03-22 22:50:02 UTC 
(In reply to comment #13)
> QE,
> 
> Can you please try to reproduce it. There were too many changes since the
> bug was reported, so let's make sure that it is still valid.

pm-suspend does not do anything.
pm-hibernate seems to hibernate the vm, starting the vm again seems to bring vm back in stage where it was hibernated correctly.
Comment 16 Ronen Hod 2013-05-26 13:10:46 UTC 
6.5 will not support S3, postponed to 6.6.
Comment 18 Ronen Hod 2014-03-27 09:24:26 UTC 
RHEL6 will probably never fully support S3. Closing.