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/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