On Sat, Jan 16, 2016 at 2:44 AM, Matthias Klose <d...@ubuntu.com> wrote:
> --- fsf/multipath.mod.s 2016-01-15 22:23:24.000000000 +0100
> +++ linaro/multipath.mod.s      2016-01-15 22:20:11.000000000 +0100
> @@ -1,7 +1,6 @@
> -       .cpu generic+fp+simd
>         .file   "multipath.mod.c"
>         .global __this_module
> -       .section        .modinfo,"a",%progbits
> +       .section        .modinfo,"a",@progbits
>         .align  3
>         .type   __UNIQUE_ID_srcversion1, %object
>         .size   __UNIQUE_ID_srcversion1, 35

I got rid of the @progbits/%progbits differences in the assembly, as
well as the .cpu and .arch differences,
but still observe the same failure.


You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  arm64: "unsupported RELA relocation"

Status in Linaro GCC:
Status in Linux:
Status in gcc-5 package in Ubuntu:
Status in linux package in Ubuntu:

Bug description:
  linux-image-4.3.0-5-generic 4.3.0-5.16 arm64 fails to load modules
  (and therefore boot). It emits messages like the following for each
  attempted module load:

  [    2.156817] module libahci: unsupported RELA relocation: 275

  This is reminiscent of LP: #1502946 - except that fix appears to still
  be in-tact. What has changed, however, is the build environment. If I
  rebuild the same kernel source in a wily chroot, it boots fine.

  Marking "Confirmed" because Paulo Pisatti reported this to me, and I

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to