Re: [linux-next:master 6856/7430] hppa64-linux-ld: init/do_mounts.o(.text.unlikely+0x88): cannot reach dump_page

[Rong Chen <rong.a.chen@intel.com>]

On 6/5/21 7:08 PM, Arnd Bergmann wrote:
> On Sat, Jun 5, 2021 at 12:59 PM kernel test robot <lkp@intel.com> wrote:
>> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>> head:   ccc252d2e818f6a479441119ad453c3ce7c7c461
>> commit: 2ada05c3a46dda2e2b065a02307c0c6268d9678f [6856/7430] Merge remote-tracking branch 'asm-generic/master'
>> config: parisc-randconfig-r012-20210604 (attached as .config)
>> compiler: hppa64-linux-gcc (GCC) 9.3.0
>> reproduce (this is a W=1 build):
>>          wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
>>          chmod +x ~/bin/make.cross
>>          # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=2ada05c3a46dda2e2b065a02307c0c6268d9678f
>>          git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>          git fetch --no-tags linux-next master
>>          git checkout 2ada05c3a46dda2e2b065a02307c0c6268d9678f
>>          # save the attached .config to linux build tree
>>          COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=parisc
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
> Helge Deller already fixed this problem with commit 778e45d7720d
> ("parisc: Enable -mlong-calls
> gcc option with CONFIG_COMPILE_TEST"), so randconfig builds with
> CONFIG_COMPILE_TEST
> turned on don't run into link failures with overly large kernels.
>
>> All errors (new ones prefixed by >>):
>>
>>     hppa64-linux-ld: init/main.o(.init.text+0xb08): cannot reach panic
>>     init/main.o: in function `initcall_blacklist':
>>     (.init.text+0xb08): relocation truncated to fit: R_PARISC_PCREL22F against symbol `panic' defined in .text.unlikely section in kernel/panic.o
>>     hppa64-linux-ld: init/main.o(.init.text+0xcd0): cannot reach rest_init
>>     init/main.o: in function `arch_call_rest_init':
>>     (.init.text+0xcd0): relocation truncated to fit: R_PARISC_PCREL22F against symbol `rest_init' defined in .ref.text section in init/main.o
>>     hppa64-linux-ld: init/main.o(.init.text+0x1154): cannot reach panic
>>     init/main.o: in function `start_kernel':
>>     (.init.text+0x1154): relocation truncated to fit: R_PARISC_PCREL22F against symbol `panic' defined in .text.unlikely section in kernel/panic.o
>>     hppa64-linux-ld: init/main.o(.init.text+0x128c): cannot reach build_all_zonelists
>>     (.init.text+0x128c): relocation truncated to fit: R_PARISC_PCREL22F against symbol `build_all_zonelists' defined in .ref.text section in mm/page_alloc.o
> The specific set of errors is completely random, so any patch that
> changes the size of the
> kernel will trigger this output.
>
> I think the best solution would be for Kconfig to enforce that
> CONFIG_COMPILE_TEST is
> set to =y when running 'make randconfig'. I had previously discussed
> this with Rong
> and Philip, who preferred to not enforce COMPILE_TEST=y on the lkp setup because
> other users doing randconfig builds might still run into the same issues.
>
> An alternative would be to just not send out emails about randconfig
> failures that
> happen only with COMPILE_TEST=n.
>
>        Arnd


Hi Arnd,

We will ignore the error firstly, I'm a little confused, who can handle 
the randconfig failures
if COMPILE_TEST=n?

Best Regards,
Rong Chen