On Wed, Feb 14, 2018 at 10:56:35AM +0800, Haozhong Zhang wrote: > On 02/13/18 20:04 -0600, Josh Poimboeuf wrote: > > On Sun, Feb 11, 2018 at 02:39:41PM +0100, Marc Haber wrote: > > > Hi, > > > > > > after in total nine weeks of bisecting, broken filesystems, service > > > outages (thankfully on unportant systems), 4.15 seems to have fixed the > > > issue. After going to 4.15, the crashes never happened again. > > > > > > They have, however, happened with each and every 4.14 release I tried, > > > which I stopped doing with 4.14.15 on Jan 28. > > > > > > This means, for me, that the issue is fixed and that I have just wasted > > > nine weeks of time. > > > > > > For you, this means that you have a crippling, data-eating issue in the > > > current long-term releae kernel. I do sincerely hope that I never have > > > to lay my eye on any 4.14 kernel and hope that no major distribution > > > will release with this version. > > > > I saw something similar today, also in kvm_async_pf_task_wait(). I had > > -tip in the guest (based on 4.16.0-rc1) and Fedora > > 4.14.16-300.fc27.x86_64 on the host. > > Could you check whether this patch [1] on the host kernel fixes your > issue? Paolo had sent it to the stable tree and it may take a while > to be merged in the next 4.14 stable release (perhaps in this week). > > [1] https://patchwork.kernel.org/patch/10155177/ Unfortunately I don't know how to recreate it, the VM had been sitting in idle for over an hour when it happened. I'll leave it running overnight without the patch and see if it happens again. -- Josh
