| 7 Jun 2024 |
 erahhal | thx. Doesn't appear to be using tmpfs. | 15:54:26 |
 atemu12 | erahhal: Check dmesg whether the OOM killer reaped a process | 16:12:05 |
| atemu12 | Make sure you have swap | 16:12:16 |
| atemu12 | Even with 32G | 16:12:37 |
| erahhal | Yup, got swap | 16:32:18 |
 eyJhb | zramswap! That's what saved my life | 16:34:13 |
| erahhal | thank you i will try that! | 16:38:02 |
| atemu12 | Don't combine zram and physical swap | 16:39:16 |
| erahhal | Ok, definitely wont | 16:41:04 |
| erahhal | I'm using zfs btw, wonder if it's related | 16:45:31 |
| atemu12 | I had Android builds trigger ZFS incompatibilities with newer kernels before | 16:46:54 |
| atemu12 | Again, check dmesg whether an OOM event occured first | 16:47:05 |
| erahhal | No OOMs | 16:48:39 |
| atemu12 | Then check the logs why it's actually failing | 16:48:53 |
| atemu12 | Which kernel are you ono? | 16:48:58 |
| atemu12 | * Which kernel are you ono | 16:49:00 |
| atemu12 | * Which kernel are you on? | 16:49:04 |
| erahhal | A lot of these: [103533.864202] systemd-journald[1122]: Under memory pressure, flushing caches. | 16:49:16 |
| erahhal | Redacted or Malformed Event | 16:49:22 |
| erahhal | 6.8 | 16:49:26 |
| erahhal | Nothing in build logs other than the ninja line above | 16:49:53 |
| atemu12 | There is, just further up | 16:50:07 |
| erahhal | No, I lied, I found an OOM in dmesg | 16:50:45 |
| atemu12 | Some build systems abort quite late | 16:50:46 |
| erahhal | just didn't scroll high enough up | 16:50:49 |
| atemu12 | Check whether the time matches | 16:51:04 |
| atemu12 | (journalctl -k can be useful for that | 16:51:20 |
| atemu12 | * (journalctl -k can be useful for that) | 16:51:23 |
| erahhal | Nope, time is too early, 6pm last night. This failure happened overnight. Looking at journalctl | 16:52:51 |
| erahhal | nothing in journalctl | 16:53:30 |
