From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Kirsher Subject: Re: [PATCH] e1000e: Taint a HW lockup Date: Wed, 06 Dec 2017 11:27:26 -0800 Message-ID: <1512588446.9469.0.camel@intel.com> References: <20171205180000.23637-1-chris@chris-wilson.co.uk> <151249715301.700.15883625561601294827@mail.alporthouse.com> Reply-To: jeffrey.t.kirsher@intel.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1757245330==" Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by gabe.freedesktop.org (Postfix) with ESMTPS id 640B6897BB for ; Wed, 6 Dec 2017 19:27:28 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Daniel Vetter , Chris Wilson , "Saarinen, Jani" , intel-wired-lan@lists.osuosl.org Cc: Tomi Sarvela , intel-gfx List-Id: intel-gfx@lists.freedesktop.org --===============1757245330== Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-fQsyq58RrXG715mg4O7a" --=-fQsyq58RrXG715mg4O7a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 2017-12-06 at 10:47 +0100, Daniel Vetter wrote: > On Tue, Dec 5, 2017 at 7:05 PM, Chris Wilson k> wrote: > > Quoting Chris Wilson (2017-12-05 18:00:00) > > > When we see an e1000e HW lockup in CI, it is typically fatal with > > > the > > > hang repeating until the host is forcibly rebooted. Speed up that > > > process by tainting the kernel, which CI can trivially detect > > > (and is > > > being used to detect similarly fatal CI conditions) and reboot > > > soon > > > after. > > >=20 > > > Signed-off-by: Chris Wilson > > > Cc: Daniel Vetter > > > Cc: Tomi Sarvela > >=20 > > I'm not concerned on selling this to e1000e, but if it helps > > improving > > CI robustness, then topic/core-for-CI. Or maybe we should create a > > new > > topic, Daniel? topic/taints-for-CI? >=20 > Sounds like a usable idea for CI. Would be especially interesting > because despite applying the suggested w/a, we still hit lockups. > Before we do that though I think we should get an ack from the e1000e > team. Jani S. maybe something you can driver? >=20 > Adding more folks to cc. > -Daniel Please send any e1000e patches to the intel-wired-lan mailing list and make sure to CC Sasha Neftin , since he is the e1000e driver maintainer. --=-fQsyq58RrXG715mg4O7a Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEiTyZWz+nnTrOJ1LZ5W/vlVpL7c4FAlooRJ4ACgkQ5W/vlVpL 7c5/Mw//VqYgrH7pTWauNf1Lg1XS9YqSFV7hNeAiDwvvfFWDUe5Ksl30uL3pzvtW XYRJtNCFEoC9YwphTG/3CXUKxnXBestRM/aohPcr64131QQ/4fNB4z0jGdP0byHL ODi/uyPa4rihGkrVvO4XTU/WU/kSHU+O0Hn8YTBTcfRAz7PNTzjd8N1LmTxAe9FM 3iDqofpq1ptrom4gj92BsBNkHmmp4rErhRjJTbObtHKZJZ1ZUMK51qYXNJdaX55w JK1I1vkelNRN+F7WYXev60ana8niU/T4TvrciN8P1bUMdEh4uhbAC20Ny0mejENP DXMAwW/XMETdSNGQUfZkUBKtwMkXvm3tG88kLDwrWFQQL0b329CDwt9sWS+NXQJ2 mEEHh6DT6J1jHkwtAqQxGlo3cBdsEJx6w0TQDYCWhqqnmFA93P5ctlfepf3nm6Ui 3vYG57Hv7LG9xjcQYbhXg8lPnr6RDlbyx3s+z7gLCzbI4PHY1PfSOUZxyZLK72/G xgX7JosxnO7C3f38BA1DDe3Z509CAlAOaEnY8b+Iu1eI7962W9BAPaLm8NsvW9JF 14QzR8mVcaYTi3ulK/70Ww+sJxg80HWfwrbdCJXXUMrkRxG/NV97YFL8gBP7m0LJ Nx25EVDAf0kYskJYRS+EfvocJhPeEjRyyKVbDxSC2xw/FGib95s= =Qbvc -----END PGP SIGNATURE----- --=-fQsyq58RrXG715mg4O7a-- --===============1757245330== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KSW50ZWwtZ2Z4 IG1haWxpbmcgbGlzdApJbnRlbC1nZnhAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vaW50ZWwtZ2Z4Cg== --===============1757245330==--