virtualbox-dkms 4.2.16-dfsg-3: virtualbox kernel module failed to build

Bug #1269274 reported by vaal on 2014-01-15
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
Undecided
Unassigned

Bug Description

failed build module for kernel 3.13.0-3.18(Ubuntu branch)

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: virtualbox-dkms 4.2.16-dfsg-3
ProcVersionSignature: Ubuntu 3.13.0-2.17-generic 3.13.0-rc7
Uname: Linux 3.13.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
DKMSKernelVersion: 3.13.0-3-generic
Date: Wed Jan 15 11:07:23 2014
DuplicateSignature: dkms:virtualbox-dkms:4.2.16-dfsg-3:/var/lib/dkms/virtualbox/4.2.16/build/vboxdrv/r0drv/linux/memobj-r0drv-linux.c:1539:26: error: ‘struct mm_struct’ has no member named ‘numa_next_reset’
InstallationDate: Installed on 2013-01-22 (357 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 4.2.16-dfsg-3
SourcePackage: virtualbox
Title: virtualbox-dkms 4.2.16-dfsg-3: virtualbox kernel module failed to build
UpgradeStatus: Upgraded to saucy on 2013-10-03 (103 days ago)
VirtualBox.ModInfo:

vaal (vaal) wrote :
Launchpad Janitor (janitor) wrote :

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

Changed in virtualbox (Ubuntu):
status: New → Confirmed
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1254803, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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

Other bug subscribers