/var/lib/dkms/nvidia-384/384.90/build/nvidia-uvm/uvm8_va_block.c: In function ‘block_cpu_fault_locked’ [error: implicit declaration of function ‘task_stack_page’; did you mean ‘task_stack_vm_area’?]
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvidia-graphics-drivers-384 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
After today installing 4.13.0-25.29 Kernel today to fix the before faulty 24.25 kernel The Nvidia dkms driver still fails to build, this time with a different error.
STDOUT:
run-parts: executing /etc/kernel/
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/
Error! Bad return status for module build on kernel: 4.13.0-25-generic (x86_64)
Consult /var/lib/
Setting up linux-image-
run-parts: executing /etc/kernel/
run-parts: executing /etc/kernel/
ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/
Error! Bad return status for module build on kernel: 4.13.0-25-generic (x86_64)
Consult /var/lib/
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nvidia-384 384.90-
ProcVersionSign
Uname: Linux 4.13.0-22-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jan 9 15:28:17 2018
SourcePackage: nvidia-
UpgradeStatus: No upgrade log present (probably fresh install)
summary: |
/var/lib/dkms/nvidia-384/384.90/build/nvidia-uvm/uvm8_va_block.c: In - function ‘block_cpu_fault_locked’ + function ‘block_cpu_fault_locked’ [error: implicit declaration of + function ‘task_stack_page’; did you mean ‘task_stack_vm_area’] |
summary: |
/var/lib/dkms/nvidia-384/384.90/build/nvidia-uvm/uvm8_va_block.c: In function ‘block_cpu_fault_locked’ [error: implicit declaration of - function ‘task_stack_page’; did you mean ‘task_stack_vm_area’] + function ‘task_stack_page’; did you mean ‘task_stack_vm_area’?] |
Here is the make log of this install. Sadly it not overwrote the craash report due to a file already existent, so I can not provide that.