Comment 5 for bug 1938013

I've also had issues with this kernel on two machines. On my Thinkpad T460p (Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz), I had two cases where the ext4 driver suddenly detected an error in the journal and aborted it. Unfortunately, the system mounted the whole file system read only, so it couldn't save a crash report.
I was able to take a picture of some logs, here is my transcription:
EXT4-fs error (device dm-1): ext4_lookup:1590 inode #14680166: comm Okular::PixmapG: iget: checksum invalid
Aborting journal on device dm-1-8
EXT4-fs (dm-1): Remounting filesystem read-only

After that, lots of "checksum invalid" and "Read-only file system" messages. Rebooting, fsck had so many issues that automatic recovery didn't work and I was dropped to a terminal and had to manually confirm the changes.

The system has full disc encryption, so dm-1 is is the encrypted root volume.

Reverting back to 4.15.0-147-generic has produced no errors since Friday.