ubuntu-x-swat team mailing list archive

[fmyhr <fmyhr@xxxxxxxxxxx>]

I can confirm Øyvind Stegard's report above:
Since upgrading my Maverick AMD64 G210 system yesterday from
nvidia-current (260.19.29-0ubuntu1~xup~maverick3) to 270.18-0ubuntu1~maverick~xup1
my log file is full of the "NVRM: os_raise_smp_barrier(), invalid context!" messages.

I haven't noticed any other ill effects, and in particular my system
still suspends to and resumes from RAM without problems. But the log
full of error messages is irritating and somewhat worrisome. I
originally started using the Ubuntu-X packages to get rid of such errors
that the Maverick Nvidia package caused.

I wonder why the Ubuntu-X community decided to package this *beta*
270.18 release rather than the current stable 260.19.36? This decision
seems to violate the stated purpose of Ubuntu-X:

https://launchpad.net/~ubuntu-x-swat/+archive/x-update
"This PPA is for stable upstream releases of X.org components. If you're looking for something even more bleeding-edge, please see the xorg-edgers PPA."

IOW, it would seem that 270.18 should have gone to xorg-edgers, and
Ubuntu-X should have gone to 260.19.36 (or simply remained at the
previously-released 260.19.29). I guess there's a reason I'm unaware of
that Ubuntu-X went straight to the beta 270.18. But it would be nice if
they could somehow indicate that it is a *beta* release so that we end-
users would be more cautious than usual about upgrading. Could the
release be called something like "270.18-0beta-ubuntu1~maverick~xup1"?

It would also be nice if Ubuntu-X could keep 2 versions of released
drivers: the current one, and the previous one. That would help people
roll back in case of problems like the above.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
https://bugs.launchpad.net/bugs/656279

Title:
  NVRM: os_raise_smp_barrier(), invalid context!