On Mon, 5 Oct 2015 22:03:46 +0200 Michal Hocko <mhocko@xxxxxxxxxx> wrote: > On Tue 15-09-15 10:39:19, Johannes Weiner wrote: > > On Thu, Sep 10, 2015 at 02:04:18PM -0700, Andrew Morton wrote: > > > (switched to email. Please respond via emailed reply-to-all, not via the > > > bugzilla web interface). > > > > > > On Tue, 01 Sep 2015 12:32:10 +0000 bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > > > > > > > https://bugzilla.kernel.org/show_bug.cgi?id=99471 > > > > > > Guys, could you take a look please? So this isn't fixed and a number of new reporters (cc'ed) are chiming in (let's please keep this going via email, not via the bugzilla UI!). We have various theories but I don't think we've nailed it down yet. Are any of the reporters able to come up with a set of instructions which will permit the developers to reproduce this bug locally? Can we think up a way of adding some form of debug/instrumentation to the kernel which will permit us to diagnose and fix this? It could be something which a tester manually adds or it could be something permanent, perhaps controlled via a procfs knob. -- 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>