gpu-manager searches for a wrong string when checking if nvidia was unloaded

Bug #1337357 reported by Rafał Cieślak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-drivers-common (Ubuntu)
Fix Released
Medium
Alberto Milone

Bug Description

I am using Ubuntu 14.04 with an Intel 4000HD and Nvidia GTX 770.
I have noticed that my gpu-manager claims that:
    Was nvidia unloaded? yes
even though the nvidia module is loaded and was never unloaded (and lsmod displays it).
Quick investigation showed that gpu-manager checks whether that module was unloaded by running:
    dmesg | grep -q "nvidia: module"
I assume that the intention was to detect any "nvidia: module unloaded" or similar messages.
However, my dmesg contains several other messages that match this pattern:
    nvidia: module license 'NVIDIA' taints kernel.
    nvidia: module verification failed: signature and/or required key missing - tainting kernel
These messages are not realated to unloading the module, it sucessfully keeps running afterwards.
Therefore I believe the pattern used by gpu-manager is incorrect.

Possible solution is to correct that search string. The only message that appears in my dmesg when I unload nvidia module is:
    [drm] Module unloaded
The dmesg output never explicitly names `nvidia` when it is unloaded.
Another possible solution would be to grep lsmod instead of dmesg, to check if the driver is currently loaded.

Changed in ubuntu-drivers-common (Ubuntu):
status: New → Fix Committed
importance: Undecided → Medium
assignee: nobody → Alberto Milone (albertomilone)
Revision history for this message
Alberto Milone (albertomilone) wrote :

I have addressed this issue in the 1:0.2.98 release

Changed in ubuntu-drivers-common (Ubuntu):
status: Fix Committed → Fix Released
Changed in ubuntu-drivers-common (Ubuntu Trusty):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Alberto Milone (albertomilone)
Revision history for this message
Alberto Milone (albertomilone) wrote :

I'll be tracking this as part of LP: #1310489

no longer affects: ubuntu-drivers-common (Ubuntu Trusty)
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.