Comment 3 for bug 758892

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.