From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Kees Cook <keescook@chromium.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: boot failure of linux-next due to 1248fb6a8201 ("x86/mm: Randomize per-cpu entry area")
Date: Fri, 28 Oct 2022 17:06:50 +0100 [thread overview]
Message-ID: <CADVatmN-iM6mhWo+R1hDBvw_qg=NBdccSDQ2104A2JxZLBkExw@mail.gmail.com> (raw)
In-Reply-To: <fcd3d702-d645-2847-d8ee-0fb4734258c6@intel.com>
On Fri, Oct 28, 2022 at 3:33 PM Dave Hansen <dave.hansen@intel.com> wrote:
>
> On 10/28/22 06:29, Sudip Mukherjee (Codethink) wrote:
> > I will be happy to test any patch or provide any extra log if needed.
> > Though I am not sure how I will collect extra logs (if needed) as there
> > was no output from qemu.
>
> Could you share your qemu config? The command-line would be fine. Does
> it have a serial console set up?
qemu-system-x86_64 -m 2048 -smp 2 -chardev
socket,id=SOCKSYZ,server,nowait,host=localhost,port=46514 -mon
chardev=SOCKSYZ,mode=control -display none -serial stdio -no-reboot
-name VM-test -device virtio-rng-pci -enable-kvm -cpu
host,migratable=off -device e1000,netdev=net0 -netdev
user,id=net0,restrict=on,hostfwd=tcp:127.0.0.1:28993-:22 -hda
bullseye.img -snapshot -kernel bzImage -append "root=/dev/sda
console=ttyS0 net.ifnames=0 biosdevname=0"
serial is via stdio, and in normal boots I get the bootlog in the
terminal, but in this case there was nothing.
--
Regards
Sudip
next prev parent reply other threads:[~2022-10-28 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 13:29 boot failure of linux-next due to 1248fb6a8201 ("x86/mm: Randomize per-cpu entry area") Sudip Mukherjee (Codethink)
2022-10-28 14:33 ` Dave Hansen
2022-10-28 16:06 ` Sudip Mukherjee [this message]
2022-10-28 16:41 ` Kees Cook
2022-10-28 20:04 ` Sudip Mukherjee
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='CADVatmN-iM6mhWo+R1hDBvw_qg=NBdccSDQ2104A2JxZLBkExw@mail.gmail.com' \
--to=sudipm.mukherjee@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).