From: 'Sebastian Andrzej Siewior' <bigeasy@linutronix.de>
To: Thomas Graziadei <thomas.graziadei@omicronenergy.com>
Cc: Mark Marshall <markmarshall14@gmail.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Mark Marshall <mark.marshall@omicronenergy.com>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>
Subject: Re: Kernel crash due to memory corruption with v5.4.26-rt17 and PowerPC e500
Date: Wed, 19 Aug 2020 09:11:38 +0200 [thread overview]
Message-ID: <20200819071138.bypg3slqhw7r577r@linutronix.de> (raw)
In-Reply-To: <c1ef757b-4cd6-410e-a647-a3303cef4b1b@EXC03-ATKLA.omicron.at>
On 2020-08-12 14:45:22 [+0200], Thomas Graziadei wrote:
> Hi Sebastian,
Hi Thomas,
> any progress on your side?
due to lack of time none. But I am on it…
> Do you think the patch could be applied for the next versions?
So I had a theory why it happens but then you said no so now I need
to figure out why it happens so I can write it in the changelog.
I believe you made it happen in qemu and you sent a .config and
everything so I will stare into it as soon as I can.
> Regards,
> Thomas
Sebastian
next prev parent reply other threads:[~2020-08-19 7:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 9:40 Kernel crash due to memory corruption with v5.4.26-rt17 and PowerPC e500 Mark Marshall
2020-05-29 13:14 ` Sebastian Andrzej Siewior
2020-05-29 15:38 ` Mark Marshall
2020-05-29 16:15 ` Sebastian Andrzej Siewior
2020-05-29 16:37 ` Sebastian Andrzej Siewior
2020-07-06 16:50 ` Sebastian Andrzej Siewior
2020-07-10 10:59 ` Thomas Graziadei
2020-08-12 12:45 ` Thomas Graziadei
2020-08-19 7:11 ` 'Sebastian Andrzej Siewior' [this message]
2020-09-01 7:41 ` 'Sebastian Andrzej Siewior'
2020-05-29 19:03 ` Mark Marshall
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=20200819071138.bypg3slqhw7r577r@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mark.marshall@omicronenergy.com \
--cc=markmarshall14@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=thomas.graziadei@omicronenergy.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;
as well as URLs for NNTP newsgroup(s).