From owner-freebsd-current@FreeBSD.ORG Sat Jan 21 13:39:03 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6259B1065673; Sat, 21 Jan 2012 13:39:03 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 7B10F8FC24; Sat, 21 Jan 2012 13:39:01 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA14361; Sat, 21 Jan 2012 15:39:00 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Rob9o-000JRL-Kc; Sat, 21 Jan 2012 15:39:00 +0200 Message-ID: <4F1ABFF3.9090305@FreeBSD.org> Date: Sat, 21 Jan 2012 15:38:59 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111222 Thunderbird/9.0 MIME-Version: 1.0 To: Gleb Smirnoff References: <20120117110242.GD12760@glebius.int.ru> <20120120154158.GD16676@FreeBSD.org> In-Reply-To: <20120120154158.GD16676@FreeBSD.org> X-Enigmail-Version: undefined Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org Subject: Re: new panic in cpu_reset() with WITNESS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2012 13:39:03 -0000 on 20/01/2012 17:41 Gleb Smirnoff said the following: > > On Tue, Jan 17, 2012 at 03:02:42PM +0400, Gleb Smirnoff wrote: > T> New panic has been introduced somewhere between > T> r229851 and r229932, that happens on shutdown if > T> kernel has WITNESS and doesn't have WITNESS_SKIPSPIN. > > I've run through binary search and panic was introduced > by r229854. > Which means that it was introduced by one of the earlier commits (probably mine). Thank you for this investigative work! Although, to be frank and honest, I still don't see how the problem could be a non-issue before. So any help/ideas/guesses are appreciated. P.S. I also have a big suspicion that we have more problems that can be triggered by WITNESS && !WITNESS_SKIPSPIN, but which are harmless in practice. -- Andriy Gapon