On 12/08/13 18:40, Felix Geyer wrote: > On 12.08.2013 17:55, Daniel Pocock wrote: >> This bug was supposedly serious and marked RC and then marked done >> >> The fixed version was apparently uploaded but is not available in stable > The bug affected experimental and later unstable and is fixed in both. > wheezy was never affected by this because the wheezy kernel is based on > v3.2.
The comments suggest that it also impacts guests, although it doesn't appear that patching the host's kernel module has any impact on the guest in this case. > >> Can somebody please comment on this? How can somebody running wheezy >> use this fix? Or should the bug be re-opened? > Apparently you already reopened the bug for whatever reason. > It shouldn't be surprising that external kernel modules don't work with > the latest kernel version since the API is constantly changing. > > The latest version of virtualbox is in wheezy-backports which is compatible > with the kernel from wheezy-backports. An unrelated kernel issue on Thinkpads prevents me running the wheezy kernel (I put up with it crashing every day for 2 weeks and then had to take a kernel from sid). It was relatively easy for me to copy the patch into /usr/src on my wheezy box and the dkms builds the module successfully - I suspect I will not be the only person to come across this type of scenario during the life of wheezy -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
