Error! Bad return status for module build on kernel: 3.16.0-16-generic (x86_64)

Bug #1370859 reported by dino99
534
This bug affects 122 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Invalid
High
Unassigned
nvidia-graphics-drivers-331 (Ubuntu)
Invalid
High
Unassigned
Nominated for Utopic by Alberto Salvia Novella

Bug Description

Installing a new kernel 3.16.0.16 from a running gnome-shell session using the kernel 3.16.014, i'm getting:

****
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.0-16-generic /boot/vmlinuz-3.16.0-16-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-16-generic /boot/vmlinuz-3.16.0-16-generic
Error! Bad return status for module build on kernel: 3.16.0-16-generic (x86_64)
Consult /var/lib/dkms/nvidia-331/331.89/build/make.log for more information.
*****

As apport also fails to report that issue (it simply does nothing, it even does not start and does not warns either), i'm joining the crash file and make.log for details.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
Uname: Linux 3.16.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Sep 18 07:13:23 2014
SourcePackage: nvidia-graphics-drivers-331
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nvidia-graphics-drivers-331 (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

Get it again

Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.0-17-generic /boot/vmlinuz-3.16.0-17-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-17-generic /boot/vmlinuz-3.16.0-17-generic
Error! Bad return status for module build on kernel: 3.16.0-17-generic (x86_64)
Consult /var/lib/dkms/nvidia-331/331.89/build/make.log for more information.

Revision history for this message
dino99 (9d9) wrote :

Latest upgrade error met:

Setting up linux-image-extra-3.16.0-18-generic (3.16.0-18.25) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
initrd.img(/boot/initrd.img-3.16.0-18-generic
) points to /boot/initrd.img-3.16.0-18-generic
 (/boot/initrd.img-3.16.0-18-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-extra-3.16.0-18-generic.postinst line 491.
vmlinuz(/boot/vmlinuz-3.16.0-18-generic
) points to /boot/vmlinuz-3.16.0-18-generic
 (/boot/vmlinuz-3.16.0-18-generic) -- doing nothing at /var/lib/dpkg/info/linux-image-extra-3.16.0-18-generic.postinst line 491.

Revision history for this message
dino99 (9d9) wrote :

Still getting that error:

cd /var/lib/dkms/nvidia-331/331.89/build; make module SYSSRC=/lib/modules/3.16.0-22-generic/build SYSOUT=/lib/modules/3.16.0-22-generic/build KBUILD_EXTMOD=/var/lib/dkms/nvidia-331/331.89/build
make[1]: Entering directory '/var/lib/dkms/nvidia-331/331.89/build'
NVIDIA: calling KBUILD...
make[2]: Entering directory '/usr/src/linux-headers-3.16.0-22-generic'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ;

Could not this be fixed ? That issue is met by many users.

Devtalk: https://devtalk.nvidia.com/default/topic/769055/dkms-fails-to-compile-nvidia-modules-340-32-343-13-during-kernel-3-16-1-compile-process-on-debia/

Revision history for this message
dino99 (9d9) wrote :

Added 'Linux' due to the 'not up to date' .config which have old entry(ies) named paramaters probably conflicting with the new ones, so the module driver issue.

Revision history for this message
dino99 (9d9) wrote :

kernel config file

Revision history for this message
Cavsfan (cavsfan) wrote :

I just got this error when kernel 3.16.0-23-generic was installed.

Revision history for this message
rth. (rth.) wrote :

I did an Ubuntu upgrade from 14.04 to 14.10 but the old kernel 3.13 were still used.

During manual installation of kernel 3.16 this bug popped-up.

> sudo apt-get install linux-image-generic linux-headers-generic
    ....
    linux-image-3.16.0-23-generic linux-image-extra-3.16.0-23-generic
    linux-image-generic thermald
    ...

Changed in nvidia-graphics-drivers-331 (Ubuntu):
importance: Undecided → High
Revision history for this message
dino99 (9d9) wrote :

Latest drivers 331 & 340 from today xorg-edgers ppa have no issue installing kernels 3.16 / 3.18 on my vivid i386 installation.

no longer affects: linux
Revision history for this message
dino99 (9d9) wrote :

Feedback:

get that issue logged today, booted with kernel 3.18 & the new nvidia driver upgraded yesterday:

kernel: [ 35.160563] No drm_driver.set_busid() implementation provided by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly.

Looks like the configuration at build time is missing a setting.

Revision history for this message
dino99 (9d9) wrote :

Today 3.18.0-3-generic

NVIDIA: calling KBUILD...
make[1]: Entering directory '/usr/src/linux-headers-3.18.0-3-generic'
test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo >&2 ; \
/bin/false)
mkdir -p /var/lib/dkms/nvidia-340/340.58/build/.tmp_versions ; rm -f /var/lib/dkms/nvidia-340/340.58/build/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/var/lib/dkms/nvidia-340/340.58/build

but the kernel is installed and boot fine

Revision history for this message
Celio Alves (celio.alves) wrote :

I can install a new kernel only when I kill the process "nvidia-persistenced".

Revision history for this message
Njenga (smuriu) wrote :

Got this on linux kernel 3.16.0-25-generic (x86_64) as well

Revision history for this message
Njenga (smuriu) wrote :

Strangley, built fine on "dpkg-reconfigure nvidia-331" for both my kernels. Maybe something in the upgrade script?

Revision history for this message
Alberto Milone (albertomilone) wrote :

The driver in 15.04 (vivid) supports up to Linux 3.18.

Also, the "echo >&2 " ERROR: Kernel configuration is invalid."; \" is not an actual error.

Revision history for this message
Alberto Milone (albertomilone) wrote :

It seems to work fine in my clean chroot:

First Installation: checking all kernels...
It is likely that 3.13.0-39-generic belongs to a chroot's host
Building for architecture x86_64
Building initial module for 3.16.0-23-generic
Done.

nvidia_331:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/3.16.0-23-generic/updates/dkms/

depmod....

DKMS: install completed.

Changed in nvidia-graphics-drivers-331 (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
dino99 (9d9) wrote :

lp:1396091 prove by itself that problem still exist on Trusty with that 331 driver.

More recent 346 driver have no such issue; hopes the archives been upgraded and dropped that 331 nightmare as the default driver asap.

Changed in nvidia-graphics-drivers-331 (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Angel Aguilera (angel-aguilera) wrote :

Got the same issue on linux kernel 3.16.0-25-generic (x86_64) as well. After the error, i used the following command:

sudo apt-get install linux-image-3.16.0-25-generic --reinstall

This time the command succeeded without errors or warnings.

Revision history for this message
dino99 (9d9) wrote :

Kernel upgrade on utopic i386: got no error with nvidia-340 installed

but upgrading nvidia-340 to nvidia-346 pushed up that issue again and the upgrade fully failed. As a workaround i had to first purge:
sudo rm /var/lib/dpkg/info/nvidia-340*

then the installation was made smootly without complaint.

Changed in hundredpapercuts:
importance: Undecided → High
status: New → Confirmed
status: Confirmed → Triaged
Changed in nvidia-graphics-drivers-331 (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Allard Pruim (allardpruim) wrote :

I have the same problem on the 3.13 kernels. Everytime when I install a kernel update I get these errors. When I simply reboot my machine the kernel seem to be working fine as it should be.

The odd thing is that I'm using Kubuntu 14.04 now for some months and with Ubuntu I didn't had this messages.

Revision history for this message
axel (axel334) wrote :

I have similar problem. I use old kernel because it doesn't update with normal Moun updates automatically. Kernel updates just don't show up for update. They don't show up also in Terminal with pt-get upgrade command. While updating in terminal with command
Code:

sudo apt-get install linux-headers-3.13.0-49 linux-headers-3.13.0-49-generic

I get errors. Please, have a look at this error log

http://pastebin.com/mqG66NPG
(The same in attached file)

I looked at some bugs from above ling but I'm not sure what is wrong in mu case. I can't point any specific output that indicates what exactly is wrong.

With 3.13.0-52 I have the same problem.

Can someone tell me what current kernel for Kubuntu 14.04 is free of this problem?

Revision history for this message
Jarl (jarl-dk) wrote :

Got this problem on 3.16.0-41-generic (x86_64)

Revision history for this message
Jarl (jarl-dk) wrote :

It says "Consult /var/lib/dkms/nvidia-331-updates/331.113/build/make.log for more information." but the file is gone after the "aptitude upgrade" completed.

Revision history for this message
dino99 (9d9) wrote :

Well, utopic has reached EOL, and nvidia-331 is deprecated and replaced by 340; which has not such issue. Closing that issue.

Changed in hundredpapercuts:
status: Triaged → Invalid
Changed in nvidia-graphics-drivers-331 (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.