Your message dated Tue, 14 Dec 2010 04:47:27 +0000
with message-id <1292302047.3136.523.ca...@localhost>
and subject line Re: virtualbox-ose-dkms: modules not built properly on kernel
upgrade to 2.6.32-5
has caused the Debian Bug report #600939,
regarding virtualbox-ose-dkms: modules not built properly on kernel upgrade to
2.6.32-5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
600939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox-ose-dkms
Version: 3.2.8-dfsg-2
Severity: important
I think (based on the virtualbox forums) that this bug belongs to the debian
packager
of the linux source, but I'm not sure where to report it, so I'm hoping you can
forward
it if appropriate.
I upgraded my kernel today:
linux-headers-2.6.32-5-686 2.6.32-23 -> 2.6.32-25
And rebooted and the dkms stuff failed to rebuild, citing:
vboxdrv: Trying to deactivate the NMI watchdog permanently...
vboxdrv: Successfully done.
vboxdrv: Found 2 processor cores.
supdrvGipCreate: failed to allocate the GIP page. rc=-8
I ran m-a a-i virtualbox-ose-source and that also failed, with only the same
error as
above.
This appears to be the same issue, though with a different kernel version:
http://www.virtualbox.org/ticket/7535
The VB guy says it is the Debian kernel packager's fault, that the -5 should
really
have been changed to a -6.
http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg830845.html
Similar to this, although I don't get the same error as this guy did:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596945
deleting and purging the virtualbox-ose-modules package did not help.
Then I uninstalled everything virtualbox-* except for virtualbox-ose, and
everything
rebuilt properly.
I suspect that simply reinstalling the virtualbox-ose-dkms would have fixed the
problem.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (700, 'testing'), (600, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968)
(ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Versions of packages virtualbox-ose-dkms depends on:
ii dkms 2.1.1.2-5 Dynamic Kernel Module Support Fram
virtualbox-ose-dkms recommends no packages.
virtualbox-ose-dkms suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
I previously stated:
> No-one has explained exactly what change affects VirtualBox, so there is
> no way we can revert it. And we are not going to make an ABI bump.
This is still the case, so we have no way to fix this bug. You will
have to rebuild the VirtualBox modules.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
