From: Carel Si <beibei.si@intel.com>
To: Borislav Petkov <bp@suse.de>
Cc: kernel test robot <oliver.sang@intel.com>,
Joerg Roedel <jroedel@suse.de>,
LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, lkp@lists.01.org, lkp@intel.com
Subject: Re: [LKP] Re: [x86/mm/64] f154f29085: BUG:kernel_reboot-without-warning_in_boot_stage
Date: Wed, 15 Dec 2021 15:00:13 +0800 [thread overview]
Message-ID: <20211215070012.GA26582@linux.intel.com> (raw)
In-Reply-To: <YbjIoewxGaodXHKF@zn.tnic>
Hi Boris,
On Tue, Dec 14, 2021 at 05:38:57PM +0100, Borislav Petkov wrote:
> On Thu, Dec 09, 2021 at 10:41:41PM +0800, kernel test robot wrote:
> >
> >
> > Greeting,
> >
> > FYI, we noticed the following commit (built with clang-14):
> >
> > commit: f154f290855b070cc94dd44ad253c0ef8a9337bb ("x86/mm/64: Flush global TLB on boot and AP bringup")
> > https://git.kernel.org/cgit/linux/kernel/git/tip/tip.git x86/mm
> >
> > in testcase: boot
> >
> > on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
> >
> > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> >
> >
> > +-------------------------------------------------+------------+------------+
> > | | 9de4999050 | f154f29085 |
> > +-------------------------------------------------+------------+------------+
> > | BUG:kernel_reboot-without-warning_in_boot_stage | 0 | 13 |
> > +-------------------------------------------------+------------+------------+
> >
> >
> > If you fix the issue, kindly add following tag
> > Reported-by: kernel test robot <oliver.sang@intel.com>
> >
> >
> > Physical KASLR using RDTSC...
> > Virtual KASLR using RDTSC...
> >
> > Decompressing Linux... Parsing ELF... Performing relocations... done.
> > Booting the kernel.
> > BUG: kernel reboot-without-warning in boot stage
> > Linux version 5.16.0-rc3-00003-gf154f290855b #1
> > Command line: ip=::::vm-snb-192::dhcp root=/dev/ram0 user=lkp job=/lkp/jobs/scheduled/vm-snb-192/boot-1-debian-10.4-x86_64-20200603.cgz-f154f290855b070cc94dd44ad253c0ef8a9337bb-20211208-23538-lnvkeg-5.yaml ARCH=x86_64 kconfig=x86_64-randconfig-a013-20211207 branch=tip/x86/mm commit=f154f290855b070cc94dd44ad253c0ef8a9337bb BOOT_IMAGE=/pkg/linux/x86_64-randconfig-a013-20211207/clang-14/f154f290855b070cc94dd44ad253c0ef8a9337bb/vmlinuz-5.16.0-rc3-00003-gf154f290855b vmalloc=128M initramfs_async=0 page_owner=on max_uptime=600 RESULT_ROOT=/result/boot/1/vm-snb/debian-10.4-x86_64-20200603.cgz/x86_64-randconfig-a013-20211207/clang-14/f154f290855b070cc94dd44ad253c0ef8a9337bb/3 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-worker30
> > Elapsed time: 60
>
> My guest boots fine here on an AMD host, albeit it takes a while until
> "Booting the kernel" appears.
>
> You probably should verify by hand whether your guest simply needs
> longer before it starts booting the kernel...
We have verified by hand, still can reproduce this issue.
We also double checked, this issue still exists in 35fa745286 ("x86/mm: Include
spinlock_t definition in pgtable") which is the head of tip/x86/mm, thanks.
=========================================================================================
compiler/kconfig/rootfs/sleep/tbox_group/testcase:
clang-14/x86_64-randconfig-a013-20211207/debian-10.4-x86_64-20200603.cgz/1/vm-snb/boot
commit:
9de4999050 ("x86/realmode: Add comment for Global bit usage in trampoline_pgd")
f154f29085 ("x86/mm/64: Flush global TLB on boot and AP bringup")
35fa745286 ("x86/mm: Include spinlock_t definition in pgtable.")
9de4999050b5f2e8 f154f290855b070cc94dd44ad25 35fa745286ac44ee26ed100c2bd
---------------- --------------------------- ---------------------------
fail:runs %reproduction fail:runs %reproduction fail:runs
| | | | |
:27 100% 27:27 100% 27:27 dmesg.BUG:kernel_reboot-without-warning_in_boot_stage
>
> early console in setup code
> early console in extract_kernel
> input_data: 0x0000000005ce82e0
> input_len: 0x0000000001d21920
> output: 0x0000000001000000
> output_len: 0x000000000650d2ec
> kernel_total_size: 0x0000000006e2c000
> needed_size: 0x0000000007000000
> trampoline_32bit: 0x000000000009d000
> Physical KASLR using RDTSC...
> Virtual KASLR using RDTSC...
>
> Decompressing Linux... Parsing ELF... Performing relocations... done.
> Booting the kernel.
> [ 0.000000][ T0] Linux version 5.16.0-rc3-00005-g35fa745286ac (boris@zn) (ClangBuiltLinux clang version 14.0.0 (https://github.com/llvm/llvm-project 08a770c378ca5d8975ef305d15f297c3f980d186), GNU ld (GNU Binutils for Debian) 2.37) #3 PREEMPT Tue Dec 14 17:29:41 CET 2021
> [ 0.000000][ T0] Command line: root=/dev/sda1 resume=/dev/sda2 debug ignore_loglevel log_buf_len=16M earlyprintk=ttyS0,115200 console=ttyS0,115200 console=tty0 no_console_suspend net.ifnames=0
> [ 0.000000][ T0] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
> [ 0.000000][ T0] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
> [ 0.000000][ T0] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
> [ 0.000000][ T0] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
> [ 0.000000][ T0] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
> [ 0.000000][ T0] signal: max sigframe size: 1360
> [ 0.000000][ T0] printk: debug: ignoring loglevel setting.
> [ 0.000000][ T0] printk: bootconsole [earlyser0] enabled
> [ 0.000000][ T0] BIOS-provided physical RAM map:
> ...
>
> --
> Regards/Gruss,
> Boris.
>
> SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg
> _______________________________________________
> LKP mailing list -- lkp@lists.01.org
> To unsubscribe send an email to lkp-leave@lists.01.org
next prev parent reply other threads:[~2021-12-15 7:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 14:41 [x86/mm/64] f154f29085: BUG:kernel_reboot-without-warning_in_boot_stage kernel test robot
2021-12-14 16:38 ` Borislav Petkov
2021-12-15 7:00 ` Carel Si [this message]
2021-12-15 10:05 ` [LKP] " Borislav Petkov
2021-12-16 7:04 ` Yin Fengwei
2021-12-16 10:06 ` Borislav Petkov
2021-12-16 11:58 ` Carel Si
2021-12-16 12:21 ` Yin Fengwei
2021-12-17 12:52 ` [LKP] Re: [x86/mm/64] f154f29085: BUG:kernel_reboot-without-warning_in_boot_stage - clang KCOV? Borislav Petkov
2021-12-17 18:04 ` Nathan Chancellor
2021-12-18 11:00 ` Borislav Petkov
2021-12-20 11:00 ` [PATCH] x86/mm: Prevent early boot triple-faults with instrumentation Borislav Petkov
2021-12-18 10:39 ` [LKP] Re: [x86/mm/64] f154f29085: BUG:kernel_reboot-without-warning_in_boot_stage - clang KCOV? Yin Fengwei
2021-12-18 11:01 ` Borislav Petkov
2021-12-20 1:51 ` Yin Fengwei
2021-12-21 14:31 ` Carel Si
2021-12-21 15:10 ` Marco Elver
2021-12-21 15:22 ` Borislav Petkov
2022-01-05 2:35 ` Yin Fengwei
2022-01-05 11:36 ` Borislav Petkov
2022-01-05 12:47 ` Yin Fengwei
2022-01-05 15:21 ` Borislav Petkov
2022-01-06 6:56 ` Yin Fengwei
2021-12-21 15:14 ` Borislav Petkov
2021-12-22 10:59 ` [tip: x86/mm] x86/mm: Prevent early boot triple-faults with instrumentation tip-bot2 for Borislav Petkov
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=20211215070012.GA26582@linux.intel.com \
--to=beibei.si@intel.com \
--cc=bp@suse.de \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox