From: Amit Machhiwal <amachhiw@linux.ibm.com>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, kvm-ppc@vger.kernel.org
Subject: Re: early boot crash in init_tracer_tracefs
Date: Tue, 29 Sep 2026 16:39:05 +0530 [thread overview]
Message-ID: <20260929163751.4923b819-9f-amachhiw@linux.ibm.com> (raw)
In-Reply-To: <arubQ77S4mvvykaN@kunlun.suse.cz>
On 2026/09/29 01:04 PM, Michal Suchánek wrote:
> On Tue, Sep 29, 2026 at 09:36:05AM +0530, Amit Machhiwal wrote:
> > On 2026/09/28 11:43 AM, Amit Machhiwal wrote:
> > > Hi Michal,
> > >
> > > Thanks for the report. We have been looking at the crash and have some findings
> > > and follow-up questions.
> > >
> > > On 2026/09/25 10:10 AM, Michal Suchánek wrote:
> > > > Hello,
> > > >
> > > > There appears to be a regression between
> >
> > < snip >
> >
> > > >
> > > > Linux 7.0.12
> > > > https://github.com/openSUSE/kernel/tree/4c9922875554ec191166ba6c0145f12d8ff9d4fc
> > > > https://github.com/openSUSE/kernel-source/blob/2ebf0bc/config/ppc64le/default
> >
> > I have been trying to recreate the issue with this kernel and config but I
> > haven't been able to. The L2 KVM guest boots fine everytime.
> >
> > In addition to the requested information, could you please also share your qemu
> > cmdline/guest xml you used?
>
> The XML of the VM is below. What other information do you require?
Thanks for sharing the guest XML. I had requested some more info [1]. Could
you please share that?
[1] https://lore.kernel.org/all/20260928111234.faec09f7-8d-amachhiw@linux.ibm.com/
Thanks,
Amit
next prev parent reply other threads:[~2026-09-29 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 8:10 early boot crash in init_tracer_tracefs Michal Suchánek
2026-09-28 6:13 ` Amit Machhiwal
2026-09-29 4:06 ` Amit Machhiwal
2026-09-29 11:04 ` Michal Suchánek
2026-09-29 11:09 ` Amit Machhiwal [this message]
2026-09-29 12:18 ` Michal Suchánek
2026-09-29 19:49 ` Amit Machhiwal
2026-09-30 10:46 ` Michal Suchánek
2026-10-09 16:51 ` Amit Machhiwal
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=20260929163751.4923b819-9f-amachhiw@linux.ibm.com \
--to=amachhiw@linux.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=msuchanek@suse.de \
/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