On Fri, Jan 10, 2020 at 4:07 AM Michal Hocko <mhocko@xxxxxxxxxx> wrote: > > So you have redirected the output (stdout) to a file. This is less > effective than using a file directly because the progy makes sure to > preallocate and mlock the output file data as well. Anyway, let's have a > look what you managed to gather [chris@fmac tmp]$ /home/chris/read_vmstat readvmstatwkgtk.out file:readvmstatwkgtk.out timeout:1.0s buffer_size:10485760 mlockall. Continuing anyway: Cannot allocate memory Estimated 3744 entries fit to the buffer ^C This is with vm.swappiness=100, is also ~12 minutes. Responsiveness appears unchanged. File is attached here: https://bugzilla.kernel.org/show_bug.cgi?id=206117#c8 More curious is I get a call trace I haven't seen before when I try to login to this hung system, via ssh. That's in https://bugzilla.kernel.org/show_bug.cgi?id=206117#c7 -- Chris Murphy
