[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YLp2hulQpBl7JRSO@casper.infradead.org>
Date: Fri, 4 Jun 2021 19:52:54 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Dexuan Cui <decui@...rosoft.com>
Cc: 'Wei Liu' <wei.liu@...nel.org>, vkuznets <vkuznets@...hat.com>,
'Vineeth Pillai' <viremana@...ux.microsoft.com>,
"'dri-devel@...ts.freedesktop.org'" <dri-devel@...ts.freedesktop.org>,
"'linux-hyperv@...r.kernel.org'" <linux-hyperv@...r.kernel.org>,
"'linux-fbdev@...r.kernel.org'" <linux-fbdev@...r.kernel.org>,
"'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
Michael Kelley <mikelley@...rosoft.com>
Subject: Re: [bug report] Commit ccf953d8f3d6 ("fb_defio: Remove custom
address_space_operations") breaks Hyper-V FB driver
On Fri, Jun 04, 2021 at 06:37:49PM +0000, Dexuan Cui wrote:
> > From: Dexuan Cui
> > Sent: Friday, June 4, 2021 11:17 AM
> > > >> ...
> > > > I've heard a similar report from Vineeth but we didn't get to the bottom
> > > > of this.
> > > I have just tried reverting the commit mentioned above and it solves the
> > > GUI freeze
> > > I was also seeing. Previously, login screen was just freezing, but VM
> > > was accessible
> > > through ssh. With the above commit reverted, I can login to Gnome.
> > >
> > > Looks like I am also experiencing the same bug mentioned here.
> > >
> > > Thanks,
> > > Vineeth
> >
> > As Matthew mentioned, this is a known issue:
> > https://lwn.net/ml/linux-kernel/YLZEhv0cpZp8uVE3@casper.infradead.org/
> >
> > Matthew has reverted ccf953d8f3d6:
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=
> > 0b78f8bcf4951af30b0ae83ea4fad27d641ab617
> > so the latest mainline should work now.
> >
> > Thanks,
> > Dexuan
>
> Hi Matthew,
> With today's latest mainline 16f0596fc1d78a1f3ae4628cff962bb297dc908c,
> the Xorg works again in Linux VM on Hyper-V, but when I reboot the VM, I
> always see a lot of "BUG: Bad page state in process Xorg " warnings (there
> are about 60 such warnings) before the VM reboots.
>
> BTW, I happen to have an older Mar-28 mainline kernel (36a14638f7c0654),
> which has the same warnings.
>
> Any idea which change introduced the warnings?
Looks like someone forgot to call fb_deferred_io_cleanup()?
Powered by blists - more mailing lists