[igt-dev] [PATCH i-g-t] runner: Show why we dump the task state
Chris Wilson
chris at chris-wilson.co.uk
Tue Apr 7 08:34:46 UTC 2020
Quoting Chris Wilson (2020-04-07 09:31:05)
> Include the reason why we are dumping the task state (test timeout) in
> the kmsg log prior to the task state. Hopefully this helps when reading
> the dump.
>
> Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
> Cc: Petri Latvala <petri.latvala at intel.com>
> ---
> runner/executor.c | 25 ++++++++++++++++---------
> 1 file changed, 16 insertions(+), 9 deletions(-)
>
> diff --git a/runner/executor.c b/runner/executor.c
> index 1b69f9c57..25e3187a3 100644
> --- a/runner/executor.c
> +++ b/runner/executor.c
> @@ -678,9 +678,20 @@ static bool sysrq(char cmd)
> return success;
> }
>
> -static void show_kernel_task_state(void)
> +static const char *show_kernel_task_state(const char *msg)
> {
> + int fd;
> +
> + fd = open("/dev/kmsg", O_WRONlY);
Yeah, I haven't had coffee.
-Chris
More information about the igt-dev
mailing list