public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Petri Latvala <petri.latvala@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] runner: Also consider TAINT_MACHINE_CHECK as abortable taint
Date: Wed, 05 Jun 2019 15:47:57 +0300	[thread overview]
Message-ID: <87zhmwqjuq.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20190605123656.GT21222@phenom.ffwll.local>

Daniel Vetter <daniel@ffwll.ch> writes:

> On Wed, Jun 05, 2019 at 03:16:07PM +0300, Petri Latvala wrote:
>> Signed-off-by: Petri Latvala <petri.latvala@intel.com>
>> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>
> I've seen lots of machines where these happen as normal side-effect of
> thermal throtlling. For some value of "normal".
>

Thermals could be ok and filtered if we can be somewhat certain that
the state didn't suffer. Can we?

> Do we really want to reboot on these? It could be like the network thing I
> recently disabled, and then everyone started screaming because our
> machines where constantly rebooting due to network cards/drivers
> temporarily having a bad time (but usually recovering).

Reboot? This won't get fixed by reboot as the hw is busted.

The question is that is it fruitful to weed out software
failures with a broken hardware.

-Mika

> -Daniel
>> ---
>>  runner/executor.c | 1 +
>>  1 file changed, 1 insertion(+)
>> 
>> diff --git a/runner/executor.c b/runner/executor.c
>> index 7e5fbe8f..69ef21e5 100644
>> --- a/runner/executor.c
>> +++ b/runner/executor.c
>> @@ -142,6 +142,7 @@ static const struct {
>>  	unsigned long bit;
>>  	const char *explanation;
>>  } abort_taints[] = {
>> +  {(1 << 4), "TAINT_MACHINE_CHECK: Processor reported a Machine Check Exception."},
>>    {(1 << 5), "TAINT_BAD_PAGE: Bad page reference or an unexpected page flags."},
>>    {(1 << 7), "TAINT_DIE: Kernel has died - BUG/OOPS."},
>>    {(1 << 9), "TAINT_WARN: WARN_ON has happened."},
>> -- 
>> 2.19.1
>> 
>> _______________________________________________
>> igt-dev mailing list
>> igt-dev@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/igt-dev
>
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-06-05 12:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-05 12:16 [igt-dev] [PATCH i-g-t] runner: Also consider TAINT_MACHINE_CHECK as abortable taint Petri Latvala
2019-06-05 12:36 ` Daniel Vetter
2019-06-05 12:47   ` Mika Kuoppala [this message]
2019-06-05 12:57     ` Petri Latvala
2019-06-05 12:53   ` Petri Latvala
2019-06-05 16:54     ` Daniel Vetter
2019-06-05 12:40 ` Mika Kuoppala
2019-06-05 13:02 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-06-06 19:21 ` [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=87zhmwqjuq.fsf@gaia.fi.intel.com \
    --to=mika.kuoppala@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --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