https://bugzilla.kernel.org/show_bug.cgi?id=204181
--- Comment #16 from Sergey Kondakov (virtuousfox@gmail.com) --- (In reply to Nicholas Kazlauskas from comment #15)
Thanks for the logs. I don't think this is related to your overclock.
Since this behavior wasn't previously observed during our 5.2 testing I think that either a patch got lost or changed during the submission process, or something from 5.3 was backported into 5.2 that shouldn't have been.
I don't think it's necessairly setup specific.
That means that you were able to reproduce it ? If so, any known workaround or ETA on the fix ? Is rc1 of 5.3 affected ? Any plans on backport to 5.2.x ?