On 5 January 2014 23:14, Peter Robinson <pbrobinson@xxxxxxxxx> wrote: > On Thu, Jan 2, 2014 at 11:07 AM, Sandeepa Prabhu > <sandeepa.prabhu@xxxxxxxxxx> wrote: >> Hi, >> >> I am trying to build kernel on fc19 aarch64 image based on v8 Foundation model. >> kernel branch is based on "armv8-uefi-v3.13rc" and toolchain: gcc >> version 4.8.1 20130920 (Red Hat 4.8.1-10) (GCC) - using 8GB RAM. >> >> Kernel build is taking for me more than 12 hours, and adding more >> threads (-j6 etc) does not improve the build speed. Is this expected ? >> or is there a step to improve kernel build? > > Have you tried the kernel from arm.koji for aarch64 foundation board? > The 3.13 should boot. Hi Peter, I am using aarch64 upstream branch (git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux-aarch64.git Br:upstream) for kprobes developement, and then I merged EFI changes from "https://github.com/mosalter/linux.git Br:armv8-uefi-v3.13rc". Further cross-compiled using using linaro toolchain: "gcc-linaro-aarch64-linux-gnu-4.8-2013.10_linux". Kernel boots fine initially but I am observing a systemd crash logs below[1] > > Alternatively you can cross compile on standard x86 with the command > "rpmbuild --rebuild --target aarch64 --with=cross --without=perf > --without=tools --without=debuginfo --define="_arch aarch64" > --define="_build_arch aarch64" --define="__strip > /usr/bin/arm-linux-gnu-strip" kernel.src.rpm" I am using Ubuntu host, so not sure if I can cross-compile using rpmbuild. Also the kernel srpms from koji does not have git so it makes us hard to develop and track or to migrate. Let me know if you have any pointers, whether I am using wrong combination of kernel, toolchain. ~Sandeepa [1] systemd crash log: [ OK ] Found device /dev/disk/by-uuid/684f9136-d0a1-46bc-9449-52520a842899. Activating swap /dev/disk/by-uuid/684f9136-d0a1-46bc...52520a842899... [ OK ] Started udev Coldplug all Devices. [ OK ] Started Tell Plymouth To Write Out Runtime Data. [ OK ] Started Trigger Flushing of Journal to Persistent Storage. [FAILED] Failed to activate swap /dev/disk/by-uuid/684f9136-d...9-52520a842899. See 'systemctl status dev-disk-by\x2duuid-684f9136\x2dd0a1\...wap' for details. [systemd[1]: unhandled level 1 translation fault (11) at 0x00000000, esr 0x92000005 pgd = ffffffc079e21000 [00000000] *pgd=0000000000000000 CPU: 0 PID: 1 Comm: systemd Not tainted 3.13.0-rc2+ #17 task: ffffffc079c60000 ti: ffffffc079c3c000 task.ti: ffffffc079c3c000 PC is at 0x7fae90cc30 LR is at 0x556de9fbf0 pc : [<0000007fae90cc30>] lr : [<000000556de9fbf0>] pstate: 20000000 sp : 0000007fe9127920 x29: 0000007fe9127920 x28: 000000556df01000 x27: 000000556df03100 x26: 0000000000000001 x25: 000000556defe940 x24: 000000556df0a000 x23: 000000556df02958 x22: 0000000000000011 x21: 0000000001c31ca6 x20: 000000557a91a8c0 x19: 000000557a91a8c0 x18: 0000000000000800 x17: 0000007fae90cc28 x16: 000000556df8c620 x15: 003b9aca00000000 x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000018 x11: 000000002e34030e x10: 0000000000000013 x9 : 0000000000000f72 x8 : 0000000000000f72 x7 : 0000000000000000 x6 : 0000007faec4d000 x5 : 636f732f6c616e72 x4 : 0000007fe9127a90 x3 : 00000000000bd3f8 x2 : 0000000000000013 x1 : 0000000000000001 x0 : 0000000000000000 OK ] Reached target Swap. systemd-journald[791]: Can't write entry: Invalid argument systemd-journald[791]: Failed to write entry, ignoring: Invalid argument systemd-journald[791]: Failed to write entry, ignoring: Invalid argument systemd-journald[791]: Failed to write entry, ignoring: Invalid argument > > Peter _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
