On Tue, Feb 18, 2025 at 03:01:30PM -0800, mhkelle...@gmail.com wrote:
> From: Michael Kelley
>
> Gen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer
> device. When the kdump kernel runs in such a VM, loading the efifb
> driver may hang because of accessing the framebuffer at the wr
On Sun, Mar 09, 2025 at 03:20:04PM +0100, Helge Deller wrote:
> On 3/9/25 05:10, Michael Kelley wrote:
> > From: Helge Deller Sent: Saturday, March 8, 2025 6:59 PM
> > >
> > > On 2/19/25 00:01, mhkelle...@gmail.com wrote:
> > > > From: Michael Kelley
> > > >
> > [snip]
> >
> > > >
> > > > Rep
On 3/9/25 05:10, Michael Kelley wrote:
From: Helge Deller Sent: Saturday, March 8, 2025 6:59 PM
On 2/19/25 00:01, mhkelle...@gmail.com wrote:
From: Michael Kelley
[snip]
Reported-by: Thomas Tai
Fixes: c25a19afb81c ("fbdev/hyperv_fb: Do not clear global screen_info")
Signed-off-by: Mich
From: Helge Deller Sent: Saturday, March 8, 2025 6:59 PM
>
> On 2/19/25 00:01, mhkelle...@gmail.com wrote:
> > From: Michael Kelley
> >
[snip]
> >
> > Reported-by: Thomas Tai
> > Fixes: c25a19afb81c ("fbdev/hyperv_fb: Do not clear global screen_info")
> > Signed-off-by: Michael Kelley
> > ---
On 2/19/25 00:01, mhkelle...@gmail.com wrote:
From: Michael Kelley
Gen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer
device. When the kdump kernel runs in such a VM, loading the efifb
driver may hang because of accessing the framebuffer at the wrong
memory address.
The scenari
From: Michael Kelley
Gen 2 Hyper-V VMs boot via EFI and have a standard EFI framebuffer
device. When the kdump kernel runs in such a VM, loading the efifb
driver may hang because of accessing the framebuffer at the wrong
memory address.
The scenario occurs when the hyperv_fb driver in the origin
