From: Marc Zyngier <maz@kernel.org>
To: Vitaly Chikunov <vt@altlinux.org>
Cc: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
Oliver Upton <oliver.upton@linux.dev>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
Will Deacon <will@kernel.org>,
"james.morse@arm.com" <james.morse@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"Wangzhou (B)" <wangzhou1@hisilicon.com>,
Gleb Fotengauer-Malinovskiy <glebfm@altlinux.org>
Subject: Re: v6.13-rc1: Internal error: Oops - Undefined instruction: 0000000002000000 [#1] SMP
Date: Tue, 10 Dec 2024 09:55:30 +0000 [thread overview]
Message-ID: <86v7vrsvzh.wl-maz@kernel.org> (raw)
In-Reply-To: <20241210025127.jmkcpw7ixu4r7hxl@altlinux.org>
On Tue, 10 Dec 2024 02:51:27 +0000,
Vitaly Chikunov <vt@altlinux.org> wrote:
>
> On Fri, Dec 06, 2024 at 11:56:02PM +0300, Vitaly Chikunov wrote:
> > On Wed, Dec 04, 2024 at 08:51:26AM +0000, Marc Zyngier wrote:
> > > On Tue, 03 Dec 2024 22:14:53 +0000,
> > > Vitaly Chikunov <vt@altlinux.org> wrote:
> > > > On Tue, Dec 03, 2024 at 10:03:11AM +0000, Shameerali Kolothum Thodi wrote:
> > >
> > > Mark has described what the problem is likely to be. 6.6-stable needs
> > > to have 6685f5d572c22e10 backported, and it probably should have been
> > > Cc: to stable. Can you please apply the following patch to your *host*
> > > machine and retest?
> >
> > We tested the host with this patch applied over 6.6.63 and 6.13-rc1
> > guest does not Oops anymore.
> >
> > I'd suggest this is also get backported to 6.12.y branch.
>
> Please, can someone backport this patch to v6.12 and send to stable? This
> would be really useful to have this fixed and it's noted this is a
> critical bug.
Look: it took you a few good days to simply *report* that the hack I
gave you was helping. Surely you can similarly wait for a few days for
the interested parties to spin proper patches and *test* them?
And if you really cannot wait, feel free to backport this change to
whatever stable release you feel needs to be fixed and post the
result. I promise that I will review it. After all, you are so far
the only person with both the HW and the problem.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2024-12-10 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241202153618.GA6834@willie-the-truck>
[not found] ` <86ttbmt71k.wl-maz@kernel.org>
[not found] ` <20241202155940.p267a3tz5ypj4sog@altlinux.org>
[not found] ` <86ser6t6fs.wl-maz@kernel.org>
[not found] ` <20241202223119.k3uod4ksnlf7gqh2@altlinux.org>
[not found] ` <20241203092721.j473dthkbq6wzez7@altlinux.org>
[not found] ` <1847e34fa7724d28aeb22d93752f64f2@huawei.com>
[not found] ` <20241203221453.mwh6sozyczi4ec2k@altlinux.org>
[not found] ` <87jzcfsuep.wl-maz@kernel.org>
[not found] ` <20241206205602.7phcrxqsv4c6oul4@altlinux.org>
2024-12-10 2:51 ` v6.13-rc1: Internal error: Oops - Undefined instruction: 0000000002000000 [#1] SMP Vitaly Chikunov
2024-12-10 9:55 ` Marc Zyngier [this message]
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=86v7vrsvzh.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=glebfm@altlinux.org \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=oliver.upton@linux.dev \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=vt@altlinux.org \
--cc=wangzhou1@hisilicon.com \
--cc=will@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