From: Jean DELVARE <jdelvare@suse.com>
To: Michael Kelley <mhklinux@outlook.com>,
Michael Schierl <schierlm@gmx.de>,
"K. Y. Srinivasan" <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Wei Liu <wei.liu@kernel.org>, Dexuan Cui <decui@microsoft.com>
Cc: "linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Early kernel panic in dmi_decode when running 32-bit kernel on Hyper-V on Windows 11
Date: Fri, 03 May 2024 11:49:17 +0200 [thread overview]
Message-ID: <4ffdf9130493c47e1893f15924d68a3da63dc92c.camel@suse.com> (raw)
In-Reply-To: <SN6PR02MB41579E87F827F26B3A2E10FED4182@SN6PR02MB4157.namprd02.prod.outlook.com>
Hi Michael,
On Thu, 2024-05-02 at 17:02 +0000, Michael Kelley wrote:
> From: Michael Schierl <schierlm@gmx.de> Sent: Friday, April 19, 2024 1:47 PM
> >
> > > Regardless of the 32-bit vs. 64-bit behavior, the DMI blob is malformed,
> > > almost certainly as created by Hyper-V. I'll see if I can bring this to
> > > the attention of one of my previous contacts on the Hyper-V team.
> >
>
> FYI, the right people on the Hyper-V team have been informed of the
> issue, and there's an internal bug report filed to track the resolution.
> I don't have access to the internal bug report, and can't predict when or
> how a fix might be made available. But given the impact, they should
> be motivated to work on it.
Thank you very much for your perseverance, let's see where it goes.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2024-05-03 9:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 13:06 Early kernel panic in dmi_decode when running 32-bit kernel on Hyper-V on Windows 11 Michael Schierl
2024-04-15 3:17 ` Michael Kelley
2024-04-15 21:03 ` Michael Schierl
2024-04-15 23:31 ` Michael Kelley
2024-04-16 21:24 ` Michael Schierl
2024-04-16 23:20 ` Michael Kelley
2024-04-17 9:43 ` Jean DELVARE
2024-04-17 15:51 ` Michael Kelley
2024-04-17 21:08 ` Michael Schierl
2024-04-17 22:34 ` Michael Kelley
2024-04-19 16:36 ` Michael Kelley
2024-04-19 20:47 ` Michael Schierl
2024-04-19 22:32 ` Michael Kelley
2024-05-02 17:02 ` Michael Kelley
2024-05-03 9:49 ` Jean DELVARE [this message]
2024-04-15 20:15 ` Wei Liu
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=4ffdf9130493c47e1893f15924d68a3da63dc92c.camel@suse.com \
--to=jdelvare@suse.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhklinux@outlook.com \
--cc=schierlm@gmx.de \
--cc=wei.liu@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