04-20-2021, 02:39 PM
@aknaggbaugh
I've never seen SLUB or SLAB errors in any Linux system and certainly not in moOde but, who knows, maybe I just wasn't looking in the right place at the right time.
My customary search of the InterWeb™ for the SLUB error message results in a real mixed bag of hits. Deep in one (regarding ZFS in a virtual machine running under heavy load) is an interesting comment "this isn't a bug just a kernel warning that memory was very tight" which I think might apply in your case because of your observation "after a period of time...it begins responding again."
In another thread you said you have moved /var/cache to RAM. That would pressure memory. In yet another thread, you've posted about local display. That also pressures memory.
Try making changes one at a time to see if the SLUB error recurs. You might even try enabling swap to give the system a pressure relief valve.
Regards,
Kent
PS - giving us the output from moodeutl -s or moodeutl -l (this latter preferably after a reboot) is always a good first step in establishing the context of an issue.
I've never seen SLUB or SLAB errors in any Linux system and certainly not in moOde but, who knows, maybe I just wasn't looking in the right place at the right time.
My customary search of the InterWeb™ for the SLUB error message results in a real mixed bag of hits. Deep in one (regarding ZFS in a virtual machine running under heavy load) is an interesting comment "this isn't a bug just a kernel warning that memory was very tight" which I think might apply in your case because of your observation "after a period of time...it begins responding again."
In another thread you said you have moved /var/cache to RAM. That would pressure memory. In yet another thread, you've posted about local display. That also pressures memory.
Try making changes one at a time to see if the SLUB error recurs. You might even try enabling swap to give the system a pressure relief valve.
Regards,
Kent
PS - giving us the output from moodeutl -s or moodeutl -l (this latter preferably after a reboot) is always a good first step in establishing the context of an issue.
