On Fri, 17 Jul 2015, Herbert Poetzl wrote:
> It would be nice to know what version before 3.18.x was
> unaffected of this issue, as I presume either something
> in the kernel changed or we "lost" a hunk during porting.
With linux-image-3.14.38-vs220.127.116.11-beng, the problem
is not present.
-- Etienne Vogt (Etienne.Vogt@obspm.fr) Observatoire de Paris-Meudon Service InformatiqueReceived on Mon Jul 20 17:24:26 2015