kernel-packages team mailing list archive

[Brad Figg <brad.figg@xxxxxxxxxxxxx>]

** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
       Status: New

** Also affects: gcc-5 (Ubuntu Vivid)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
       Status: New

** Also affects: gcc-5 (Ubuntu Wily)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Wily)
       Status: New => Fix Committed

** Changed in: linux (Ubuntu Vivid)
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1533009

Title:
  arm64: "unsupported RELA relocation"

Status in Linaro GCC:
  Unknown
Status in Linux:
  Unknown
Status in gcc-5 package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in gcc-5 source package in Trusty:
  New
Status in linux source package in Trusty:
  Fix Committed
Status in gcc-5 source package in Vivid:
  New
Status in linux source package in Vivid:
  Fix Committed
Status in gcc-5 source package in Wily:
  New
Status in linux source package in Wily:
  Fix Committed
Status in gcc-5 source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released

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
  reproduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-linaro/+bug/1533009/+subscriptions