Video mode corrupted after resume from suspend to RAM

[Jarno Suni]

Binary package hint: xserver-xorg-video-nouveau

After the video mode corruption, I could only restart by Alt-SysRq-s Alt-SysRq-u Alt-SysRq-b.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: xserver-xorg-video-nouveau 1:0.0.15+git20100219+9b4118d-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Thu Apr 22 12:40:34 2010
DkmsStatus: Error: [Errno 2] No such file or directory
EcryptfsInUse: Yes
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=e69d90ac-3845-4f87-a993-e531fcd2510b ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: xserver-xorg-video-nouveau
dmi.bios.date: 04/25/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: MS-7051
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd04/25/2005:svn:pn:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7051:rvr:cvn:ct3:cvr:
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: lucid
 architecture: i686
 kernel: 2.6.32-21-generic

[Jarno Suni (jarnos)]

Could xserver-xorg-video-nv driver be used as a workaround? At least the driver worked in Karmic for my hardware.

[Chris Halse Rogers (raof)]

> Could xserver-xorg-video-nv driver be used as a workaround? At least the
> driver worked in Karmic for my hardware.
>

Absolutely - check out
https://wiki.ubuntu.com/X/Troubleshooting/Nouveau#Reverting to the -nv
driver

[Jarno Suni (jarnos)]

Thanksfor the information. I can not always reproduce the bug. It may happen at least when Xfce power manager is used for suspending and screen locking is set in its preferences and random screensaver is used. I have not tried the nv drive in Lucid, yet.

[Daniel Hahler (blueyed)]

Linking to bug 569122 - might be related.

Can you provide a screenshot / photo of the distortion?

[Jarno Suni (jarnos)]

I switched to using the nv driver and video mode is still corrupted somehow after resume.

[Jarno Suni (jarnos)]

Desktop is shown in two areas partly, and windows come visible only when I switch to them by alt-tab. Mouse cursor is big messy rectangle and mouse can move only within a third rectangle area. That does not show in screenshot, althought I can take a screenshot.

[Jarno Suni (jarnos)]

The previous comment applies to the case when using nv driver.

[Jarno Suni (jarnos)]

Hello! Apparently this bug occurs with both open source drivers. nv driver worked in 9.10. Can anyone help with this bug? Maybe this bug should be reported against a third package? Is there something wrong in /usr/lib/pm-utils/sleep.d/99video?

[Chris Parker (cparke)]

For me, with a Nvidia Quadro NVS 50 card, I have this bug with suspend/hibernate the Nouveau video driver also, but these suspend/hibernate functions also work perfectly with the VESA and NV drivers on Ubuntu 10.10 Maverick. The NV driver is slower than Nouveau, of course (ex: play an HD movie file), but otherwise functions correctly.

[Bryce Harrington (bryce)]

Likely this bug is something in the linux kernel's nouveau drm driver. If that's true, then booting a newer version of the kernel might resolve it. Has anyone tested if this issue still exists with Lucid 10.04.4?

As we're on the cusp of the next LTS release, it would be worth testing if this issue exists in the 12.04 beta. This can be checked using a USB live image. You can get it at http://cdimage.ubuntu.com/daily/current/, and use USB Disk Creator to make a boot drive. Please update this bug report once you've tested. (If you've already tested any version of ubuntu newer than Lucid and already know it works, that's sufficient testing, just mention that here.)

[bugbot (bugbot)]

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.