[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<SN6PR02MB41579E87F827F26B3A2E10FED4182@SN6PR02MB4157.namprd02.prod.outlook.com>
Date: Thu, 2 May 2024 17:02:05 +0000
From: Michael Kelley <mhklinux@...look.com>
To: Michael Schierl <schierlm@....de>, Jean DELVARE <jdelvare@...e.com>, "K.
Y. Srinivasan" <kys@...rosoft.com>, Haiyang Zhang <haiyangz@...rosoft.com>,
Wei Liu <wei.liu@...nel.org>, Dexuan Cui <decui@...rosoft.com>
CC: "linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Early kernel panic in dmi_decode when running 32-bit kernel on
Hyper-V on Windows 11
From: Michael Schierl <schierlm@....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.
Michael Kelley
Powered by blists - more mailing lists