Bug 541603

Summary:

compositing breaks suspend/hibernate on thinkpad t500

Product:

[Fedora] Fedora

Reporter:

Paolo Bonzini <pbonzini>

Component:

xorg-x11-drv-intel

Assignee:

Adam Jackson <ajax>

Status:

CLOSED NEXTRELEASE

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

medium

Docs Contact:

Priority:

low

Version:

CC:

ajax, dougsland, gansalmon, itamar, kernel-maint, mcepl, xgl-maint

Target Milestone:

---

Target Release:

---

Hardware:

All

OS:

Linux

Whiteboard:

card_GM45

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2010-05-28 14:24:49 UTC

Type:

---

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
Xorg.0.log	none

Description Paolo Bonzini 2009-11-26 12:57:08 UTC

Description of problem:
With compositing enabled, suspend/hibernate will only work 40-60% of the time.

Version-Release number of selected component (if applicable):
kernel-2.6.31.5-127.fc12
xorg-x11-drv-intel-2.7.0-7.fc11.x86_64.rpm
xorg-x11-drivers-7.3-11.fc11.x86_64.rpm
mesa-dri-drivers-7.6-0.1.fc11.i586.rpm
mesa-dri-drivers-7.6-0.1.fc11.x86_64.rpm

How reproducible:
40-60%

Steps to Reproduce:
1. enable compositing
2. suspend
3. hibernate
  
Actual results:
Video remains black.

Expected results:
Systems come up from sleep.

Additional info:
I think applications run but I'm not sure.  I haven't tried switching VT and rebooting from there.

Comment 1 Paolo Bonzini 2009-11-26 12:57:33 UTC

Worked in F11.  Downgrading kernel to F11's doesn't seem to fix the problem.

Comment 2 Matěj Cepl 2009-11-27 16:52:47 UTC

Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 3 Paolo Bonzini 2009-11-27 17:45:08 UTC

Just to avoid multiple iterations, is there anything else I can attach from the power management log?

Thanks!

Comment 4 Matěj Cepl 2009-11-27 22:41:10 UTC

(In reply to comment #3)
> Just to avoid multiple iterations, is there anything else I can attach from the
> power management log?

This is my standard blurb requesting information (you must be new here, that you haven't met it thousand times ;)). I think it should cover most of our needs, but of course, who knows where will the track lead us.

So, no, I think this should be OK for now.

Comment 5 Paolo Bonzini 2009-11-30 08:32:20 UTC

Created attachment 374704 [details]
Xorg.0.log

heh, no, I've seen the blurb already but I doubt Xorg.log adds much. :-(

I have no xorg.conf.

Comment 6 Paolo Bonzini 2009-12-03 20:16:47 UTC

Sorry, wrong versions.  The one in the original post are the ones that worked.

The failing ones are:

xorg-x11-drv-intel-2.9.1-1.fc12
xorg-x11-drivers-7.3-13.fc12
mesa-dri-drivers-7.6-0.13.fc12

Comment 7 Chris Campbell 2010-01-23 22:23:34 UTC


-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 8 Paolo Bonzini 2010-05-27 07:24:03 UTC

Seems to work in F13.

Comment 9 Matěj Cepl 2010-05-28 14:24:49 UTC

Thank you for letting us know.