Ok, I'm compiling it now on my other PC. Meanwhile, the error happened twice in the same day. That's odd, it usually took at least 2 days to manifest again. Could it be that something chanded on my PC?
Anyways, here's the error: 4609.325351] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1447: inode #26610978: comm updatedb.mlocat: checksumming directory block 0 [ 4609.327443] Aborting journal on device nvme0n1p2-8. [ 4609.329533] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [ 4609.357281] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1447: inode #26739117: comm updatedb.mlocat: checksumming directory block 0 [ 4609.627350] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1447: inode #5901277: comm updatedb.mlocat: checksumming directory block 0 [ 4795.596378] perf: interrupt took too long (2563 > 2500), lowering kernel.perf_event_max_sample_rate to 78000 [ 4911.346846] audit: type=1400 audit(1519876882.781:29): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=4149 comm="cupsd" capability=12 capname="net_admin" I'll test the new compiler kernel in some hours -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
