Hi Josselin, On Thu, Jun 1, 2023 at 1:17 PM Josselin Poiret <[email protected]> wrote: > > It could be a transient failure > as well, which should probably be fixed then (unless it's something like > OOM).
Having seen the same error locally with three different generations, the failure does not strike me as transient. Maybe it's the other channel? As for an out-of-memory scenario, it's always a possibility but this particular equipment was rebooted two days ago and has 44 GB of combined RAM and swap. There was also no obvious sign of swap activity. Kind regards Felix * * * $ uptime 20:52:20 up 2 days 21:05, 0 users, load average: 0.96, 1.06, 0.98 $ cat /proc/meminfo MemTotal: 28657964 kB MemFree: 12833128 kB MemAvailable: 20422296 kB Buffers: 1031604 kB Cached: 7104156 kB SwapCached: 0 kB Active: 3573924 kB Inactive: 10087916 kB Active(anon): 6632 kB Inactive(anon): 6520256 kB Active(file): 3567292 kB Inactive(file): 3567660 kB Unevictable: 867160 kB Mlocked: 26080 kB SwapTotal: 16777212 kB SwapFree: 16777212 kB
