Not necessarily. This bug here was introduced somewhere in the 4.11 kernel
development (see bisect), 4.12.x still affected. I don't have this problem with
kernel 4.10.x and 4.9.x.

The other bug #95015 is about 4.4.x kernel, though the error message is the
same. So maybe the two have a common cause, but that's only guesswork from my
side.