Bug 625982
| Summary: | nouveau cant resume after suspend | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mark Lamers <mark.r.lamers> | ||||||||||||||||||
| Component: | xorg-x11-drv-nouveau | Assignee: | Ben Skeggs <bskeggs> | ||||||||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||||||
| Priority: | low | ||||||||||||||||||||
| Version: | 13 | CC: | airlied, ajax, bskeggs | ||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||
| Last Closed: | 2011-06-28 14:18:27 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: |
|
||||||||||||||||||||
Created attachment 440083 [details]
Xorg.log on normall boot
Created attachment 440084 [details]
lshal ouput
Created attachment 440085 [details]
lspci output
Created attachment 440086 [details]
pm-suspend.log
Created attachment 440087 [details]
dmidecode
Can I see dmesg output please? Preferably from after resume, if you can manage to get it somehow. Created attachment 440348 [details]
dmesg after failed resume from hybernation
Ah, this is a known bug with your kernel. Give this a try: http://koji.fedoraproject.org/koji/buildinfo?buildID=191473 Created attachment 440558 [details]
Succesfull test with kernel-2.6.24.5
Thx Ben,
This works great. Are there any symptoms I should look for in case of advising others with similar issues?
\\ML
The tell-tale sign is: [drm] nouveau 0000:01:00.0: Reinitialising engines... [drm] nouveau 0000:01:00.0: Restoring GPU objects... [drm] nouveau 0000:01:00.0: Restoring mode... [drm] nouveau 0000:01:00.0: Couldn't find matching output script table [drm] nouveau 0000:01:00.0: Couldn't find matching output script table [drm] nouveau 0000:01:00.0: Couldn't find matching output script table However, not all cases where the "Couldn't find.." message are shown are indicative of a problem, it's perfectly normal in some configurations. This case though, is a bug :) This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 440082 [details] Xorg.log on resume Description of problem: After a successful suspend the screen and keyboard wont come up on resume. All programs come up well and i even can log in trough ssh Version-Release number of selected component (if applicable): xorg-x11-drv-nouveau-0.0.16-7.20100423git13c1043.fc13.x86_64 How reproducible: This happends always Steps to Reproduce: 1. Suspend laptop 2. Resume latop Actual results: Screen blank, no keyboard Expected results: Normal operation Additional info: