From: Peter Zijlstra <peterz@infradead.org>
To: Venkat Rao Bagalkote <venkat88@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
vschneid@redhat.com, mingo@kernel.org, sfr@canb.auug.org.au
Subject: Re: [PowerPC][Linux-next][6.11.0-rc4-next-20240820] OOPs while running LTP FS Stress
Date: Mon, 16 Sep 2024 13:30:30 +0200 [thread overview]
Message-ID: <20240916113030.GZ4723@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <82b9c434-a0fd-4488-95be-a45b8cd4b6e6@linux.vnet.ibm.com>
On Mon, Sep 16, 2024 at 12:00:52PM +0530, Venkat Rao Bagalkote wrote:
> I am seeing below kernel crash from 6.11.0-rc4-next-20240820.
0820 is almost a month old by now, did you verify if the same happens on
a recent kernel? We did fix a bunch of issues around this.
next prev parent reply other threads:[~2024-09-16 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 6:30 [PowerPC][Linux-next][6.11.0-rc4-next-20240820] OOPs while running LTP FS Stress Venkat Rao Bagalkote
2024-09-16 11:30 ` Peter Zijlstra [this message]
2024-09-16 14:40 ` Venkat Rao Bagalkote
2024-09-19 6:09 ` [patch] " Mike Galbraith
2024-09-19 14:39 ` Venkat Rao Bagalkote
2024-09-20 2:15 ` Mike Galbraith
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=20240916113030.GZ4723@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=venkat88@linux.vnet.ibm.com \
--cc=vschneid@redhat.com \
/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