From owner-svn-src-head@freebsd.org Fri Feb 24 20:19:27 2017 Return-Path: Delivered-To: svn-src-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B81EACEC99B; Fri, 24 Feb 2017 20:19:27 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from mail.strugglingcoder.info (strugglingcoder.info [104.236.146.68]) by mx1.freebsd.org (Postfix) with ESMTP id A2ED11BA8; Fri, 24 Feb 2017 20:19:27 +0000 (UTC) (envelope-from hiren@strugglingcoder.info) Received: from localhost (unknown [10.1.1.3]) (Authenticated sender: hiren@strugglingcoder.info) by mail.strugglingcoder.info (Postfix) with ESMTPA id 7BF9A179B3; Fri, 24 Feb 2017 12:19:22 -0800 (PST) Date: Fri, 24 Feb 2017 12:19:22 -0800 From: hiren panchasara To: "Jonathan T. Looney" Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r314216 - head/sys/x86/x86 Message-ID: <20170224201922.GA18343@strugglingcoder.info> References: <201702241856.v1OIu150004903@repo.freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3" Content-Disposition: inline In-Reply-To: <201702241856.v1OIu150004903@repo.freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Feb 2017 20:19:27 -0000 --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 02/24/17 at 06:56P, Jonathan T. Looney wrote: > Author: jtl > Date: Fri Feb 24 18:56:00 2017 > New Revision: 314216 > URL: https://svnweb.freebsd.org/changeset/base/314216 >=20 > Log: > We have seen several cases recently where we appear to get a double-fau= lt: > We have an original panic. Then, instead of writing the core to the dump > device, the kernel has a second panic: "smp_targeted_tlb_shootdown: > interrupts disabled". This change is an attempt to fix that second pani= c. > =20 > When the other CPUs are stopped, we can't notify them of the TLB shootd= own, > so we skip that operation. However, when the CPUs come back up, we > invalidate the TLB to ensure they correctly observe any changes to the > page mappings. > =20 > Reviewed by: kib > Sponsored by: Netflix > Differential Revision: https://reviews.freebsd.org/D9786 Can this be MFCd to 11? Cheers, Hiren --r5Pyd7+fXNt84Ff3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAABCgBmBQJYsJVHXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBNEUyMEZBMUQ4Nzg4RjNGMTdFNjZGMDI4 QjkyNTBFMTU2M0VERkU1AAoJEIuSUOFWPt/lBv0IAJ18WZy81Zg3cD1Fp4OSh94r Jg+3AAhn8jmRkss6GAXbZQTzviifzLNvKz554+7jdxdL9uBRBMWlStj3KFByO5KV 5kQH8ynpw1BrUh0Ajovhsb1UhyyoMuWisXnTMbLMvDah/ytxOgkAO0fl/n2xGT5G gafmL3zU4+nPDqIyWbPgrssvG/vUZQDkAjemgpVWj8eJzYie7vLAWGs5D4RstJsE K3f+CXQSPPnedSWEpf/cUzRqRZW5cVdyxuFW2fILFDD7N+0cCdmgLA2gljEbj/ww 4eeimJI9ie8WBdo6l2yq+8UKukyJG4Tx2vzsyHUgx49Z6fcFomeL1HujhP72p+w= =9L9k -----END PGP SIGNATURE----- --r5Pyd7+fXNt84Ff3--