diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2022-10-23 21:16:09 +0100 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@kernel.org> | 2022-11-25 08:19:03 +0000 |
| commit | ac8dd062aa6cb095096e02240f497786891317b0 (patch) | |
| tree | 2ac4fe018e6576449b7d7dc44f7fa7b7f601b5cb /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | media: atomisp: Flush queue on atomisp_css_start() error (diff) | |
| download | linux-ac8dd062aa6cb095096e02240f497786891317b0.tar.gz linux-ac8dd062aa6cb095096e02240f497786891317b0.zip | |
media: atomisp: Log an error on failing to alloc private-mem
I managed to trigger an atomisp_css_start() error by pushing my test
system towards an OOM situation, this resulted in the following errors:
atomisp-isp2 0000:00:03.0: alloc pages err...
atomisp-isp2 0000:00:03.0: hmm_bo_alloc_pages failed.
atomisp-isp2 0000:00:03.0: stream[0] start error.
But it is not entirely clear what the root cause of
the "alloc pages err..." error is. I suspect the root cause is
alloc_pages_bulk_array() failing. Add a log message to make
the root cause more clear if this is hit again.
Reviewed-by: Andy Shevchenko <andy@kernel.org>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
