10de:0244 frozen screen, Xorg semi-hang after resuming from suspend

[roothorick]

Every time, if I'm in full GNOME 3 (not fallback), suspend the system, when it comes back the X server screen is frozen at the lockscreen, which is completely and utterly unresponsive. The X server is still sort-of-there; I can VT-switch, and connect X clients to it from a shell (testing with glxgears) but they don't appear on screen, and appear to get stuck.

Behavior does not occur if running in fallback (no effects).

I went so far as to kill -STOP gdm-session-manager and kill everything connected to the X server, and there was no change whatsoever in the visual on X's screen.

I can recover the system by killing gnome-session, triggering gdm to kill and restart the X server, but I lose my logged in session and any running applications in the process, dropping me back to the gdm login screen.

Am about to try removing libgl1-mesa-dri-experimental and see if behavior changes.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2
ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Mon Feb 18 23:17:14 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation C51 [GeForce Go 6150] [10de:0244] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:30e5]
InstallationDate: Installed on 2013-02-16 (2 days ago)
InstallationMedia: This
MachineType: Hewlett-Packard HP Pavilion tx2000 Notebook PC
MarkForUpload: True
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic root=UUID=9c2e9bfa-216e-4f0c-a280-822b1a8647ec ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-video-nouveau
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.08
dmi.board.name: 30E5
dmi.board.vendor: Quanta
dmi.board.version: 88.0A
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.08:bd04/18/2008:svnHewlett-Packard:pnHPPaviliontx2000NotebookPC:pvrRev1:rvnQuanta:rn30E5:rvr88.0A:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion tx2000 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.42-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.0.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2
xserver.bootTime: Mon Feb 18 23:06:35 2013
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output LVDS-1 TV-1 VGA-1
xserver.version: 2:1.13.2-0ubuntu2
xserver.video_driver: nouveau

[roothorick (8-roothorick-gmail-com)]

Not sure why there is no upgrade log... I manually upgraded from 12.10 by modifying sources.list and dist-upgrade'ing.

[roothorick (8-roothorick-gmail-com)]

No change in behavior after removing libgl1-mesa-dri-experimental. Will just work in fallback mode for the time being.

[penalvch (penalvch)]

Ben A, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[roothorick (8-roothorick-gmail-com)]

Ran it from USB, put it to sleep and brought it back, it appeared to recover no problem.

I'm still keeping the machine on Windows 8 due to wireless problems unfortunately.

[penalvch (penalvch)]

Ben A, thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Saucy Salamander.

This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

Regarding the wireless problem, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.