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:58: Error: invalid register 'atomctl' for 'wsr' instruction
Date: Fri, 17 Apr 2026 21:49:39 +0800 [thread overview]
Message-ID: <202604172102.1KIXUw9l-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: 43cfbdda5af60ffc6272a7b8c5c37d1d0a181ca9
commit: 916aa36042db8ee230543ffe0d192f900e8b8c9f clocksource/drivers/timer-tegra186: Avoid 64-bit divide operation
date: 7 months ago
config: xtensa-randconfig-r063-20260417 (https://download.01.org/0day-ci/archive/20260417/202604172102.1KIXUw9l-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260417/202604172102.1KIXUw9l-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/202604172102.1KIXUw9l-lkp@intel.com/
All errors (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 +58 arch/xtensa/boot/boot-elf/bootstrap.S
e85e335f8ff615f Max Filippov 2012-12-03 42
e85e335f8ff615f Max Filippov 2012-12-03 43 .align 4
e85e335f8ff615f Max Filippov 2012-12-03 44 _SetupMMU:
09af39f649dac66 Max Filippov 2021-07-26 45 #if XCHAL_HAVE_WINDOWED
e85e335f8ff615f Max Filippov 2012-12-03 46 movi a0, 0
e85e335f8ff615f Max Filippov 2012-12-03 47 wsr a0, windowbase
e85e335f8ff615f Max Filippov 2012-12-03 48 rsync
e85e335f8ff615f Max Filippov 2012-12-03 49 movi a0, 1
e85e335f8ff615f Max Filippov 2012-12-03 50 wsr a0, windowstart
e85e335f8ff615f Max Filippov 2012-12-03 51 rsync
09af39f649dac66 Max Filippov 2021-07-26 52 #endif
e85e335f8ff615f Max Filippov 2012-12-03 53 movi a0, 0x1F
e85e335f8ff615f Max Filippov 2012-12-03 54 wsr a0, ps
e85e335f8ff615f Max Filippov 2012-12-03 55 rsync
e85e335f8ff615f Max Filippov 2012-12-03 56
e85e335f8ff615f Max Filippov 2012-12-03 57 #ifndef CONFIG_INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX
e85e335f8ff615f Max Filippov 2012-12-03 @58 initialize_mmu
:::::: The code at line 58 was first introduced by commit
:::::: e85e335f8ff615f74e29e09cc2599f095600114b xtensa: add MMU v3 support
:::::: TO: Max Filippov <jcmvbkbc@gmail.com>
:::::: CC: Chris Zankel <chris@zankel.net>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-04-17 13:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 13:49 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-12 23:52 arch/xtensa/boot/boot-elf/bootstrap.S:58: Error: invalid register 'atomctl' for 'wsr' instruction kernel test robot
2025-12-07 13:03 kernel test robot
2025-11-08 16:53 kernel test robot
2025-10-28 17:51 kernel test robot
2022-10-11 16:54 kernel test robot
2022-09-30 21:16 kernel test robot
2022-06-06 17:41 kernel test robot
2022-04-17 2:49 kernel test robot
2022-03-29 20:50 kernel test robot
2022-03-01 18:30 kernel test robot
2022-02-01 2:25 kernel test robot
2022-02-01 2:25 ` 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=202604172102.1KIXUw9l-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 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.