[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#890999: marked as done (VirtualBox modules built against headers version 4.14.17-1 cannot be loaded by kernel version 4.14.13-1: Unknown symbol __x86_indirect_thunk_r15 (err 0))

Your message dated Wed, 21 Feb 2018 14:30:56 +0100
with message-id <1519219856.2388.7.camel@debian.org>
and subject line Re: Bug#890999: VirtualBox modules built against headers version 4.14.17-1 cannot be loaded by kernel version 4.14.13-1: Unknown symbol __x86_indirect_thunk_r15 (err 0)
has caused the Debian Bug report #890999,
regarding VirtualBox modules built against headers version 4.14.17-1 cannot be loaded by kernel version 4.14.13-1: Unknown symbol __x86_indirect_thunk_r15 (err 0)
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 owner@bugs.debian.org
immediately.)


-- 
890999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890999
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-headers-4.14.0-3-amd64
Version: 4.14.17-1

When I build VirtualBox kernel modules using linux-headers-4.14.0-3-amd64 version 4.14.17-1, the resulting modules can't be loaded using linux-image-4.14.0-3-amd64 version 4.14.13-1. When I build the same modules using headers version 4.14.13-1, they load successfully.

Here are some error messages:

systemd[1]: Starting LSB: VirtualBox Linux kernel module...
kernel: vboxdrv: Unknown symbol __x86_indirect_thunk_r15 (err 0)
kernel: vboxdrv: Unknown symbol __x86_indirect_thunk_rax (err 0)
kernel: vboxdrv: Unknown symbol __x86_indirect_thunk_rdx (err 0)
kernel: vboxdrv: Unknown symbol __x86_indirect_thunk_r14 (err 0)
kernel: vboxdrv: Unknown symbol __x86_indirect_thunk_rbx (err 0)
kernel: vboxdrv: Unknown symbol __x86_indirect_thunk_r13 (err 0)
kernel: vboxdrv: Unknown symbol __x86_indirect_thunk_r10 (err 0)
kernel: vboxdrv: Unknown symbol __x86_indirect_thunk_rcx (err 0)
kernel: vboxdrv: Unknown symbol __x86_indirect_thunk_rsi (err 0)
kernel: vboxdrv: Unknown symbol __x86_indirect_thunk_r9 (err 0)
kernel: vboxdrv: Unknown symbol __x86_indirect_thunk_r12 (err 0)
kernel: vboxdrv: Unknown symbol __x86_indirect_thunk_r8 (err 0)
virtualbox[6834]: Loading VirtualBox kernel modules...modprobe vboxdrv failed. Please use 'dmesg' to find out why ... failed!
virtualbox[6834]:  failed!

--- End Message ---
--- Begin Message --- 
On Wed, 2018-02-21 at 15:43 +0300, Evgeny Kapun wrote:
> When I build VirtualBox kernel modules using linux-headers-4.14.0-3-amd64
> version 4.14.17-1, the resulting modules can't be loaded using linux-image-
> 4.14.0-3-amd64 version 4.14.13-1. When I build the same modules using
> headers version 4.14.13-1, they load successfully.

Hi Evgeny,

this is expected, there is no warranty of ABI compatibility downward, only
upward.

That means it should be possible to load modules built against an older kernel
in a new kernel (providing the ABI number, 3 here, is the same), but not the
other way around (loading modules built against a newer kernel on an older
one).

This is done so you don't have to rebuild all out-of-tree modules every time
you upgrade your kernels, but downgrade is not a common operation, so you just
have to rebuild the modules if you do that.

I'm closing this bug since it's the expected behavior.

Regards,
-- 
Yves-Alexis

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: