[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231220060030.GV1674809@ZenIV>
Date: Wed, 20 Dec 2023 06:00:30 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: Baoquan He <bhe@...hat.com>
Cc: kernel test robot <lkp@...el.com>, oe-kbuild-all@...ts.linux.dev,
linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: arch/sh/kernel/relocate_kernel.S:38: Error: invalid operands for
opcode
On Wed, Dec 20, 2023 at 01:44:19PM +0800, Baoquan He wrote:
> > arch/sh/kernel/relocate_kernel.S: Assembler messages:
> > >> arch/sh/kernel/relocate_kernel.S:38: Error: invalid operands for opcode
> > arch/sh/kernel/relocate_kernel.S:41: Error: invalid operands for opcode
> > arch/sh/kernel/relocate_kernel.S:126: Error: invalid operands for opcode
> > arch/sh/kernel/relocate_kernel.S:129: Error: invalid operands for opcode
>
> I reproduced this error, haven't got why and a way to fix it, will come
> back later if I have fix.
At a guess - after that commit ARCH_SUPPORTS_CRASH_DUMP is enough to enable CRASH_DUMP,
which selects KEXEC_CORE regardless of ARCH_SUPPORTS_KEXEC. And on sh you have
the former selected on any UP build, while the latter - only on MMU ones (i.e.
not SH2).
Powered by blists - more mailing lists