Kernel Oops - BUG: unable to handle kernel paging request at ffffffffa05acce0; RIP: 0010:[<ffffffffa05acb67>] [<ffffffffa05acb67>] RTHeapSimpleInit+0x67/0x100 [vboxdrv]

Moritz Naumann, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, as a potential WORKAROUND, does using virtualbox from either the repositories or PPA work for you? As well, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

Christopher: I am no longer running Ubuntu version 11.04, and have since upgraded to Ubuntu 12.04 where this issue does not occur (for me) using either the proprietary or open source vboxdrv kernel module.

Note that the test differs a lot from the original bug report, though, since I have not tested this in the original constellation where kernel drivers meant for Maverick were attempted to be built on Natty. I could not tell whether this bug would still apply in this scenario - and I do not plan to test this (more than a year after the initial bug report).

I may or may not find the time to test this on an Ubuntu development release. I am wondering whether investing this time really makes much sense, though, since both the kernel ABI and driver modules will have changed quite a bit since. Also, the test scenario would be a bit unclear to me, since the issue only occurred while combining a kernel module written for an earlier kernel version with a, then, current kernel.

So if you can provide more detailed instructions on how to or what to test, that'd be appreciated.

Moritz Naumann, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.