Hi Marc,

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-e46747d3a...@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).

Regards,
Salvatore

Reply via email to