From: Marc Zyngier <maz@kernel.org>
To: Vitaly Chikunov <vt@altlinux.org>
Cc: Will Deacon <will@kernel.org>,
james.morse@arm.com, linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org, oliver.upton@linux.dev,
mark.rutland@arm.com
Subject: Re: v6.13-rc1: Internal error: Oops - Undefined instruction: 0000000002000000 [#1] SMP
Date: Mon, 02 Dec 2024 16:07:03 +0000 [thread overview]
Message-ID: <86ser6t6fs.wl-maz@kernel.org> (raw)
In-Reply-To: <20241202155940.p267a3tz5ypj4sog@altlinux.org>
On Mon, 02 Dec 2024 15:59:40 +0000,
Vitaly Chikunov <vt@altlinux.org> wrote:
>
> Marc,
>
> On Mon, Dec 02, 2024 at 03:53:59PM +0000, Marc Zyngier wrote:
> >
> > What the log doesn't say is what the host is. Is it 6.13-rc1 as well?
>
> No, host is 6.6.60.
Right. I wouldn't be surprised if:
- this v6.6 kernel doesn't hide the MPAM feature as it should (and
that's proably something we should backport)
- you get a nastygram in the host log telling you that the guest has
executed something it shouldn't (you'll get the encoding of the
instruction)
Can you confirm these two things?
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-12-02 16:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 4:58 v6.13-rc1: Internal error: Oops - Undefined instruction: 0000000002000000 [#1] SMP Vitaly Chikunov
2024-12-02 15:36 ` Will Deacon
2024-12-02 15:53 ` Marc Zyngier
2024-12-02 15:59 ` Vitaly Chikunov
2024-12-02 16:07 ` Marc Zyngier [this message]
2024-12-02 17:53 ` Mark Rutland
2024-12-02 22:31 ` Vitaly Chikunov
2024-12-03 1:19 ` Oliver Upton
2024-12-03 4:03 ` Vitaly Chikunov
2024-12-05 2:09 ` Vitaly Chikunov
2024-12-03 9:27 ` Vitaly Chikunov
2024-12-03 10:03 ` Shameerali Kolothum Thodi
2024-12-03 22:14 ` Vitaly Chikunov
2024-12-04 8:51 ` Marc Zyngier
2024-12-04 18:34 ` Vitaly Chikunov
2024-12-04 19:13 ` Marc Zyngier
2024-12-05 8:53 ` Shameerali Kolothum Thodi
2024-12-04 18:53 ` Vitaly Chikunov
2024-12-06 20:56 ` Vitaly Chikunov
2024-12-10 2:51 ` Vitaly Chikunov
2024-12-10 9:55 ` Marc Zyngier
2024-12-02 16:06 ` Shameerali Kolothum Thodi
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=86ser6t6fs.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=oliver.upton@linux.dev \
--cc=vt@altlinux.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.