All of lore.kernel.org
 help / color / mirror / Atom feed
* [tip:x86/percpu] [x86/percpu]  ca42563486: BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#)
@ 2023-10-07  6:15 kernel test robot
  2023-10-07  9:36 ` Uros Bizjak
  0 siblings, 1 reply; 4+ messages in thread
From: kernel test robot @ 2023-10-07  6:15 UTC (permalink / raw)
  To: Uros Bizjak
  Cc: oe-lkp, lkp, linux-kernel, x86, Ingo Molnar, Nadav Amit,
	Andy Lutomirski, Brian Gerst, Denys Vlasenko, H. Peter Anvin,
	Linus Torvalds, Peter Zijlstra, Thomas Gleixner, Josh Poimboeuf,
	linux-mm, oliver.sang



Hello,

kernel test robot noticed "BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#)" on:

commit: ca4256348660cb2162668ec3d13d1f921d05374a ("x86/percpu: Use C for percpu read/write accessors")
https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git x86/percpu

[test failed on linux-next/master 0f0fe5040de5e5fd9b040672e37725b046e312f0]

in testcase: boot

compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G

(please refer to attached dmesg/kmsg for entire log/backtrace)


+--------------------------------------------------------------------------------------+------------+------------+
|                                                                                      | 9a462b9eaf | ca42563486 |
+--------------------------------------------------------------------------------------+------------+------------+
| boot_successes                                                                       | 13         | 0          |
| boot_failures                                                                        | 0          | 13         |
| BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#) | 0          | 13         |
+--------------------------------------------------------------------------------------+------------+------------+


If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202310071301.a5113890-oliver.sang@intel.com


trampoline_32bit: 0x0000000000000000

Decompressing Linux... Parsing ELF... done.
Booting the kernel (entry_offset: 0x0000000000000080).
convert early boot stage from hang to failed
BUG: kernel failed in early-boot stage, last printk: Booting the kernel (entry_offset: 0x0000000000000080).
Linux version 6.5.0-11417-gca4256348660 #1
Command line: ip=::::vm-meta-312::dhcp root=/dev/ram0 RESULT_ROOT=/result/boot/300/vm-snb/debian-11.1-x86_64-20220510.cgz/x86_64-randconfig-006-20231006/gcc-12/ca4256348660cb2162668ec3d13d1f921d05374a/3 BOOT_IMAGE=/pkg/linux/x86_64-randconfig-006-20231006/gcc-12/ca4256348660cb2162668ec3d13d1f921d05374a/vmlinuz-6.5.0-11417-gca4256348660 branch=tip/x86/percpu job=/lkp/jobs/scheduled/vm-meta-312/boot-300-debian-11.1-x86_64-20220510.cgz-x86_64-randconfig-006-20231006-ca4256348660-20231007-59999-9pqjzt-4.yaml user=lkp ARCH=x86_64 kconfig=x86_64-randconfig-006-20231006 commit=ca4256348660cb2162668ec3d13d1f921d05374a nmi_watchdog=0 vmalloc=256M initramfs_async=0 page_owner=on max_uptime=600 LKP_SERVER=internal-lkp-server selinux=0 debug apic=debug sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 net.ifnames=0 printk.devkmsg=on panic=-1 softlockup_panic=1 nmi_watchdog=panic oops=panic load_ramdisk=2 prompt_ramdisk=0 drbd.minor_count=8 systemd.log_level=err ignore_loglevel console=tty0 earlyprintk=ttyS0,115200 console=ttyS0,115200 vga=normal rw rcuperf.shutdown=0 watchdog_thresh=240

Kboot worker: lkp-worker57
Elapsed time: 780


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20231007/202310071301.a5113890-oliver.sang@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [tip:x86/percpu] [x86/percpu] ca42563486: BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#)
  2023-10-07  6:15 [tip:x86/percpu] [x86/percpu] ca42563486: BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#) kernel test robot
@ 2023-10-07  9:36 ` Uros Bizjak
  2023-10-07 10:06   ` Philip Li
  0 siblings, 1 reply; 4+ messages in thread
From: Uros Bizjak @ 2023-10-07  9:36 UTC (permalink / raw)
  To: kernel test robot
  Cc: oe-lkp, lkp, linux-kernel, x86, Ingo Molnar, Nadav Amit,
	Andy Lutomirski, Brian Gerst, Denys Vlasenko, H. Peter Anvin,
	Linus Torvalds, Peter Zijlstra, Thomas Gleixner, Josh Poimboeuf,
	linux-mm

On Sat, Oct 7, 2023 at 8:16 AM kernel test robot <oliver.sang@intel.com> wrote:
>
>
>
> Hello,
>
> kernel test robot noticed "BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#)" on:
>
> commit: ca4256348660cb2162668ec3d13d1f921d05374a ("x86/percpu: Use C for percpu read/write accessors")
> https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git x86/percpu
>
> [test failed on linux-next/master 0f0fe5040de5e5fd9b040672e37725b046e312f0]
>
> in testcase: boot
>
> compiler: gcc-12
> test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
>
> (please refer to attached dmesg/kmsg for entire log/backtrace)
>
>
> +--------------------------------------------------------------------------------------+------------+------------+
> |                                                                                      | 9a462b9eaf | ca42563486 |
> +--------------------------------------------------------------------------------------+------------+------------+
> | boot_successes                                                                       | 13         | 0          |
> | boot_failures                                                                        | 0          | 13         |
> | BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#) | 0          | 13         |
> +--------------------------------------------------------------------------------------+------------+------------+

Since this is a randconfig (x86_64-randconfig-006-20231006), does it
mean that all other configs worked OK:

i386                             allmodconfig   gcc
i386                              allnoconfig   gcc
i386                             allyesconfig   gcc
i386         buildonly-randconfig-001-20231005   gcc
i386         buildonly-randconfig-002-20231005   gcc
i386         buildonly-randconfig-003-20231005   gcc
i386         buildonly-randconfig-004-20231005   gcc
i386         buildonly-randconfig-005-20231005   gcc
i386         buildonly-randconfig-006-20231005   gcc
i386                              debian-10.3   gcc
i386                                defconfig   gcc
i386                  randconfig-001-20231005   gcc
i386                  randconfig-002-20231005   gcc
i386                  randconfig-003-20231005   gcc
i386                  randconfig-004-20231005   gcc
i386                  randconfig-005-20231005   gcc
i386                  randconfig-006-20231005   gcc

and

x86_64                            allnoconfig   gcc
x86_64                           allyesconfig   gcc
x86_64                              defconfig   gcc
x86_64                randconfig-001-20231005   gcc
x86_64                randconfig-002-20231005   gcc
x86_64                randconfig-003-20231005   gcc
x86_64                randconfig-004-20231005   gcc
x86_64                randconfig-005-20231005   gcc
x86_64                randconfig-006-20231005   gcc
x86_64                          rhel-8.3-rust   clang
x86_64                               rhel-8.3   gcc

are of interest to me. Assuming they are built with gcc-12, I wouldn't
immediately blame the compiler for the failure. Due to the nature of
the change, perhaps a weakness in the kernel has been found with some
obscure config setting. As said, my default Fedora 39 kernel (6.5.5),
built with gcc-13 works without any problems.

Also, does a successful report from yesterday [1] mean everything was OK?

[1] https://lore.kernel.org/lkml/202310060322.yeZgaj6Q-lkp@intel.com/

Uros.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [tip:x86/percpu] [x86/percpu] ca42563486: BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#)
  2023-10-07  9:36 ` Uros Bizjak
