From owner-freebsd-current@FreeBSD.ORG Thu Aug 26 20:48:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 608CD16A4CE for ; Thu, 26 Aug 2004 20:48:15 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FBED43D2F for ; Thu, 26 Aug 2004 20:48:15 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 398997A3D2; Thu, 26 Aug 2004 13:48:15 -0700 (PDT) Message-ID: <412E4C8E.7000108@elischer.org> Date: Thu, 26 Aug 2004 13:48:14 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Daniel Eriksson References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: PLEASE TEST: IPI deadlock avoidance patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Thu, 26 Aug 2004 20:48:15 -0000 heh.. My partial diagnosis is that there is another SMP related problem that you can not tickle without the IPI patch, because you can not stay up long enough.. Looking at the IPI patch, it is almost impossible to imagine a scenario where it itself could cause data corruption. Daniel Eriksson wrote: >Julian Elischer wrote: > > > >>and if you remove the IPI patch? >> >> > >Then the machine reliably hang under load. > >/Daniel Eriksson > > >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > >