On Thu, Nov 29, 2018 at 12:54:13PM +0100, Thierry Reding wrote:

> This looks like the same issue that I was seeing a couple of weeks ago.
> There's a fix for this here:

> 	http://patchwork.ozlabs.org/patch/993812/

> Not sure if Ben's picked that up yet, though.

It's certainly not visible in -next and the issue is showing so guessing
not.