nvidia 1.0.9629 crashes X

Bug #74146 reported by chantra
6
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.19 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: nvidia-glx

the actual feisty nvidia-glx is kind of buggy.

see for instance:
http://www.nvnews.net/vbulletin/showthread.php?t=81316

known bug which is triggered when making a specific type of mode change while using a DFP, and will be resolved in the next driver release. The current workarounds are to either change to the mode you need with xrandr or downgrade to an older driver version.

How to make X crash: simply start a game which modify your resolution.

This issue makes me wonder if feisty should jump directly to the actual beta driver 1.0.9742

Revision history for this message
chantra (chantra) wrote :

1.0-9631 has been released since the 4th of december.
Changelog seems to say that the bug is fixed:
Release Highlights

    * Fixed an OpenGL crash on some GeForce 3 and GeForce 4 GPUs.
    * Fixed an X server crash starting some fullscreen OpenGL games.
    * Improved interaction with newer Linux kernels.

Revision history for this message
Daniel Hahler (blueyed) wrote :

I've been using 1.0-9631 through an unofficial repository (http://www.albertomilone.com/drivers/edgy/nonlegacy/32bit) and it indeed fixed the crashing bug.

Revision history for this message
Randakar (randakar) wrote :

I appear to be having similar problems. I turned on the 'desktop-effects' stuff yesterday and it turns my machine into a brick after I login. I get some interesting 'Xid' messages in syslog (attached).

I already had problems with the screensaver kicking in and hanging the machine, and of late it appears usplash and these drivers have begun a catfight about resolutions, as usplash suddenly turns to blueish (kubuntu) snow halfway during boot.

More worrying is that these crashes appear to be causing filesystem corruption. At first it was not clear to me what was happening but after such a crash I had some really odd behaviour that cleared up after running an fsck. (which found errors, I might add).

Revision history for this message
Randakar (randakar) wrote :

Note that I am using a DFP device, as describe in that nv forum comment.

Revision history for this message
Jason Fergus (leech-sisna) wrote :

I will confirm this bug, and it happens on CRT screens as well. I've tried it with both Planet Penguin Racer and atari800 emulator. The 9631 driver fixes the issue.

Revision history for this message
chantra (chantra) wrote :

As it has been confirmed by others, I guess I can switch the bug to confirm.

I still have my edgy system up and running so I will be waiting for the latest nvidia drivers to get included in the distro.

Changed in linux-restricted-modules-2.6.19:
status: Unconfirmed → Confirmed
Revision history for this message
chantra (chantra) wrote :

1.0.9631 is now out. Closing the bug

Changed in linux-restricted-modules-2.6.19:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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