Kirill A. Shutemov <kirill <at> shutemov.name> writes: > > On Sat, Jan 23, 2016 at 03:57:21PM +0000, Hugh Greenberg wrote: > > Kirill A. Shutemov <kirill <at> shutemov.name> writes: > > > > > > Could you try to insert "late_initcall(set_recommended_min_free_kbytes);" > > > back and check if makes any difference. > > > > > > > We tested adding late_initcall(set_recommended_min_free_kbytes); > > back in 4.1.14 and it made a huge difference. We aren't sure if the > > issue is 100% fixed, but it could be. We will keep testing it. > > It would be nice to have values of min_free_kbytes before and after > set_recommended_min_free_kbytes() in your configuration. > We'll try to get this for you. The reports are coming from 2GB Haswell chromebooks. I have a 4GB haswell chromebook and I cannot reproduce the issue, even if I boot the kernel with 2GB or less. After more testing, we were still able to reproduce the issue. It seems to have taken longer to show up this time. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>