Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>,
	Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [igt-dev] [PATCH i-g-t] runner: Show why we dump the task state
Date: Tue, 07 Apr 2020 11:42:01 +0300	[thread overview]
Message-ID: <875zeblmau.fsf@intel.com> (raw)
In-Reply-To: <20200407083533.1692277-1-chris@chris-wilson.co.uk>

On Tue, 07 Apr 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> 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@chris-wilson.co.uk>
> Cc: Petri Latvala <petri.latvala@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..7061b28d3 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);
> +	if (fd != -1) {
> +		write(fd, "<4>[IGT] ", 7);
> +		write(fd, msg, strlen(msg));
> +		close(fd);
> +	}
> +

igt_kmsg(KMSG_WARNING "%s\n", msg);

BR,
Jani.


>  	sysrq('t');
> +
> +	return msg;
>  }
>  
>  static const char *need_to_timeout(struct settings *settings,
> @@ -725,16 +736,12 @@ static const char *need_to_timeout(struct settings *settings,
>  		return "Killing the test because the kernel is tainted.\n";
>  
>  	if (settings->per_test_timeout != 0 &&
> -	    time_since_subtest > settings->per_test_timeout) {
> -		show_kernel_task_state();
> -		return "Per-test timeout exceeded. Killing the current test with SIGQUIT.\n";
> -	}
> +	    time_since_subtest > settings->per_test_timeout)
> +		return show_kernel_task_state("Per-test timeout exceeded. Killing the current test with SIGQUIT.\n");
>  
>  	if (settings->inactivity_timeout != 0 &&
> -	    time_since_activity > settings->inactivity_timeout) {
> -		show_kernel_task_state();
> -		return "Inactivity timeout exceeded. Killing the current test with SIGQUIT.\n";
> -	}
> +	    time_since_activity > settings->inactivity_timeout)
> +		return show_kernel_task_state("Inactivity timeout exceeded. Killing the current test with SIGQUIT.\n");
>  
>  	return NULL;
>  }

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2020-04-07  8:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07  8:31 [igt-dev] [PATCH i-g-t] runner: Show why we dump the task state Chris Wilson
2020-04-07  8:33 ` [igt-dev] ✗ Fi.CI.BUILD: failure for " Patchwork
2020-04-07  8:34 ` [igt-dev] [PATCH i-g-t] " Chris Wilson
2020-04-07  8:35 ` Chris Wilson
2020-04-07  8:42   ` Jani Nikula [this message]
2020-04-07  8:43     ` Chris Wilson
2020-04-07  9:51       ` Jani Nikula
2020-04-07  9:55   ` Petri Latvala
2020-04-07  9:58     ` Chris Wilson
2020-04-07  8:42 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2020-04-07  9:27 ` [igt-dev] ✓ Fi.CI.BAT: success for runner: Show why we dump the task state (rev2) Patchwork
2020-04-07 10:07 ` [igt-dev] [PATCH i-g-t v2] runner: Show why we dump the task state Chris Wilson
2020-04-07 10:41 ` [igt-dev] ✓ Fi.CI.BAT: success for runner: Show why we dump the task state (rev3) Patchwork
2020-04-07 16:38 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875zeblmau.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=petri.latvala@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox