Bug 821114
Summary: | netbook with GMA 500 GPU freezes when I try to suspend | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Aram Agajanian <agajan> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | david, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-11 12:20:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Aram Agajanian
2012-05-12 03:40:39 UTC
The bug fixed in the web pages at the following URLs may be the same issue. http://lists.freedesktop.org/archives/dri-devel/2012-May/023033.html http://lists.freedesktop.org/archives/dri-devel/2012-May/023152.html Thanks for the links. The patch referenced there is queued up to be included in the 3.3.8 and 3.4.1 stable kernel releases. F17 will pick up one of those shortly. Your testing feedback when they are built would be much appreciated. Fedora 17 has been installed on my netbook. Suspend and resume are working fine on my netbook with kernel-3.4.0-1.fc17.i686.rpm. Thank you for letting us know. Same error here, upgraded to 3.4.0-1 kernel but resume still fails with a black screen and computer not responding (not even CAP LOCK key). Any way to debug? Thanks! (In reply to comment #5) > Same error here, upgraded to 3.4.0-1 kernel but resume still fails with a > black screen and computer not responding (not even CAP LOCK key). > Any way to debug? I encountered a similar problem this evening on my netbook. I just filed bug 831462. |