Hi Anshuman, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on arm64/for-next/core] [also build test WARNING on soc/for-next v5.8-rc1 next-20200616] [cannot apply to arm/for-next xlnx/master kvmarm/next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the base tree in git format-patch, please see https://stackoverflow.com/a/37406982] url: https://github.com/0day-ci/linux/commits/Anshuman-Khandual/arm64-panic-Un... base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core config: arm64-allyesconfig (attached as .config) compiler: aarch64-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 # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64 If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp(a)intel.com&gt; All warnings (new ones prefixed by >>, old ones prefixed by <<): 403 | void dump_kernel_offset(void) | ^~~~~~~~~~~~~~~~~~ vim +/dump_kernel_offset +403 arch/arm64/kernel/setup.c 402 404 { 405 const unsigned long offset = kaslr_offset(); 406 407 if (IS_ENABLED(CONFIG_RANDOMIZE_BASE) && offset > 0) { 408 pr_emerg("Kernel Offset: 0x%lx from 0x%lx\n", 409 offset, KIMAGE_VADDR); 410 pr_emerg("PHYS_OFFSET: 0x%llx\n", PHYS_OFFSET); 411 } else { 412 pr_emerg("Kernel Offset: disabled\n"); 413 } 414 } 415 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org