Summary: | Resume from suspend to ram fails on G71 [Quadro FX 1500M] (rev a1) | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Cristian Rosa <cristianrosa> | ||||||
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||||
Severity: | major | ||||||||
Priority: | medium | ||||||||
Version: | unspecified | ||||||||
Hardware: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Created attachment 39015 [details]
The X.org log of the crash
I'm using kernel from nouveau's git 2.6.36-rc5 It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report. In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one. Thanks, The Nouveau Team |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 39014 [details] dmesg output Resume from suspend to ram using swsusp fails after 2 suspend/resume cycles. The first time always work flawlessly, the second time, it works but the screen is corrupted for a few seconds after a refresh, the third time it just hangs and the screen is corrupted. (it might be possible to do a vt switch but not always, it is very unpredictible). In dmesg I get many PGRAPH_ERROR messages, check attached dmesg.log