Issues for the linux-aarch64 package

This forum is for topics dealing with problems with software specifically in the AArch64 repo.

Issues for the linux-aarch64 package

Postby yuyichao » Fri Sep 23, 2016 11:29 pm

Sorry if this is the wrong place for bug report but I asked on IRC without a reply and the github issue tracker pointed to by viewtopic.php?f=65&t=2675 is closed.

I'm having a few issues with the linux-aarch64 packages.
1. The package version is wrong. uname reports 4.7.0-* even though it's actually 4.7.4
2. The package doesn't seem to compile directly. The config file already specified compression of the kernel modules which cause the compression command in the PKGBUILD to error.
3. linux.preset and linux-aarch64 still refers to 4.3.0 which needs updating.
4. 32bit ELF seems to be not supported.
5. I'm getting a strange error in LLVM JIT with the stock kernel but the problem is gone when I compiled the kernel with a config file modified from the opensuse kernel config (the config file I use is available at https://gist.github.com/yuyichao/1a30ce ... ab28f158a0, it compiles to a much bigger kernel so I don't think it's PR ready yet before I can narrow down the minimum necessary options). The problem is that LLVM emits `movz xzr, #0` instead of `movz x13, #0` for a relocation, in case if anyone know how that can happen.

The first issue is minor (just a little confusing)
The second and the third issues are only about compiling the package myself.
The forth and the fifth issues are about the binary package in the repo.
yuyichao
 
Posts: 7
Joined: Fri Sep 23, 2016 11:17 pm

Re: Issues for the linux-aarch64 package

Postby yuyichao » Fri Sep 23, 2016 11:32 pm

Oh, forgot to mention that the hardware is an overdrive-3000. Even with the current kernel I'm still having a small issue with running 32bit applications

Ref https://community.arm.com/message/38647#38647
yuyichao
 
Posts: 7
Joined: Fri Sep 23, 2016 11:17 pm

Re: Issues for the linux-aarch64 package

Postby yuyichao » Fri Dec 09, 2016 5:12 am

As a brief update, the LLVM issue turns out to be a LLVM relocation bug. Should/Will be fixed by https://reviews.llvm.org/D27609 .
yuyichao
 
Posts: 7
Joined: Fri Sep 23, 2016 11:17 pm


Return to ARMv8

Who is online

Users browsing this forum: No registered users and 8 guests