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

[Daryl Hughes]

This Bug was caused by me Testing Kernel 3.13
3.13 didn't boot up properly just showed Black screen with X as the Mouse arrow and the Kernel was not in a Virtual Box is was in the Main computer system there are 3 Bugs I collected on this will have them below all 3 is the same not sure if it was of the same thing of kernel 3.13 But could of effected something if it brought 3 Report problems

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: virtualbox-dkms 4.2.16-dfsg-3ubuntu1
ProcVersionSignature: Ubuntu 3.12.0-4.10-generic 3.12.1
Uname: Linux 3.12.0-4-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.7-0ubuntu1
Architecture: amd64
DKMSKernelVersion: 3.13.0-031300rc1-generic
Date: Tue Nov 26 22:41:48 2013
DuplicateSignature: dkms:virtualbox-dkms:4.2.16-dfsg-3ubuntu1:/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-11-12 (14 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131111)
PackageArchitecture: all
PackageVersion: 4.2.16-dfsg-3ubuntu1
SourcePackage: virtualbox
Title: virtualbox-dkms 4.2.16-dfsg-3ubuntu1: virtualbox kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

[Daryl Hughes (zorw2016)]

https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1255392

[Daryl Hughes (zorw2016)]

https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1255393

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1255393, so 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. Please continue to report any other bugs you may find.