nvidia-375 375.66-0ubuntu0.16.04.1: nvidia-375 kernel module failed to build

Bug #1699110 reported by Samarth on 2017-06-20
52
This bug affects 10 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-375 (Ubuntu)
Undecided
Unassigned

Bug Description

The error came after I restarted the system. I know nothing about it, and don't have the time to search where it came from.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-375 375.66-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
DKMSKernelVersion: 4.8.0-56-generic
Date: Tue Jun 20 16:45:31 2017
InstallationDate: Installed on 2017-05-25 (25 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
PackageVersion: 375.66-0ubuntu0.16.04.1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.20
SourcePackage: nvidia-graphics-drivers-375
Title: nvidia-375 375.66-0ubuntu0.16.04.1: nvidia-375 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Samarth (skskrobot) wrote :
Daniel van Vugt (vanvugt) wrote :

The important log file (DKMSBuildLog.txt) appears to be incomplete and isn't showing what went wrong (unless what went wrong was the whole system freezing).

Can you find a more complete DKMS build log file? (check /var/lib/dkms/)

Changed in nvidia-graphics-drivers-375 (Ubuntu):
status: New → Incomplete
Sebastian Unger (sebunger44) wrote :

I just logged into my system, the update-manager popped up and said there where a number of updates. When I told it to install them it went ahead, but in the middle of the update it reported that Ubuntu had experienced a problem (the update went on though) and when I reported it it offered me a largish number of issues that might be duplicates. I chose this one because it had the exact same subject line as the bug report generated for me.

I searched under /var/lib/dkms/ and there where no files named DKMSBuildLog.txt there. However, the was /var/lib/dkms/nvidia-375/375.66/4.4.0-83-generic/x86_64/log/make.log with a timestamp matching approximately when the error occurred. However, it didn't appear to have any errors in it.

/var/log/apt/term.log was slightly more interesting. It had the following in it:

Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
Error! Bad return status for module build on kernel: 4.4.0-83-generic (x86_64)
Consult /var/lib/dkms/nvidia-375/375.66/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-83-generic
W: plymouth module (/usr/lib/x86_64-linux-gnu/plymouth//.so) missing, skipping that theme.
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic

I'll attach it as well. The log file mentioned (/var/lib/dkms/nvidia-375/375.66/build/make.log) however, does not exist.

Changed in nvidia-graphics-drivers-375 (Ubuntu):
status: Incomplete → New
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-graphics-drivers-375 (Ubuntu):
status: New → Confirmed
Dario Pintaric (dario-pintaric) wrote :

Same here... i got the error after rebooting due to updates... As soon as desktio showed (after login screen) i got the message...

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers