From: kernel test robot <lkp@intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Jon Hunter <jonathanh@nvidia.com>
Subject: arch/xtensa/boot/boot-elf/bootstrap.S:68: Warning: value 0x1a0003000 truncated to 0xa0003000
Date: Sat, 26 Sep 2026 07:51:33 +0800 [thread overview]
Message-ID: <202609260743.V1BFyc9T-lkp@intel.com> (raw)
Hi Guenter,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 5fc5768c7ca92895ccd1de94dc521e5a55ae7896
commit: 916aa36042db8ee230543ffe0d192f900e8b8c9f clocksource/drivers/timer-tegra186: Avoid 64-bit divide operation
date: 1 year ago
config: xtensa-randconfig-r1303-20260925 (https://download.01.org/0day-ci/archive/20260926/202609260743.V1BFyc9T-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260926/202609260743.V1BFyc9T-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
| Fixes: 916aa36042db ("clocksource/drivers/timer-tegra186: Avoid 64-bit divide operation")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609260743.V1BFyc9T-lkp@intel.com/
All warnings (new ones prefixed by >>):
arch/xtensa/boot/boot-elf/bootstrap.S: Assembler messages:
arch/xtensa/boot/boot-elf/bootstrap.S:58: Error: invalid register 'atomctl' for 'wsr' instruction
>> arch/xtensa/boot/boot-elf/bootstrap.S:68: Warning: value 0x1a0003000 truncated to 0xa0003000
vim +68 arch/xtensa/boot/boot-elf/bootstrap.S
e85e335f8ff615 Max Filippov 2012-12-03 60
e85e335f8ff615 Max Filippov 2012-12-03 61 rsil a0, XCHAL_DEBUGLEVEL-1
e85e335f8ff615 Max Filippov 2012-12-03 62 rsync
4bedea94545165 Chris Zankel 2005-06-23 63 reset:
037602705109ec Max Filippov 2018-12-05 64 #if defined(CONFIG_INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX) && \
037602705109ec Max Filippov 2018-12-05 65 XCHAL_HAVE_PTP_MMU && XCHAL_HAVE_SPANNING_WAY
037602705109ec Max Filippov 2018-12-05 66 movi a0, CONFIG_KERNEL_LOAD_ADDRESS
037602705109ec Max Filippov 2018-12-05 67 #else
037602705109ec Max Filippov 2018-12-05 @68 movi a0, KERNELOFFSET
:::::: The code at line 68 was first introduced by commit
:::::: 037602705109ec2ab96340bea93ad87daa3ac046 xtensa: don't use l32r opcode directly
:::::: TO: Max Filippov <jcmvbkbc@gmail.com>
:::::: CC: Max Filippov <jcmvbkbc@gmail.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-09-25 23:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 23:51 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-19 7:38 kernel test robot
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=202609260743.V1BFyc9T-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel.lezcano@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=oe-kbuild-all@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®