linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* lib/x86_64/handlers.S:20: Error: unrecognized instruction `call route_exception'
@ 2021-07-26 21:10 kernel test robot
  2021-07-27 16:07 ` Sean Christopherson
  0 siblings, 1 reply; 3+ messages in thread
From: kernel test robot @ 2021-07-26 21:10 UTC (permalink / raw)
  To: Aaron Lewis; +Cc: kbuild-all, linux-kernel, Paolo Bonzini, Alexander Graf

[-- Attachment #1: Type: text/plain, Size: 10723 bytes --]

Hi Aaron,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   ff1176468d368232b684f75e82563369208bc371
commit: 29faeb9632012d6c3fa4aa33c3d589b9ff18b206 selftests: kvm: Add exception handling to selftests
date:   9 months ago
config: openrisc-randconfig-s031-20210726 (attached as .config)
compiler: or1k-linux-gcc (GCC) 10.3.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.3-341-g8af24329-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=29faeb9632012d6c3fa4aa33c3d589b9ff18b206
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout 29faeb9632012d6c3fa4aa33c3d589b9ff18b206
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=openrisc SHELL=/bin/bash -C tools/testing/selftests install

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   lib/x86_64/handlers.S: Assembler messages:
>> lib/x86_64/handlers.S:2: Error: unrecognized instruction `push %r15'
>> lib/x86_64/handlers.S:3: Error: unrecognized instruction `push %r14'
>> lib/x86_64/handlers.S:4: Error: unrecognized instruction `push %r13'
>> lib/x86_64/handlers.S:5: Error: unrecognized instruction `push %r12'
>> lib/x86_64/handlers.S:6: Error: unrecognized instruction `push %r11'
>> lib/x86_64/handlers.S:7: Error: unrecognized instruction `push %r10'
>> lib/x86_64/handlers.S:8: Error: unrecognized instruction `push %r9'
>> lib/x86_64/handlers.S:9: Error: unrecognized instruction `push %r8'
>> lib/x86_64/handlers.S:11: Error: unrecognized instruction `push %rdi'
>> lib/x86_64/handlers.S:12: Error: unrecognized instruction `push %rsi'
>> lib/x86_64/handlers.S:13: Error: unrecognized instruction `push %rbp'
>> lib/x86_64/handlers.S:14: Error: unrecognized instruction `push %rbx'
>> lib/x86_64/handlers.S:15: Error: unrecognized instruction `push %rdx'
>> lib/x86_64/handlers.S:16: Error: unrecognized instruction `push %rcx'
>> lib/x86_64/handlers.S:17: Error: unrecognized instruction `push %rax'
>> lib/x86_64/handlers.S:18: Error: unrecognized instruction `mov %rsp,%rdi'
>> lib/x86_64/handlers.S:20: Error: unrecognized instruction `call route_exception'
>> lib/x86_64/handlers.S:22: Error: unrecognized instruction `pop %rax'
>> lib/x86_64/handlers.S:23: Error: unrecognized instruction `pop %rcx'
>> lib/x86_64/handlers.S:24: Error: unrecognized instruction `pop %rdx'
   lib/x86_64/handlers.S:25: Error: unrecognized instruction `pop %rbx'
   lib/x86_64/handlers.S:26: Error: unrecognized instruction `pop %rbp'
   lib/x86_64/handlers.S:27: Error: unrecognized instruction `pop %rsi'
   lib/x86_64/handlers.S:28: Error: unrecognized instruction `pop %rdi'
   lib/x86_64/handlers.S:29: Error: unrecognized instruction `pop %r8'
   lib/x86_64/handlers.S:30: Error: unrecognized instruction `pop %r9'
   lib/x86_64/handlers.S:31: Error: unrecognized instruction `pop %r10'
   lib/x86_64/handlers.S:32: Error: unrecognized instruction `pop %r11'
   lib/x86_64/handlers.S:33: Error: unrecognized instruction `pop %r12'
   lib/x86_64/handlers.S:34: Error: unrecognized instruction `pop %r13'
   lib/x86_64/handlers.S:35: Error: unrecognized instruction `pop %r14'
   lib/x86_64/handlers.S:36: Error: unrecognized instruction `pop %r15'
   lib/x86_64/handlers.S:39: Error: unrecognized instruction `add $16,%rsp'
   lib/x86_64/handlers.S:40: Error: unrecognized instruction `iretq'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:73: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:74: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:74: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:75: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:75: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:75: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:76: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:76: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:76: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:76: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:76: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:76: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:76: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:76: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:76: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:76: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:77: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:77: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:77: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:77: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:77: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:77: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:78: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:78: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `jmp handle_exception'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $0'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `pushq $vector'
   lib/x86_64/handlers.S:79: Error: unrecognized instruction `jmp handle_exception'

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32043 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: lib/x86_64/handlers.S:20: Error: unrecognized instruction `call route_exception'
  2021-07-26 21:10 lib/x86_64/handlers.S:20: Error: unrecognized instruction `call route_exception' kernel test robot
@ 2021-07-27 16:07 ` Sean Christopherson
  2021-07-27 18:51   ` Paolo Bonzini
  0 siblings, 1 reply; 3+ messages in thread
From: Sean Christopherson @ 2021-07-27 16:07 UTC (permalink / raw)
  To: kernel test robot
  Cc: Aaron Lewis, kbuild-all, linux-kernel, Paolo Bonzini, Alexander Graf

On Tue, Jul 27, 2021, kernel test robot wrote:
> Hi Aaron,
> 
> First bad commit (maybe != root cause):
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head:   ff1176468d368232b684f75e82563369208bc371
> commit: 29faeb9632012d6c3fa4aa33c3d589b9ff18b206 selftests: kvm: Add exception handling to selftests
> date:   9 months ago
> config: openrisc-randconfig-s031-20210726 (attached as .config)
> compiler: or1k-linux-gcc (GCC) 10.3.0
> reproduce:
>         wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>         chmod +x ~/bin/make.cross
>         # apt-get install sparse
>         # sparse version: v0.6.3-341-g8af24329-dirty
>         # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=29faeb9632012d6c3fa4aa33c3d589b9ff18b206
>         git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>         git fetch --no-tags linus master
>         git checkout 29faeb9632012d6c3fa4aa33c3d589b9ff18b206
>         # save the attached .config to linux build tree
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross C=1
>         CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=openrisc
>         SHELL=/bin/bash -C tools/testing/selftests install

KVM's selftests don't play nice with cross-compiles for unsupported architectures.
arm64 and s390 have expilict x86_64 -> {arm64,s390} support from commit 66d69e081b52
("selftests: fix kvm relocatable native/cross builds and installs"), but for
anything else the Makefile assumes an x86_64 target.

Realistically, only test bots are going to run afoul of our laziness.  Do we care
enough to fix this up properly? 

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: lib/x86_64/handlers.S:20: Error: unrecognized instruction `call route_exception'
  2021-07-27 16:07 ` Sean Christopherson
@ 2021-07-27 18:51   ` Paolo Bonzini
  0 siblings, 0 replies; 3+ messages in thread
From: Paolo Bonzini @ 2021-07-27 18:51 UTC (permalink / raw)
  To: Sean Christopherson, kernel test robot
  Cc: Aaron Lewis, kbuild-all, linux-kernel, Alexander Graf

On 27/07/21 18:07, Sean Christopherson wrote:
> On Tue, Jul 27, 2021, kernel test robot wrote:
>> Hi Aaron,
>>
>> First bad commit (maybe != root cause):
>>
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head:   ff1176468d368232b684f75e82563369208bc371
>> commit: 29faeb9632012d6c3fa4aa33c3d589b9ff18b206 selftests: kvm: Add exception handling to selftests
>> date:   9 months ago
>> config: openrisc-randconfig-s031-20210726 (attached as .config)
>> compiler: or1k-linux-gcc (GCC) 10.3.0
>> reproduce:
>>          wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>>          chmod +x ~/bin/make.cross
>>          # apt-get install sparse
>>          # sparse version: v0.6.3-341-g8af24329-dirty
>>          # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=29faeb9632012d6c3fa4aa33c3d589b9ff18b206
>>          git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>          git fetch --no-tags linus master
>>          git checkout 29faeb9632012d6c3fa4aa33c3d589b9ff18b206
>>          # save the attached .config to linux build tree
>>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross C=1
>>          CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=openrisc
>>          SHELL=/bin/bash -C tools/testing/selftests install
> 
> KVM's selftests don't play nice with cross-compiles for unsupported architectures.
> arm64 and s390 have expilict x86_64 -> {arm64,s390} support from commit 66d69e081b52
> ("selftests: fix kvm relocatable native/cross builds and installs"), but for
> anything else the Makefile assumes an x86_64 target.
> 
> Realistically, only test bots are going to run afoul of our laziness.  Do we care
> enough to fix this up properly?

Seems easy enough, I will give it a shot.

Paolo


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2021-07-27 18:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-26 21:10 lib/x86_64/handlers.S:20: Error: unrecognized instruction `call route_exception' kernel test robot
2021-07-27 16:07 ` Sean Christopherson
2021-07-27 18:51   ` Paolo Bonzini

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).