desktop-packages team mailing list archive

[Stefan Bader <stefan.bader@xxxxxxxxxxxxx>]

Alberto is rolling this back into older releases over time. To be fair
it is an annoying issue but not one that is so fatal one would not be
able to recover a system. In the majority of cases this ends up being
just a false system issue notification. Because on kernel update the
parallel builds are actually started 3 times. By now I just made it a
habit of doing the following whenever kernel updates come in:

- run "dkms status" to see whether both nvidia modules appear for the latest kernel (bbswitch is always there)
- if one(or both) is missing, do "sudo dkms install -m <module> -v <module version> -k <kernel version>
   (the name and versions taken from the dkms status report)
- "sudo rm /var/crash/*nvidia*" to ignore the build failures before

When the fixed version of the driver hits this can be noticed by having
only one module reported by dkms for nvidia. The *-uvm one will be gone
and the module it produced will be part of the remaining dkms module
which then produces two kernel modules.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1431753

Title:
  Nvidia binary driver FTBS due to DKMS layer violation

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-346-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-331 source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-331-updates source package in Trusty:
  Triaged
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-340-updates source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346 source package in Trusty:
  Confirmed
Status in nvidia-graphics-drivers-346-updates source package in Trusty:
  Confirmed

Bug description:
  Filing this against the 340-updates version but possibly the same
  applies to older versions, too. The nvidia source package produces two
  individual dkms packages: nvidia-340-updates, nvidia-340-updates-uvm.
  The problem is that the DKMS build of the nvidia-uvm module runs
  compile steps inside the nvidia modules build directory. This is
  violating the DKMS assumption that each module can be build
  independently (there is no way of describing cross-modules
  dependencies and even more important, the autoinstall step after a new
  kernel is installed will run the modules build in parallel).

  Since nvidia and nvidia-uvm are very dependent on each other the right
  course of action seems to be to combine both sources in one DKMS
  module that produces two kernel modules (this is supported by DKMS).
  For the transition this resulting dkms package needs to have a
  breaks/replaces for the nvidia-uvm package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions