linux-samsung-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Moon <linux.amoon@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	linux-samsung-soc@vger.kernel.org,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	Chanwoo Choi <cw00.choi@samsung.com>
Subject: ARM: warning: relocation out of range on Exynos XU4 and U3+
Date: Thu, 11 Jun 2020 11:13:57 +0530	[thread overview]
Message-ID: <CANAwSgQv9BKV4QfZAgSfFQvO7ftcFyCGXEo+g4pgQA4mgK52iQ@mail.gmail.com> (raw)

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.

On XU4 - HCI

[alarm@archl-hc1d ~]$ uname -a
Linux archl-hc1d 5.7.1-1-ARCH #1 SMP PREEMPT Tue Jun 9 01:24:41 UTC
2020 armv7l GNU/Linux
[alarm@archl-hc1d ~]$ dmesg | grep relocation
[    6.188003] x_tables: section 4 reloc 2 sym 'mutex_lock':
relocation 28 out of range (0xbf0000bc -> 0xc101c154)
[    7.452559] sch_fq_codel: section 4 reloc 34 sym
'_raw_spin_lock_bh': relocation 28 out of range (0xbf000a44 ->
0xc101e9dc)
[    8.452434] uio: section 4 reloc 33 sym 'mutex_lock': relocation 28
out of range (0xbf009210 -> 0xc101c154)
[    8.576134] exynos5422_dmc: section 4 reloc 14 sym 'mutex_lock':
relocation 28 out of range (0xbf000188 -> 0xc101c154)
[    8.578422] exynos_rng: section 4 reloc 35 sym 'mutex_lock':
relocation 28 out of range (0xbf00a330 -> 0xc101c154)
[    8.585860] rng_core: section 4 reloc 15 sym
'mutex_lock_interruptible': relocation 28 out of range (0xbf0120b8 ->
0xc101c108)
[    8.818463] videobuf2_v4l2: section 4 reloc 62 sym 'mutex_lock':
relocation 29 out of range (0xbf0009b8 -> 0xc101c154)
[    8.938475] exynos_gsc: section 4 reloc 0 sym
'_raw_spin_lock_irqsave': relocation 28 out of range (0xbf000014 ->
0xc101e370)
[    8.996208] exynos_gsc: section 4 reloc 0 sym
'_raw_spin_lock_irqsave': relocation 28 out of range (0xbf00f014 ->
0xc101e370)
[    9.375951] r8152: section 4 reloc 4 sym 'mutex_lock': relocation
28 out of range (0xbf007130 -> 0xc101c154)

Share the console logs on Odroid XU4 HC1
[0] https://pastebin.com/5ZnEfyEM

On U3+

Linux archl-u3et 5.7.1-1-ARCH #1 SMP PREEMPT Tue Jun 9 01:24:41 UTC
2020 armv7l GNU/Linux
[alarm@archl-u3et ~]$ dmesg | grep relocation
[    5.324703] x_tables: section 4 reloc 2 sym 'mutex_lock':
relocation 28 out of range (0xbf0000bc -> 0xc101c154)
[    6.580612] sch_fq_codel: section 4 reloc 34 sym
'_raw_spin_lock_bh': relocation 28 out of range (0xbf000a44 ->
0xc101e9dc)
[    8.054852] uio: section 4 reloc 33 sym 'mutex_lock': relocation 28
out of range (0xbf009210 -> 0xc101c154)
[    8.168492] evdev: section 4 reloc 0 sym 'mutex_lock': relocation
28 out of range (0xbf018088 -> 0xc101c154)
[    8.435888] videobuf2_common: section 4 reloc 0 sym
'_raw_spin_lock_irqsave': relocation 28 out of range (0xbf005130 ->
0xc101e370)
[    8.656151] videobuf2_common: section 4 reloc 0 sym
'_raw_spin_lock_irqsave': relocation 28 out of range (0xbf005130 ->
0xc101e370)
[    8.671966] gpu_sched: section 4 reloc 0 sym '_raw_spin_lock':
relocation 28 out of range (0xbf016044 -> 0xc101e98c)
[    8.794059] exynos_bus: section 4 reloc 11 sym 'mutex_lock':
relocation 28 out of range (0xbf00514c -> 0xc101c154)
[    8.824699] exynos_bus: section 4 reloc 11 sym 'mutex_lock':
relocation 28 out of range (0xbf00d14c -> 0xc101c154)
[    8.824791] snd_timer: section 4 reloc 2 sym
'_raw_spin_lock_irqsave': relocation 28 out of range (0xbf0150d0 ->
0xc101e370)
[    9.002896] exynos_bus: section 4 reloc 11 sym 'mutex_lock':
relocation 28 out of range (0xbf01914c -> 0xc101c154)
[    9.139199] s5p_csis: section 4 reloc 2 sym
'_raw_spin_lock_irqsave': relocation 28 out of range (0xbf019050 ->
0xc101e370)
[    9.417648] snd_soc_hdmi_codec: section 4 reloc 24 sym
'mutex_lock': relocation 28 out of range (0xbf0053e0 -> 0xc101c154)

Share the console log for Odroid U3+
[1] https://pastebin.com/sm8qCHdV

Best Regards
-Anand

             reply	other threads:[~2020-06-11  5:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11  5:43 Anand Moon [this message]
2020-06-11  6:45 ` ARM: warning: relocation out of range on Exynos XU4 and U3+ Krzysztof Kozlowski
2020-06-11  7:51   ` Anand Moon
2020-06-11 10:59     ` Robin Murphy
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=CANAwSgQv9BKV4QfZAgSfFQvO7ftcFyCGXEo+g4pgQA4mgK52iQ@mail.gmail.com \
    --to=linux.amoon@gmail.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=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).