From: Saurabh Singh Sengar Sent: Saturday,
February 22, 2025 9:27 AM
>
> On Wed, Feb 19, 2025 at 05:22:36AM +, Michael Kelley wrote:
> > From: Saurabh Sengar Sent: Saturday, February
> > 15,
> 2025 1:21 AM
> > >
> > > When a Hyper-V framebuffer device is unbind, hyperv_fb driver tries to
>
On Wed, Feb 19, 2025 at 05:22:36AM +, Michael Kelley wrote:
> From: Saurabh Sengar Sent: Saturday, February
> 15, 2025 1:21 AM
> >
> > When a Hyper-V framebuffer device is unbind, hyperv_fb driver tries to
> > release the framebuffer forcefully. If this framebuffer is in use it
> > produce t
From: Saurabh Sengar Sent: Saturday, February 15,
2025 1:21 AM
>
> When a Hyper-V framebuffer device is unbind, hyperv_fb driver tries to
> release the framebuffer forcefully. If this framebuffer is in use it
> produce the following WARN and hence this framebuffer is never released.
>
> [ 44.
When a Hyper-V framebuffer device is unbind, hyperv_fb driver tries to
release the framebuffer forcefully. If this framebuffer is in use it
produce the following WARN and hence this framebuffer is never released.
[ 44.111220] WARNING: CPU: 35 PID: 1882 at
drivers/video/fbdev/core/fb_info.c:70 f
