ubuntu-x-swat team mailing list archive
-
ubuntu-x-swat team
-
Mailing list archive
-
Message #107048
Re: [Bug 656279] Re: NVRM: os_raise_smp_barrier(), invalid context!
same behavior on my machine with ubuntu 10.10
I notice to u that if i disable logical cpu and then re-enable e
suppress os_raise_smp_barrier spamming message
2011/1/25 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 direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/656279
>
> Title:
> NVRM: os_raise_smp_barrier(), invalid context!
>
> Status in “nvidia-graphics-drivers” package in Ubuntu:
> Triaged
>
> Bug description:
> dmesg output is full of these messages:
> NVRM: os_raise_smp_barrier(), invalid context!
>
> Other than the errors being spammed and dmesg being unusable, I do not
> notice any immediate problems with the nVidia driver.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.10
> Package: nvidia-current 260.19.06-0ubuntu1
> ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
> Uname: Linux 2.6.35-22-generic x86_64
> NonfreeKernelModules: nvidia
> .proc.driver.nvidia.version:
> NVRM version: NVIDIA UNIX x86_64 Kernel Module 260.19.06 Mon Sep 13
> 04:29:19 PDT 2010
> GCC version: gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5)
> Architecture: amd64
> Date: Thu Oct 7 14:39:24 2010
> DkmsStatus:
> nvidia-current, 260.19.06, 2.6.32-25-generic, x86_64: built
> nvidia-current, 260.19.06, 2.6.35-22-generic, x86_64: installed
> GdmLog:
> Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log'] failed
> with exit code 1: QInotifyFileSystemWatcherEngine::addPaths:
> inotify_add_watch failed: No such file or directory
> QFileSystemWatcher: failed to add paths: /home/alvin/.config/ibus/bus
> Bus::open: Can not get ibus-daemon's address.
> IBusInputContext::createInputContext: no connection to ibus-daemon
> cat: /var/log/gdm/:0.log: No such file or directory
> GdmLog1: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.1']
> failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or
> directory
> GdmLog2: Error: command ['kdesudo', '--', 'cat', '/var/log/gdm/:0.log.2']
> failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or
> directory
> ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-22-generic
> root=/dev/mapper/vg0-root ro splash
> ProcEnviron:
> LANGUAGE=
> LANG=C
> SHELL=/bin/bash
> SourcePackage: nvidia-graphics-drivers
> dmi.bios.date: 09/07/2010
> dmi.bios.vendor: Intel Corp.
> dmi.bios.version: TMIBX10H.86A.0039.2010.0907.1056
> dmi.board.asset.tag: To be filled by O.E.M.
> dmi.board.name: DQ57TM
> dmi.board.vendor: Intel Corporation
> dmi.board.version: AAE70931-401
> dmi.chassis.type: 3
> dmi.modalias:
> dmi:bvnIntelCorp.:bvrTMIBX10H.86A.0039.2010.0907.1056:bd09/07/2010:svntranstecAG:pn:pvr:rvnIntelCorporation:rnDQ57TM:rvrAAE70931-401:cvn:ct3:cvr:
> dmi.sys.vendor: transtec AG
> glxinfo: Error: [Errno 2] No such file or directory
> system:
> distro: Ubuntu
> codename: maverick
> architecture: x86_64
> kernel: 2.6.35-22-generic
>
> To unsubscribe from this bug, go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/656279/+subscribe
>
--
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!
Follow ups
References