[igt-dev] [PATCH i-g-t] runner: More task debug!

[Chris Wilson]

Quoting Chris Wilson (2020-04-16 11:10:25)
> Quoting Petri Latvala (2020-04-16 10:48:05)
> > On Thu, Apr 16, 2020 at 10:39:18AM +0100, Chris Wilson wrote:
> > > In a few cases, we hit a timeout where no process appears to be
> > > deadlocked (i.e. tasks stuck in 'D' with intertwined stacks) but
> > > everything appears to be running happily. Often, they appear to be
> > > fighting over the shrinker, so one naturally presumes we are running low
> > > on memory. But for tests that were designed to run with ample memory to
> > > spare, that is a little disconcerting and I would like to know where the
> > > memory actually went.
> > > 
> > > sysrq('m'): Will dump current memory info to your console
> > > 
> > > Sounds like that should do the trick.
> > > 
> > > Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
> > > Cc: Petri Latvala <petri.latvala at intel.com>
> > 
> > If indeed 'm' does what you want and not just useless crud like first
> > two lines of /proc/meminfo,
> 
> It calls into show_mem(), the same as used for oom and panics. Sounds
> promising. /Fortunately/ we have some timeouts so we will get to see
> what happens in practice.

Well we won't, because all the timeouts are being filtered by
blacklist-premerge! Nvm, nothing like testing on production.
-Chris