[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4ffdf9130493c47e1893f15924d68a3da63dc92c.camel@suse.com>
Date: Fri, 03 May 2024 11:49:17 +0200
From: Jean DELVARE <jdelvare@...e.com>
To: Michael Kelley <mhklinux@...look.com>, Michael Schierl
<schierlm@....de>, "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
Hi Michael,
On Thu, 2024-05-02 at 17:02 +0000, Michael Kelley wrote:
> 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.
Thank you very much for your perseverance, let's see where it goes.
--
Jean Delvare
SUSE L3 Support
Powered by blists - more mailing lists