On Fri, Jan 15, 2016 at 6:29 PM, Matthias Klose <d...@ubuntu.com> wrote: > please attach the preprocessed source and the exact command line options > to build the libahci module.
Not only libahci modules, all built modules has the problem. Follows the command line for building libahci.ko: 1) apt-get source linux-image-`uname -r` 2) cd linux-XXXX #only one directory is generated 3) make -C /usr/src/linux-headers-`uname -r` M=`pwd` drivers/ata/libahci.ko then the libahci.ko will be generated. BTW, the issue can only be reproduced on Xenial. Thanks, > > -- > You received this bug notification because you are subscribed to linux > in Ubuntu. > https://bugs.launchpad.net/bugs/1533009 > > Title: > arm64: "unsupported RELA relocation" > > Status in gcc-5 package in Ubuntu: > New > Status in linux package in Ubuntu: > Triaged > > 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/ubuntu/+source/gcc-5/+bug/1533009/+subscriptions -- 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 gcc-5 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged 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/ubuntu/+source/gcc-5/+bug/1533009/+subscriptions -- 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