Comment 18 for bug 1715861

Currently having problems consistently reproducing the error using kernel 4.13.0-041300-generic, despite trying.

Laptop generally runs without generating the error - I thought it might be related to recovery after hibernating, but that does not trigger the behaviour reliably. I have had one instance of the log filling, but without a reliable means of generating the problem, a bug report isn't very helpful.

However, using this kernel gives me a separate issue - hibernate works, but suspend does not. This is entirely reproducible, so I might have to file a bug for that. Suspend worked reliably in the previous kernel I was using.