From: Philip Li <philip.li@intel.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: kernel test robot <oliver.sang@intel.com>,
<oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>, <x86@kernel.org>,
"Ingo Molnar" <mingo@kernel.org>, Nadav Amit <namit@vmware.com>,
Andy Lutomirski <luto@kernel.org>,
Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Josh Poimboeuf <jpoimboe@redhat.com>, <linux-mm@kvack.org>
Subject: Re: [tip:x86/percpu] [x86/percpu] ca42563486: BUG:kernel_failed_in_early-boot_stage,last_printk:Booting_the_kernel(entry_offset:#)
Date: Sat, 7 Oct 2023 18:06:18 +0800 [thread overview]
Message-ID: <ZSEtmiUERKp1+KX7@rli9-mobl> (raw)
In-Reply-To: <CAFULd4bUu=wVhH8AweOPycEw2QsbFWSjP8ytr7SM6Z5WLOdWsA@mail.gmail.com>
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.
>
next prev parent reply other threads:[~2023-10-07 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2023-10-08 9:29 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZSEtmiUERKp1+KX7@rli9-mobl \
--to=philip.li@intel.com \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=namit@vmware.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.