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

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

[kernel test robot]

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

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>

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
   hppa64-linux-ld: init/main.o(.init.text+0x1414): cannot reach unknown
   (.init.text+0x1414): relocation truncated to fit: R_PARISC_PCREL22F against `want_init_on_free'
   hppa64-linux-ld: init/main.o(.init.text+0x1424): cannot reach unknown
   (.init.text+0x1424): relocation truncated to fit: R_PARISC_PCREL22F against `want_init_on_free'
   hppa64-linux-ld: init/main.o(.init.text+0x160c): cannot reach profile_init
   (.init.text+0x160c): relocation truncated to fit: R_PARISC_PCREL22F against symbol `profile_init' defined in .ref.text section in kernel/profile.o
   hppa64-linux-ld: init/main.o(.init.text+0x19c8): cannot reach wait_for_completion
   init/main.o: in function `kernel_init_freeable':
   (.init.text+0x19c8): relocation truncated to fit: R_PARISC_PCREL22F against symbol `wait_for_completion' defined in .sched.text section in kernel/sched/completion.o
   hppa64-linux-ld: init/main.o(.init.text+0x1b44): cannot reach panic
   (.init.text+0x1b44): 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(.ref.text+0x1c): cannot reach rcu_scheduler_starting
   init/main.o: in function `rest_init':
   (.ref.text+0x1c): relocation truncated to fit: R_PARISC_PCREL22F against symbol `rcu_scheduler_starting' defined in .text section in kernel/rcu/tree.o
   hppa64-linux-ld: init/main.o(.ref.text+0x40): cannot reach kernel_thread
   (.ref.text+0x40): additional relocation overflows omitted from the output
   hppa64-linux-ld: init/main.o(.ref.text+0x70): cannot reach find_task_by_pid_ns
   hppa64-linux-ld: init/main.o(.ref.text+0xa8): cannot reach set_cpus_allowed_ptr
   hppa64-linux-ld: init/main.o(.ref.text+0xb8): cannot reach unknown
   hppa64-linux-ld: init/main.o(.ref.text+0xdc): cannot reach kernel_thread
   hppa64-linux-ld: init/main.o(.ref.text+0x104): cannot reach find_task_by_pid_ns
   hppa64-linux-ld: init/main.o(.ref.text+0x120): cannot reach unknown
   hppa64-linux-ld: init/main.o(.ref.text+0x148): cannot reach complete
   hppa64-linux-ld: init/main.o(.ref.text+0x168): cannot reach cpu_startup_entry
   hppa64-linux-ld: init/main.o(.ref.text+0x1a4): cannot reach unknown
   hppa64-linux-ld: init/main.o(.ref.text+0x1b4): cannot reach async_synchronize_full
   hppa64-linux-ld: init/main.o(.ref.text+0x1c4): cannot reach kprobe_free_init_mem
   hppa64-linux-ld: init/main.o(.ref.text+0x1d4): cannot reach kgdb_free_init_mem
   hppa64-linux-ld: init/main.o(.ref.text+0x204): cannot reach rcu_barrier
   hppa64-linux-ld: init/main.o(.ref.text+0x214): cannot reach mark_rodata_ro
   hppa64-linux-ld: init/main.o(.ref.text+0x234): cannot reach rcu_end_inkernel_boot
   hppa64-linux-ld: init/do_mounts.o(.init.text+0x23c): cannot reach unknown
   hppa64-linux-ld: init/do_mounts.o(.init.text+0x3e0): cannot reach unknown
   hppa64-linux-ld: init/do_mounts.o(.init.text+0x4e0): cannot reach unknown
   hppa64-linux-ld: init/do_mounts.o(.init.text+0x520): cannot reach unknown
   hppa64-linux-ld: init/do_mounts.o(.init.text+0x608): cannot reach panic
>> hppa64-linux-ld: init/do_mounts.o(.text.unlikely+0x88): cannot reach dump_page
   hppa64-linux-ld: init/do_mounts.o(.text.unlikely+0x10c): cannot reach __put_page
   hppa64-linux-ld: init/initramfs.o(.init.text+0x7e8): cannot reach unknown
   hppa64-linux-ld: init/initramfs.o(.init.text+0xc10): cannot reach unknown
   hppa64-linux-ld: init/initramfs.o(.init.text+0xf20): cannot reach unknown
   hppa64-linux-ld: init/initramfs.o(.init.text+0x19b4): cannot reach unknown
   hppa64-linux-ld: arch/parisc/mm/init.o(.text+0x58): cannot reach _raw_spin_lock
   hppa64-linux-ld: arch/parisc/mm/init.o(.text+0xa0): cannot reach _raw_spin_unlock
   hppa64-linux-ld: arch/parisc/mm/init.o(.text+0x124): cannot reach _raw_spin_lock
   hppa64-linux-ld: arch/parisc/mm/init.o(.text+0x1b8): cannot reach _raw_spin_unlock
   hppa64-linux-ld: arch/parisc/mm/init.o(.text+0x200): cannot reach _raw_spin_lock
   hppa64-linux-ld: arch/parisc/mm/init.o(.text+0x284): cannot reach _raw_spin_unlock
   hppa64-linux-ld: arch/parisc/mm/init.o(.text+0x2dc): cannot reach _raw_spin_lock
   hppa64-linux-ld: arch/parisc/mm/init.o(.text+0x310): cannot reach _raw_spin_unlock
   hppa64-linux-ld: arch/parisc/mm/init.o(.text+0x334): cannot reach _raw_spin_lock
   hppa64-linux-ld: arch/parisc/mm/init.o(.text+0x3bc): cannot reach _raw_spin_unlock
   hppa64-linux-ld: arch/parisc/mm/init.o(.init.text+0x7bc): cannot reach panic
   hppa64-linux-ld: arch/parisc/mm/init.o(.init.text+0xaa8): cannot reach panic
   hppa64-linux-ld: arch/parisc/mm/init.o(.ref.text+0x78): cannot reach unknown
   hppa64-linux-ld: arch/parisc/mm/init.o(.ref.text+0xa0): cannot reach unknown
   hppa64-linux-ld: arch/parisc/mm/init.o(.ref.text+0xc4): cannot reach unknown
   hppa64-linux-ld: arch/parisc/mm/init.o(.ref.text+0xe0): cannot reach __flush_tlb_range
   hppa64-linux-ld: arch/parisc/mm/init.o(.ref.text+0xf8): cannot reach flush_kernel_dcache_range_asm
   hppa64-linux-ld: arch/parisc/mm/init.o(.ref.text+0x110): cannot reach flush_kernel_icache_range_asm
   hppa64-linux-ld: arch/parisc/mm/init.o(.ref.text+0x144): cannot reach pdc_chassis_send_status
   hppa64-linux-ld: arch/parisc/kernel/setup.o(.init.text+0x118): cannot reach unknown
   hppa64-linux-ld: arch/parisc/kernel/setup.o(.init.text+0x308): cannot reach panic
   hppa64-linux-ld: arch/parisc/kernel/setup.o(.init.text+0x4c0): cannot reach panic
   hppa64-linux-ld: arch/parisc/kernel/hardware.o(.init.text+0x13c): cannot reach panic
   hppa64-linux-ld: arch/parisc/kernel/topology.o(.init.text+0x1a4): cannot reach unknown
   hppa64-linux-ld: arch/parisc/kernel/topology.o(.init.text+0x1c0): cannot reach unknown
   hppa64-linux-ld: arch/parisc/kernel/topology.o(.init.text+0x1f0): cannot reach unknown
   hppa64-linux-ld: arch/parisc/kernel/topology.o(.init.text+0x20c): cannot reach unknown
   hppa64-linux-ld: kernel/extable.o(.text+0x204): cannot reach rcu_nmi_enter
   hppa64-linux-ld: kernel/extable.o(.text+0x258): cannot reach rcu_nmi_exit
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x6ec): cannot reach warn_bogus_irq_restore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x79c): cannot reach warn_bogus_irq_restore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x8ac): cannot reach warn_bogus_irq_restore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x1108): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x1124): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x1174): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x1190): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x1540): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x160c): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x1c2c): cannot reach _raw_spin_lock_bh
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x1c64): cannot reach _raw_spin_unlock_bh
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x1d84): cannot reach warn_bogus_irq_restore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x1dd8): cannot reach warn_bogus_irq_restore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x1f94): cannot reach warn_bogus_irq_restore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x1fe0): cannot reach warn_bogus_irq_restore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x22b4): cannot reach warn_bogus_irq_restore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x22f8): cannot reach warn_bogus_irq_restore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x256c): cannot reach warn_bogus_irq_restore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x264c): cannot reach warn_bogus_irq_restore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x2754): cannot reach mutex_lock
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x280c): cannot reach mutex_unlock
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x28bc): cannot reach warn_bogus_irq_restore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x2a5c): cannot reach warn_bogus_irq_restore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x300c): cannot reach mutex_lock
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x3084): cannot reach _raw_spin_lock_bh
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x30b8): cannot reach _raw_spin_unlock_bh
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x3110): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x312c): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x3168): cannot reach mutex_unlock
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x3540): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x3568): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x3ea4): cannot reach _raw_spin_lock_irqsave
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x3ed0): cannot reach _raw_spin_unlock_irqrestore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x3f7c): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4170): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x428c): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x43e0): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4430): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4464): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4524): cannot reach mutex_unlock
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4938): cannot reach mutex_unlock
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4b0c): cannot reach mutex_lock
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4b28): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4b5c): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4b70): cannot reach mutex_unlock
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4d9c): cannot reach mutex_lock
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4db8): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4df0): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4e00): cannot reach mutex_unlock
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4e84): cannot reach mutex_lock
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4ea0): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4f3c): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x4f4c): cannot reach mutex_unlock
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x52c0): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x535c): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x5880): cannot reach _raw_spin_lock_irqsave
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x58f8): cannot reach _raw_spin_unlock_irqrestore
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x5d64): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x5e50): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x5f9c): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x6038): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x60e0): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x6140): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x622c): cannot reach _raw_spin_lock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x6290): cannot reach _raw_spin_unlock_irq
   hppa64-linux-ld: kernel/cgroup/cgroup.o(.text+0x67c0): cannot reach _raw_spin_lock_bh

---
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: 22936 bytes --]

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

[Arnd Bergmann]

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

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

[Rong Chen]

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

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

[Arnd Bergmann]

On Mon, Jun 7, 2021 at 8:27 AM Rong Chen <rong.a.chen@intel.com> wrote:
> 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: E
>
> We will ignore the error firstly, I'm a little confused, who can handle
> the randconfig failures if COMPILE_TEST=n?

The failures that you only see with COMPILE_TEST=n are the ones that
someone has previously decided can not be handled properly, for one
reason or another, examples include:

- rebuilding generated files that require additional tools to be
installed on the host,
  e.g. CONFIG_PREVENT_FIRMWARE_BUILD
- configurations that may or may not work but result in excessive
compiler warnings
  that are not otherwise interesting, e.g. GCC_PLUGIN_CYC_COMPLEXITY
- options that enable compile-time warnings about pointless configurations
  such as leaving out support for every machine
- options that are unlikely to have an effect on testing but slow down the build
  time (e.g. CONFIG_DEBUG_INFO) for build bots finite hardware resources.

On the primary architectures, randconfig builds with 'make -s' should generally
result in no output from the build, and I would consider any output
you get a bug.
When COMPILE_TEST is disabled, there are countless known issues in
configurations that make no practical sense.

        Arnd

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

[Rong Chen]

On 6/7/21 3:19 PM, Arnd Bergmann wrote:
> On Mon, Jun 7, 2021 at 8:27 AM Rong Chen <rong.a.chen@intel.com> wrote:
>> 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: E
>> We will ignore the error firstly, I'm a little confused, who can handle
>> the randconfig failures if COMPILE_TEST=n?
> The failures that you only see with COMPILE_TEST=n are the ones that
> someone has previously decided can not be handled properly, for one
> reason or another, examples include:
>
> - rebuilding generated files that require additional tools to be
> installed on the host,
>    e.g. CONFIG_PREVENT_FIRMWARE_BUILD
> - configurations that may or may not work but result in excessive
> compiler warnings
>    that are not otherwise interesting, e.g. GCC_PLUGIN_CYC_COMPLEXITY
> - options that enable compile-time warnings about pointless configurations
>    such as leaving out support for every machine
> - options that are unlikely to have an effect on testing but slow down the build
>    time (e.g. CONFIG_DEBUG_INFO) for build bots finite hardware resources.
>
> On the primary architectures, randconfig builds with 'make -s' should generally
> result in no output from the build, and I would consider any output
> you get a bug.
> When COMPILE_TEST is disabled, there are countless known issues in
> configurations that make no practical sense.
>
>          Arnd

Hi Arnd,

Thanks for the detailed explanation, and we have asked advice of 
internal developers,
we'll enable COMPILE_TEST for randconfig, and check the failures if 
COMPILE_TEST=n
in future.

BTW is there any issue that found by randconfig with COMPILE_TEST=n 
should be reported?

Best Regards,
Rong Chen

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

[Arnd Bergmann]

On Fri, Jun 18, 2021 at 4:30 AM Rong Chen <rong.a.chen@intel.com> wrote:
> On 6/7/21 3:19 PM, Arnd Bergmann wrote:
> > On Mon, Jun 7, 2021 at 8:27 AM Rong Chen <rong.a.chen@intel.com> wrote:
> >> On 6/5/21 7:08 PM, Arnd Bergmann wrote:

>
> Thanks for the detailed explanation, and we have asked advice of
> internal developers,
> we'll enable COMPILE_TEST for randconfig, and check the failures if
> COMPILE_TEST=n
> in future.

Awesome, thanks a lot.

> BTW is there any issue that found by randconfig with COMPILE_TEST=n
> should be reported?

It's definitely possible, but I expect that to be rare enough that
investing your
time elsewhere is more helpful. If you do wish to keep testing this
configuration,
this is how I would approach it:

- Since you have a database of known warnings and errors, a good thing to try
  would be analyze it and figure out the types of warning that predominantly
 happen with COMPILE_TEST=n randconfigs, but still happen occasionally
 with COMPILE_TEST=y, as those are more likely real bugs.

- possibly annotate them to find which particular Kconfig option that
gets guarded
  by COMPILE_TEST causes which output. This should be possible because
  there are only a small number of such options.

- Run a small percentage of randconfig builds with COMPILE_TEST=n and the
  cross-check the output against the known classes of diagnostic output
  rather than individual lines.

       Arnd