From: Petri Latvala <petri.latvala@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
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, 5 Jun 2019 15:53:54 +0300 [thread overview]
Message-ID: <20190605125354.GI22949@platvala-desk.ger.corp.intel.com> (raw)
In-Reply-To: <20190605123656.GT21222@phenom.ffwll.local>
On Wed, Jun 05, 2019 at 02:36:56PM +0200, Daniel Vetter wrote:
> 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".
>
> 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).
I've seen some MCE log messages on dmesgs, quite often on one of the
BXTs for example. How often those MCE triggers caused taint is another
question.
Reading the mce code, it seems to be thermal _failure_ that causes a
taint. And all of these add_taint() calls also use
LOCKDEP_NOW_UNRELIABLE so we're already deep under the bus if we get
that taint.
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-06-05 12:53 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
2019-06-05 12:57 ` Petri Latvala
2019-06-05 12:53 ` Petri Latvala [this message]
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=20190605125354.GI22949@platvala-desk.ger.corp.intel.com \
--to=petri.latvala@intel.com \
--cc=daniel@ffwll.ch \
--cc=igt-dev@lists.freedesktop.org \
/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