New stable release - 185.18.36 - should replace 185.18.31 ASAP

Bug #408561 reported by Noel J. Bergman
52
This bug affects 7 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-180 (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Jaunty by Andrew Cranwell

Bug Description

As per ftp://download.nvidia.com/XFree86/Linux-x86_64/latest.txt, this is the new, latest, stable driver.

See http://www.nvnews.net/vbulletin/showthread.php?t=137697
       http://www.nvnews.net/vbulletin/showthread.php?p=2071497#post2071497

This version finally fixes the problems with mobile GPUs that have plagued the 185 series lately. I have tested it on Hardy, Intrepid, Jaunty and Karmic. Please update this ASAP. It is important to replace the defective .31 build as soon as possible.

It is also in the NVIDIA-VDPAU PPA (https://launchpad.net/~nvidia-vdpau/+archive/ppa), as well as being at ftp://download.nvidia.com/XFree86/Linux-x86_64/185.18.36.

--------------------------------------------------------------------------------

Release highlights since 185.18.31:

    * Fixed a bug that caused kernel panics when starting X on some mobile GPUs.
    * Fixed an interaction problem between VDPAU and PowerMizer when using VDPAU solely as a display mechanism, and not to decode video streams. The GPU performance level should now be raised, if required, in this scenario.
    * Fixed VDPAU to avoid "display preemption" in some cases where a VdpOutputSurface is deleted while it is still active (either queued or visible) in a VdpPresentationQueue. In particular, this can occur in MPlayer when using the "-fs" option, and could completely prevent VDPAU from operating successfully, depending on the exact timing conditions.

Release highlights since 185.18.29:

    * Fixed a crash on certain mobile GPUs.

Release highlights since 185.18.14:

    * Added code to forcibly terminate long-running CUDA kernels when Ctrl-C is pressed.
    * Fixed a bug that could cause occasional memory corruption problems or segmentation faults when running OpenGL applications on Quadro GPUs.
    * Fixed a deadlock in the OpenGL library that could be triggered in certain rare circumstances on Quadro GPUs.
    * Fixed an interaction problem between PowerMizer and CUDA applications that caused the performance level to be reduced while the CUDA kernel is running.
    * Made CUDA compute-exclusive mode persistent across GPU resets.
    * Fixed the order of outputs in the GPUScaling nvidia-settings property.
    * Fixed a bug that caused graphics corruption in some OpenGL applications when the Unified Back Buffer is enabled the application window is moved.
    * Fixed a bug that caused glXGetVideoSyncSGI, glXWaitVideoSyncSGI, and glXGetRefreshRateSGI to operate on the wrong screen when there are multiple X screens.
    * Fixed a bug that causes corruption or GPU errors when an application paints a redirected window whose background is set to ParentRelative on X.Org servers older than 1.5. This was typically triggered by running Kopete while using Compiz or Beryl.
    * Fixed a bug in VDPAU that could cause visible corruption when decoding H.264 clips with alternating frame/field coded reference pictures, and a video surface is concurrently removed from the DPB, and re-used as the decode target, in a single decode operation. This affected all GPUs supported by VDPAU.
    * Fixed a bug in VDPAU that could cause visible corruption near the bottom edge of the picture when decoding VC-1 advanced profile clips whose heights are not exact multiples of 16 pixels, on G98 and MCP7x (IGP) GPUs.
    * Enhanced VDPAU to better handle corrupt/invalid H.264 bitstreams on G84, G86, G92, G94, G96, or GT200 GPUs. This should prevent most cases of "display preemption" that are caused by bitstream errors.
    * Fixed an X server crash when using the VDPAU overlay-based presentation queue and VT-switching away from the X server.
    * Enhanced VDPAU's detection of the GPU's video decode capabilities.
    * Fixed a bug in VDPAU that could cause ghosting/flashing issues when decoding H.264 clips, in certain full DPB scenarios, on G98 and MCP7x.
    * Fixed VDPAU to detect an attempt to destroy the VdpDevice object when other device-owned objects still exist. VDPAU now triggers "display preemption", and returns an error, when this occurs.
    * Enhanced VDPAU's error handling and resource management in presentation queue creation and operation. This change correctly propagates all errors back to the client application, and avoids some resource leaks.

Tags: karmic
Noel J. Bergman (noeljb)
description: updated
description: updated
Revision history for this message
Noel J. Bergman (noeljb) wrote :
Download full text (3.8 KiB)

crash data:

Aug 3 16:23:41 karmic kernel: [ 20.814640] Pid: 2853, comm: Xorg Tainted: P 2.6.31-5-generic #24-Ubuntu 64577WU
Aug 3 16:23:41 karmic kernel: [ 20.814641] RIP: 0010:[<0000000000000000>] [<(null)>] (null)
Aug 3 16:23:41 karmic kernel: [ 20.814644] RSP: 0018:ffff88012dc15d20 EFLAGS: 00010292
Aug 3 16:23:41 karmic kernel: [ 20.814646] RAX: ffff88012f90e000 RBX: ffff88013604afa8 RCX: 0000000000000001
Aug 3 16:23:41 karmic kernel: [ 20.814648] RDX: ffff8801344ce854 RSI: ffff88012f90e000 RDI: ffff8801347f1000
Aug 3 16:23:41 karmic kernel: [ 20.814649] RBP: ffff88013604af60 R08: ffff8801347f1000 R09: 0000000000000246
Aug 3 16:23:41 karmic kernel: [ 20.814651] R10: 0000000000000010 R11: 0000000000000000 R12: ffff8801344ce850
Aug 3 16:23:41 karmic kernel: [ 20.814653] R13: ffff8801347f1000 R14: 00007fff61d1f670 R15: 0000000000000000
Aug 3 16:23:41 karmic kernel: [ 20.814655] FS: 00007fab318166f0(0000) GS:ffff880028022000(0000) knlGS:0000000000000000
Aug 3 16:23:41 karmic kernel: [ 20.814657] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Aug 3 16:23:41 karmic kernel: [ 20.814659] CR2: 0000000000000000 CR3: 000000012f8d0000 CR4: 00000000000006b0
Aug 3 16:23:41 karmic kernel: [ 20.814661] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Aug 3 16:23:41 karmic kernel: [ 20.814663] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Aug 3 16:23:41 karmic kernel: [ 20.814665] Process Xorg (pid: 2853, threadinfo ffff88012dc14000, task ffff88012f9ac410)
Aug 3 16:23:41 karmic kernel: [ 20.814666] Stack:
Aug 3 16:23:41 karmic kernel: [ 20.814667] ffffffffa0185577 ffff88013604afa8 00000000c1d00001 000000000000000c
Aug 3 16:23:41 karmic kernel: [ 20.814671] <0> 00007fff61d1f670 0000000000000110 ffffffffa01872da 0000000000000020
Aug 3 16:23:41 karmic kernel: [ 20.814674] <0> ffffffffa05816d1 0000000000000110 ffffffffa05812d9 0000000000000110
Aug 3 16:23:41 karmic kernel: [ 20.814678] Call Trace:
Aug 3 16:23:41 karmic kernel: [ 20.814820] [<ffffffffa0185577>] ? _nv007272rm+0xaa/0x314 [nvidia]
Aug 3 16:23:41 karmic kernel: [ 20.814889] [<ffffffffa01872da>] ? _nv019651rm+0x16/0x1c [nvidia]
Aug 3 16:23:41 karmic kernel: [ 20.814999] [<ffffffffa05816d1>] ? _nv003836rm+0x9/0xe [nvidia]
Aug 3 16:23:41 karmic kernel: [ 20.815115] [<ffffffffa05812d9>] ? _nv003802rm+0x179/0x1c2 [nvidia]
Aug 3 16:23:41 karmic kernel: [ 20.815228] [<ffffffffa0581616>] ? _nv003838rm+0x98/0x13e [nvidia]
Aug 3 16:23:41 karmic kernel: [ 20.815347] [<ffffffffa04b523e>] ? _nv007070rm+0x19/0x25 [nvidia]
Aug 3 16:23:41 karmic kernel: [ 20.815457] [<ffffffffa02c30a6>] ? _nv003698rm+0x576/0x5b4 [nvidia]
Aug 3 16:23:41 karmic kernel: [ 20.815576] [<ffffffffa053a181>] ? rm_ioctl+0x2f/0x67 [nvidia]
Aug 3 16:23:41 karmic kernel: [ 20.815667] [<ffffffffa0611aec>] ? nv_kern_ioctl+0x12c/0x450 [nvidia]
Aug 3 16:23:41 karmic kernel: [ 20.815672] [<ffffffff81273e32>] ? copy_user_generic_string+0x32/0x40
Aug 3 16:23:41 karmic kernel: [ 20.815762] [<ffffffffa0611e4c>] ? nv_kern_unlocked_ioctl+0x1c/0x20 [nvidia]
Aug 3 16:23:41 karmic kernel: [ 20.815766...

Read more...

description: updated
summary: - New stable release - 185.18.31 - available
+ New stable release - 185.18.31 - available but see WARNING
Noel J. Bergman (noeljb)
description: updated
Revision history for this message
Noel J. Bergman (noeljb) wrote : Re: New stable release - 185.18.31 - available but see WARNING
Revision history for this message
Philip Muškovac (yofel) wrote :

Confirmed with the ppa version.

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: New → Confirmed
Revision history for this message
Artur Rona (ari-tczew) wrote :

It would be nice that make a transitional package nvidia-graphics-drivers-185/nvidia-glx-185 by upgrading to new upstream release. Then remove nvidia-glx-180 (and related) for not duplicating driver.

Revision history for this message
Noel J. Bergman (noeljb) wrote :

For those who find themselves here having encountered the problem with 185.18.31, please note that there does not appear to be a problem with 190.18.03, so installing 190.* from the PPA may help.

Bryce Harrington (bryce)
tags: added: karmic
Noel J. Bergman (noeljb)
description: updated
summary: - New stable release - 185.18.31 - available but see WARNING
+ New stable release - 185.18.36 - should replace 185.18.31 ASAP
Revision history for this message
U Das (nxb76z7f001) wrote :

Karmic on my Lenovo T61 goes into a blank screen after updating to the -185 driver. Eagerly awaiting the 185.18.36.

Revision history for this message
wavded (wavded) wrote :

Got the black screen as well on my XPS Laptop. Also eagerly await the update.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package nvidia-graphics-drivers-180 - 185.18.36-0ubuntu1

---------------
nvidia-graphics-drivers-180 (185.18.36-0ubuntu1) karmic; urgency=low

  * New upstream release (LP: #408561)
    - Fixed a bug that caused kernel panics when starting X on some mobile GPUs
    - Fixed an interaction problem between VDPAU and PowerMizer when using
      VDPAU solely as a display mechanism, and not to decode video streams. The
      GPU performance level should now be raised, if required, in this scenario.
    - Fixed VDPAU to avoid "display preemption" in some cases where a
      VdpOutputSurface is deleted while it is still active (either queued or
      visible) in a VdpPresentationQueue. In particular, this can occur in
      MPlayer when using the "-fs" option, and could completely prevent VDPAU
      from operating successfully, depending on the exact timing conditions.
  * debian/nvidia-glx-185.preinst:
     - Update to print-architecture rather than print-installation-architecture

 -- Mario Limonciello <email address hidden> Sun, 23 Aug 2009 11:38:08 -0500

Changed in nvidia-graphics-drivers-180 (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Thanks Mario, this update fixed the problem on my T61.

Revision history for this message
Andrew Cranwell (andrew-cranwell) wrote :

Can this please be updated / upgraded / backported / whatever in Jaunty?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.