On Tue 22-08-17 15:55:30, Andrew Morton wrote:
>
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Tue, 22 Aug 2017 11:17:08 +0000 <email address hidden> wrote:
[...]
> Sadly I haven't been able to capture this information
> > fully yet due to said unresponsiveness.
Please try to collect /proc/vmstat in the bacground and provide the
collected data. Something like
while true
do
cp /proc/vmstat > vmstat.$(date +%s)
sleep 1s
done
If the system turns out so busy that it won't be able to fork a process
or write the output (which you will see by checking timestamps of files
and looking for holes) then you can try the attached proggy
./read_vmstat output_file timeout output_size
Note you might need to increase the mlock rlimit to lock everything into
memory.
Created attachment 258067
read_vmstat.c
On Tue 22-08-17 15:55:30, Andrew Morton wrote:
>
> (switched to email. Please respond via emailed reply-to-all, not via the
> bugzilla web interface).
>
> On Tue, 22 Aug 2017 11:17:08 +0000 <email address hidden> wrote:
[...]
> Sadly I haven't been able to capture this information
> > fully yet due to said unresponsiveness.
Please try to collect /proc/vmstat in the bacground and provide the
collected data. Something like
while true
do
cp /proc/vmstat > vmstat.$(date +%s)
sleep 1s
done
If the system turns out so busy that it won't be able to fork a process
or write the output (which you will see by checking timestamps of files
and looking for holes) then you can try the attached proggy
./read_vmstat output_file timeout output_size
Note you might need to increase the mlock rlimit to lock everything into
memory.