From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: add a private asm/unaligned.h
Date: Mon, 30 Oct 2017 17:24:34 +0100 [thread overview]
Message-ID: <8737601u4d.fsf@free-electrons.com> (raw)
In-Reply-To: <20171030161207.GS20805@n2100.armlinux.org.uk> (Russell King's message of "Mon, 30 Oct 2017 16:12:08 +0000")
Hi Russell King,
On lun., oct. 30 2017, Russell King - ARM Linux <linux@armlinux.org.uk> wrote:
> On Mon, Oct 30, 2017 at 05:01:44PM +0100, Gregory CLEMENT wrote:
>> Hi Russell King,
>>
>> On lun., oct. 30 2017, Russell King - ARM Linux <linux@armlinux.org.uk> wrote:
>>
>> > On Mon, Oct 30, 2017 at 02:48:02PM +0100, Gregory CLEMENT wrote:
>> >> Hi Russell,
>> >>
>> >> So I tested the branch fixes in your git tree.
>> >>
>> >> After doing a "make multi_v7_defconfig; make zImage", I got the message
>> >> "arm-linux-gnueabi-ld: error: zImage file size is incorrect" you added
>> >> in the commit "ARM: verify size of zImage".
>> >>
>> >> It is the same with mvebu_v7_defconfig, so I wonder wich with
>> >> configuration this patch was tested ?
>> >
>> > I heard a similar report from Olof when his autobuilder produced 100%
>> > failure. I tried one of the same defconfig's that Olof tried here,
>> > and didn't see the failure. It passes my build tests here, and it
>> > also passes kernelci's build tests too.
>> >
>> > So, I _think_ it's got something to do with the toolchain versions
>> > being used, but at the moment I'm just guessing. I've no real idea,
>> > because I've no idea what's causing the failure at the moment.
>> >
>> > Olof said that he'd send me one of the build trees, but I'm still
>> > waiting.
>> >
>> > What I need is a tarball of the objects from arch/arm/boot/compressed
>> > to work out what's going on - when grabbing that, it may be a good
>>
>> I've just attached this tarball to this email. It might be rejected by
>> the mailing list, but as you are also in the "To" field you should
>> receive it.
>>
>> Actually the archive is the full content of arch/arm/boot/compressed
>> from my build directory and I removed vmlinux and all the piggy files to
>> have a small archive.
>>
>> If they are also needed then I can provide an url for it.
>
> Thanks.
>
> Unfortunately, I can't reproduce the issue using your objects and my
> linker.
>
> If I modify your vmlinux.lds to add the assert in, and then link using:
>
> $ arm-linux-ld -o vmlinux -T vmlinux.lds *.o --defsym _kernel_bss_size=0 \
> --defsym input_data_end=0 --defsym input_data=0
>
> Then it links successfully. If I objcopy that:
>
> $ arm-linux-objcopy -O binary -R .comment -S vmlinux zImage
> $ vdir zImage
> -rwxrwxr-x 1 rmk rmk 27784 Oct 30 16:10 zImage
> $ arm-linux-nm vmlinux |grep _edata
> 00006c88 D _edata
> $ echo $((0x6c88))
> 27784
>
> So it all looks sane here. So my hunch is that whatever's going wrong,
> it's going wrong at the final link, which means I need the vmlinux as
> generated by your toolchain.
Here you will find all the objects included the vmlinux:
http://free-electrons.com/~gregory/pub/compressed.tgz
Gregory
>
> --
> RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
> FTTC broadband for 0.8mile line in suburbia: sync at 8.8Mbps down 630kbps up
> According to speedtest.net: 8.21Mbps down 510kbps up
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2017-10-30 16:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 20:01 [PATCH] ARM: add a private asm/unaligned.h Arnd Bergmann
2017-10-20 20:22 ` Ard Biesheuvel
2017-10-23 15:04 ` Romain Izard
2017-10-27 15:19 ` Gregory CLEMENT
2017-10-27 15:27 ` Russell King - ARM Linux
2017-10-30 13:48 ` Gregory CLEMENT
2017-10-30 14:55 ` Ard Biesheuvel
2017-10-30 15:05 ` Gregory CLEMENT
2017-10-30 15:07 ` Ard Biesheuvel
2017-10-30 15:09 ` Gregory CLEMENT
2017-10-30 15:20 ` Ard Biesheuvel
2017-10-30 15:33 ` Gregory CLEMENT
2017-10-30 15:35 ` Ard Biesheuvel
2017-10-30 15:40 ` Gregory CLEMENT
2017-10-30 16:59 ` Russell King - ARM Linux
2017-10-30 15:55 ` Russell King - ARM Linux
2017-10-30 16:04 ` Gregory CLEMENT
2017-10-30 15:48 ` Russell King - ARM Linux
[not found] ` <87bmko1v6f.fsf@free-electrons.com>
2017-10-30 16:12 ` Russell King - ARM Linux
2017-10-30 16:24 ` Gregory CLEMENT [this message]
2017-10-30 16:38 ` Russell King - ARM Linux
2017-10-31 12:47 ` Russell King - ARM Linux
2017-10-31 12:57 ` Ard Biesheuvel
2017-10-31 13:22 ` Gregory CLEMENT
2017-11-01 15:57 ` Ard Biesheuvel
2017-11-01 18:00 ` Russell King - ARM Linux
2017-11-01 18:02 ` Ard Biesheuvel
2017-11-01 18:11 ` Russell King - ARM Linux
2017-11-01 18:20 ` Ard Biesheuvel
2017-11-01 19:10 ` Russell King - ARM Linux
2017-10-30 15:09 ` Arnd Bergmann
2017-10-30 15:50 ` Russell King - ARM Linux
2017-10-30 17:01 ` Arnd Bergmann
2017-10-30 17:13 ` Russell King - ARM Linux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737601u4d.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).