Red Hat Bugzilla – Bug 1303979
OOM with kernel 4.3.x (regression)
Last modified: 2016-02-03 03:16:37 EST
Description of problem:
When booted from 4.3 kernels, laptop starts killing process for OOM within 8 hours.
Version-Release number of selected component (if applicable):
Always, but no hard timeline.
Steps to Reproduce:
1. Boot with 4.3.4 (hang on to last working kernel-4.2.8)
2. Do stuff. Network seems important
OOM, with userspace memory only 50% used.
Same stable operation as 4.2.8 kernel.
Adding a USB wifi dongle (for a total of 2 connected wifi nets) seemed to cut time to OOM in half. But this was subjective and squishy. Haven't done it often enough to quantify.
This is different from https://bugzilla.redhat.com/show_bug.cgi?id=1303270 in that SUnreclaim is not increasing without bound. However, it is similar in that user space processes don't seem to be using the memory. (And in 4.3 kernel being generally borked.) I'll be adding logs and another regression for intel video.
Created attachment 1120490 [details]
This may be related to bug#1303990, as video was "jumpy" prior to the OOMs, and firefox was using more memory than for the same set of tabs with 4.2.8. Thunderbird is always a pig, but the OOMs follow 4.3 kernels.
Note, while the OOM handler starts with killing thunderbird and firefox (the biggest pigs), it continues killing processes, including mate-panel, various applets, etc, until the desktop is empty! It only seems to kill processes using X, however. Which is why I think bug#1303990 might be related.
Created attachment 1120497 [details]
systemd-jrournal gets the axe
*** This bug has been marked as a duplicate of bug 1303270 ***