From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: drivers/clocksource/timer-mediatek.c:351:(.text+0x297): dangerous relocation: windowed longcall crosses 1GB boundary; return may fail: *UND*
Date: Sun, 04 Oct 2026 12:06:21 +0800 [thread overview]
Message-ID: <202610041116.5K7blOpy-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "bisect to a FBC not belonging to original linux-review patches: branch: linux-review/Luca-Leonardo-Scorcia/clocksource-drivers-timer-mediatek-Fix-random-crash-at-boot/20261002-091926, commit: 322dca3aa6d9da75845506ad72b09bd570b0d451"
:::::: Manual check reason: "xtensa: dangerous relocation"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Luca Leonardo Scorcia <l.scorcia@gmail.com>
CC: 0day robot <lkp@intel.com>
tree: https://github.com/intel-lab-lkp/linux/commits/Luca-Leonardo-Scorcia/clocksource-drivers-timer-mediatek-Fix-random-crash-at-boot/20261002-091926
head: 0c8c1bddeb603ee5834db94da982745e97c68119
commit: 322dca3aa6d9da75845506ad72b09bd570b0d451 clocksource/drivers/timer-mediatek: Convert to OF probing
date: 2 days ago
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: xtensa-randconfig-1000-20261003 (https://download.01.org/0day-ci/archive/20261004/202610041116.5K7blOpy-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261004/202610041116.5K7blOpy-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/r/202610041116.5K7blOpy-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/clocksource/timer-mediatek.o: in function `mtk_timer_probe':
>> drivers/clocksource/timer-mediatek.c:351:(.text+0x297): dangerous relocation: windowed longcall crosses 1GB boundary; return may fail: *UND*
vim +351 drivers/clocksource/timer-mediatek.c
322dca3aa6d9da7 Luca Leonardo Scorcia 2026-10-02 344
322dca3aa6d9da7 Luca Leonardo Scorcia 2026-10-02 345 static int mtk_timer_probe(struct platform_device *pdev)
322dca3aa6d9da7 Luca Leonardo Scorcia 2026-10-02 346 {
322dca3aa6d9da7 Luca Leonardo Scorcia 2026-10-02 347 int (*timer_init)(struct device_node *node);
322dca3aa6d9da7 Luca Leonardo Scorcia 2026-10-02 348 struct device_node *np = pdev->dev.of_node;
322dca3aa6d9da7 Luca Leonardo Scorcia 2026-10-02 349
322dca3aa6d9da7 Luca Leonardo Scorcia 2026-10-02 350 timer_init = of_device_get_match_data(&pdev->dev);
322dca3aa6d9da7 Luca Leonardo Scorcia 2026-10-02 @351 return timer_init(np);
322dca3aa6d9da7 Luca Leonardo Scorcia 2026-10-02 352 }
322dca3aa6d9da7 Luca Leonardo Scorcia 2026-10-02 353
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-04 4:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202610041116.5K7blOpy-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.