@ 2023-10-07 10:06   ` Philip Li
  2023-10-08  9:29     ` Ingo Molnar
  0 siblings, 1 reply; 4+ messages in thread
From: Philip Li @ 2023-10-07 10:06 UTC (permalink / raw)
  To: Uros Bizjak
  Cc: kernel test robot, oe-lkp, lkp, linux-kernel, x86, Ingo Molnar,
	Nadav Amit, Andy Lutomirski, Brian Gerst, Denys Vlasenko,
	H. Peter Anvin, Linus Torvalds, Peter Zijlstra, Thomas Gleixner,
	Josh Poimboeuf, linux-mm

On Sat, Oct 07, 2023 at 11:36:26AM +0200, Uros Bizjak wrote:
> On Sat, Oct 7, 2023 at 8:16 AM kernel test robot <oliver.sang@intel.com> wrote:
> >
> >
> >
> > Hello,
> >
> > kernel test robot noticed "BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#)" on:
> >
> > commit: ca4256348660cb2162668ec3d13d1f921d05374a ("x86/percpu: Use C for percpu read/write accessors")
> > https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git x86/percpu
> >
> > [test failed on linux-next/master 0f0fe5040de5e5fd9b040672e37725b046e312f0]
> >
> > in testcase: boot
> >
> > compiler: gcc-12
> > test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
> >
> > (please refer to attached dmesg/kmsg for entire log/backtrace)
> >
> >
> > +--------------------------------------------------------------------------------------+------------+------------+
> > |                                                                                      | 9a462b9eaf | ca42563486 |
> > +--------------------------------------------------------------------------------------+------------+------------+
> > | boot_successes                                                                       | 13         | 0          |
> > | boot_failures                                                                        | 0          | 13         |
> > | BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#) | 0          | 13         |
> > +--------------------------------------------------------------------------------------+------------+------------+
> 
> Since this is a randconfig (x86_64-randconfig-006-20231006), does it
> mean that all other configs worked OK:

