On 15.11.18 10:52, Baoquan He wrote: > On 11/15/18 at 10:42am, David Hildenbrand wrote: >> I am wondering why it is always the last memory block of that device >> (and even that node). Coincidence? > > I remember one or two times it's the last 6G or 4G which stall there, > the size of memory block is 2G. But most of time it's the last memory > block. And from the debug printing added by Michal's patch, it's the > stress program itself which owns the migrating page and loop forvever > there. > Alright, seems like you found a very good reproducer for an existing problem :) -- Thanks, David / dhildenb
