[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#885166: instability with 4.14 regarding KVM virtualization



On Mon, Feb 19, 2018 at 06:31:16AM +0100, Salvatore Bonaccorso wrote:
> On Sun, Feb 18, 2018 at 11:34:21AM +0100, Marc Haber wrote:
> > On Sun, Feb 18, 2018 at 10:15:43AM +0100, Salvatore Bonaccorso wrote:
> > > Looking today through the kernel archive, I noticed an answer from
> > > Paolo Bonzini, <62aa6b81-5456-07dc-cf64-e46747d3a70d@redhat.com>,
> > > claiming this is fixed by
> > > 
> > > https://git.kernel.org/linus/2a266f23550be997d783f27e704b9b40c4010292
> > > which is in 4.15-rc8, and thus confirming that you did not had the
> > > issue anymore in 4.15.
> > 
> > ... unfortunately with a totally unexplaining commit message though.
> > 
> > > Closing this bug with that version, but do you have a chance to
> > > confirm that?
> > 
> > What exactly do you want me to test:
> > 
> > - that the bug doesn't happen any more in Debian 4.15 kernels?
> > - that ths bug still happens in Debian's 4.14 kernel and vanishes with
> >   the patch applied?
> > - Something else?
> 
> In an optimal case we get a confirmation that
> 2a266f23550be997d783f27e704b9b40c4010292 is the fixing commit for your
> issues. But given we have uploaded 4.15.4-1 to unstable, if you can
> confirm that this one defintively fix your issue that would be great
> (bonus if you can confirm your last non-working 4.14+commit fixes the
> issue as well).

If I used git correctly, then 4.14.20 already has
2a266f23550be997d783f27e704b9b40c4010292, so I tried 4.14.19. 4.14.19 on
the one virt host that had the most violent failures failed in the first
hour of operation, but with a slightly different error behavior that I
was used to. I am therefore not sure whether we are not talking about
multiple issues, one of them having been fixed somewhere in between
4.14.13 and 4.14.19.

I then applied 2a266f23550be997d783f27e704b9b40c4010292 to 4.14.19,
resulting in 4.4.19+, and this one has been running flawlessly for two
days (and 0 minutes, incidentally) now. I will stay on 4.14.19+ until
4.15.5 comes out (and will update then). If you don't hear from me again
in this bug report, then you can safely assume that 4.14.19+ lived on
the test machine until its planned decommissioning during the 4.15.5
rollout.

Hope this helps.

Greetings
Marc


-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany    |  lose things."    Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421


Reply to: