From: Robin Murphy <robin.murphy@arm.com>
To: Anand Moon <linux.amoon@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: Chanwoo Choi <cw00.choi@samsung.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: ARM: warning: relocation out of range on Exynos XU4 and U3+
Date: Thu, 11 Jun 2020 11:59:46 +0100 [thread overview]
Message-ID: <19d94eb3-d08c-e436-ccc0-cca56291eed2@arm.com> (raw)
In-Reply-To: <CANAwSgQqW6+W2=QcrAx8DsafK_0eMtQthQWcZWy9NDWxN3WkbQ@mail.gmail.com>
On 2020-06-11 08:51, Anand Moon wrote:
> Hi Krzysztof,
>
> On Thu, 11 Jun 2020 at 12:15, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On Thu, Jun 11, 2020 at 11:13:57AM +0530, Anand Moon wrote:
>>> Hi All,
>>>
>>> I would like to report some warnings I observed on pre-compiled kernel
>>> image (5.7.1-1-ARCH) from Archlinux.
>>> Sometimes ethernet would not come up and get connected, so in order to
>>> investigate.
>>> I found below warnings, So I am sharing the logs at my end.
>>>
>>> Are these warnings related to in-consistency in locking, How can we
>>> Investigate more to fix this issue.
>>
>> These rather look like some address space randomization or some compiler
>> (LLVM?) feature. Not Exynos-specific anyway.
>>
>> You should report it to Arch folks because they know how they compiled
>> the kernel and what config they used (althogh config you can find in
>> /proc/config.gz).
>
> Thanks for your inputs.
> Ok I will do more checks at my end, before reporting further to Archlinux.
Looks like the relocations fail when loading modules, and PLTs are not
enbabled[1], so chances are the kernel image has simply grown too big to
keep everything within direct branch range of everything else.
Robin.
[1]
https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-odroid-xu3/config#L619
next prev parent reply other threads:[~2020-06-11 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 5:43 ARM: warning: relocation out of range on Exynos XU4 and U3+ Anand Moon
2020-06-11 6:45 ` Krzysztof Kozlowski
2020-06-11 7:51 ` Anand Moon
2020-06-11 10:59 ` Robin Murphy [this message]
2020-06-12 2:53 ` Anand Moon
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=19d94eb3-d08c-e436-ccc0-cca56291eed2@arm.com \
--to=robin.murphy@arm.com \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux.amoon@gmail.com \
--cc=m.szyprowski@samsung.com \
/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).