Thanks Uros. The previous report you receive are for build/compling test,
which means for these tested kconfigs, the kernel are built successfully.

For this report, we have found a possible boot issue on the reported kconfig
as compared to the parent commit. You can kindly do a check.

Thanks

> 
> i386                             allmodconfig   gcc
> i386                              allnoconfig   gcc
> i386                             allyesconfig   gcc
> i386         buildonly-randconfig-001-20231005   gcc
> i386         buildonly-randconfig-002-20231005   gcc
> i386         buildonly-randconfig-003-20231005   gcc
> i386         buildonly-randconfig-004-20231005   gcc
> i386         buildonly-randconfig-005-20231005   gcc
> i386         buildonly-randconfig-006-20231005   gcc
> i386                              debian-10.3   gcc
> i386                                defconfig   gcc
> i386                  randconfig-001-20231005   gcc
> i386                  randconfig-002-20231005   gcc
> i386                  randconfig-003-20231005   gcc
> i386                  randconfig-004-20231005   gcc
> i386                  randconfig-005-20231005   gcc
> i386                  randconfig-006-20231005   gcc
> 
> and
> 
> x86_64                            allnoconfig   gcc
> x86_64                           allyesconfig   gcc
> x86_64                              defconfig   gcc
> x86_64                randconfig-001-20231005   gcc
> x86_64                randconfig-002-20231005   gcc
> x86_64                randconfig-003-20231005   gcc
> x86_64                randconfig-004-20231005   gcc
> x86_64                randconfig-005-20231005   gcc
> x86_64                randconfig-006-20231005   gcc
> x86_64                          rhel-8.3-rust   clang
> x86_64                               rhel-8.3   gcc
> 
> are of interest to me. Assuming they are built with gcc-12, I wouldn't
> immediately blame the compiler for the failure. Due to the nature of
> the change, perhaps a weakness in the kernel has been found with some
> obscure config setting. As said, my default Fedora 39 kernel (6.5.5),
> built with gcc-13 works without any problems.
> 
> Also, does a successful report from yesterday [1] mean everything was OK?
> 
> [1] https://lore.kernel.org/lkml/202310060322.yeZgaj6Q-lkp@intel.com/
> 
> Uros.
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [tip:x86/percpu] [x86/percpu] ca42563486: BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#)
  2023-10-07 10:06   ` Philip Li
@ 2023-10-08  9:29     ` Ingo Molnar
  0 siblings, 0 replies; 4+ messages in thread
From: Ingo Molnar @ 2023-10-08  9:29 UTC (permalink / raw)
  To: Philip Li
  Cc: Uros Bizjak, kernel test robot, oe-lkp, lkp, linux-kernel, x86,
	Nadav Amit, Andy Lutomirski, Brian Gerst, Denys Vlasenko,
	H. Peter Anvin, Linus Torvalds, Peter Zijlstra, Thomas Gleixner,
	Josh Poimboeuf, linux-mm


* Philip Li <philip.li@intel.com> wrote:

> For this report, we have found a possible boot issue on the reported 
> kconfig as compared to the parent commit. You can kindly do a check.

Thank you for reporting this - I've excluded tip:x86/percpu from 
tip:master for the time being, until we manage to fix the bug.

This should address the boot crash starting with tomorrow's -next 
integration.

Thanks,

	Ingo

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-10-08  9:29 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-10-07  6:15 [tip:x86/percpu] [x86/percpu] ca42563486: BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#) kernel test robot
2023-10-07  9:36 ` Uros Bizjak
2023-10-07 10:06   ` Philip Li
2023-10-08  9:29     ` Ingo Molnar

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.