Comment 257 for bug 269904

Revision history for this message
selkovjr (selkovjr-observercentral) wrote : Re: Screen refresh problems with nvidia on intrepid

I was about to go back to 177 and report failure with 180.11 when I noticed the announcements that 180.44 is offered for testing. Which is what's happening presently. It is certainly too early for making conclusions, but I noticed one thing immediately: it is still buggy, perhaps in the same way 180.11 was. The difference is that those bugs don't kill my system. They just scream.

Here's what I saw with 180.11 (after about 4 days of running it):

1. Apparently, It did fix scrolling in firefox. I have not seen the refresh bugs in 4 days.

2. In xterm, it wasn't fixed. If anything, it became more regular. I couldn't scroll in xterm without refreshing it externally.

3. It caused obvious memory violations that killed my machine several times. It could not wake from sleep without halting, and it didn't even let me reboot the machine without turning the power off. On one occasion, I saw my entire screen become corrupt, as if something was writing into screen memory randomly. For a while, I watched the show, but the machine became unresponsive and eventually shut itself down. Today I saw something similar, when it killed my compiz and didn't let me restart it; out of a bunch of applications still running, I could only use firefox, all others' windows were blank and non-responsive. Probably another memory fault.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Now, the good news about 180.44 is that I've been running it for an hour and we're still alive, with no artifacts, in praticular none of the refresh problems that launched this thread.

The bad news, it sounds like, is that it still spills its bytes over in the wrong places. I tested how it comes out of S3 and how it starts from cold- and warm-boot; in all three cases the system beeper screams in the manner of a tty receiving tons of garbage, as soon as the nvidia module gets loaded, but eventually it goes quiet, and here I am typing away through an X window, and everything seems normal.

Maybe it's the same bug as in 180.11, only this time non-lethal.

Quadro FX 360M (rev a1)

nvidia-180-kernel-source:
  Installed: 180.44-0ubuntu1
  Candidate: 180.44-0ubuntu1
  Version table:
 *** 180.44-0ubuntu1 0
        500 http://ppa.launchpad.net jaunty/main Packages
        100 /var/lib/dpkg/status
     180.11-0ubuntu1~intrepid1 0
        500 http://gb.archive.ubuntu.com intrepid-updates/restricted Packages