I think there are two issues at play here, one is the bad pmd one, and one is the original "huge_memory: mapcount 0 page_mapcount 1".
Perhaps we could break the bad pmd issue out into a different LP bug?
People with the original bug - was anyone able to verify if this happened on a more recent kernel? My understanding of mm/huge_memory.c is that it was significantly refactored after 4.4, so I would be interested to hear if that makes the issue go away.
I think disabling transparent huge pages on boot should also make the issue go away if anyone is able to try that?
Hi all,
I think there are two issues at play here, one is the bad pmd one, and one is the original "huge_memory: mapcount 0 page_mapcount 1".
Perhaps we could break the bad pmd issue out into a different LP bug?
People with the original bug - was anyone able to verify if this happened on a more recent kernel? My understanding of mm/huge_memory.c is that it was significantly refactored after 4.4, so I would be interested to hear if that makes the issue go away.
I think disabling transparent huge pages on boot should also make the issue go away if anyone is able to try that?
Regards,
Daniel