From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 20:49:29 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 C548A16A4CE for ; Tue, 16 Nov 2004 20:49:29 +0000 (GMT) Received: from web54606.mail.yahoo.com (web54606.mail.yahoo.com [68.142.225.190]) by mx1.FreeBSD.org (Postfix) with SMTP id 585CE43D69 for ; Tue, 16 Nov 2004 20:49:29 +0000 (GMT) (envelope-from nskyline_r35@yahoo.com) Received: (qmail 61311 invoked by uid 60001); 16 Nov 2004 20:49:28 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=cf/e9QbmLmYRHXZ1opU4w7pftaMoN3jRGQjF0C5SyTx7EopPVvSvspYuzVPfehrP6OPgVRpcpOYtoZ9nSC6U60Y+nEaougbRyfN3iFR3Maw+MyF6KrwAXP+PAbxiVuXsJlay8dQ0ZWe4tSvcBeRtxPtkHUTvtyJMmpbKInufLfM= ; Message-ID: <20041116204928.61309.qmail@web54606.mail.yahoo.com> Received: from [82.44.96.53] by web54606.mail.yahoo.com via HTTP; Tue, 16 Nov 2004 12:49:28 PST Date: Tue, 16 Nov 2004 12:49:28 -0800 (PST) From: Nik Azim Azam To: Stephan Uphoff , Doug White In-Reply-To: <1100617025.2456.27.camel@palm.tree.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: "Ketrien I. Saihr-Kesenchedra" cc: freebsd-current@freebsd.org Subject: Re: number of CPUs and IPI panic 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: Tue, 16 Nov 2004 20:49:29 -0000 my box survived a make buildworld with the patch. without the patch, it will crash after 20-30 mins. i will test the patch further. good work, Stephan. thanks, nik. --- Stephan Uphoff wrote: > On Mon, 2004-11-15 at 22:10, Doug White wrote: > > On Fri, 12 Nov 2004, Stephan Uphoff wrote: > > > > > On Fri, 2004-11-12 at 09:19, Nik Azim Azam > wrote: > > > > Win2K Advanced Server works just fine here. > > > > > > The root cause seems to be a misunderstanding of > the interrupt delivery > > > and buffering mechanism. The fix may take a few > days since it probably > > > requires extensive changes to the IPI layer. > > > > [getting in late on this] > > > > Tomorrow I will have access to a Dell PowerEdge > 6500 (4x500MHz) I can use > > to capture info or test patches. Or see if the bug > reproduces there in the > > first place :) > > > > rwatson mumbled something about wanting to > determine what triggered the > > prior IPI that the panic later trips over. I'll > have to find a sutiable > > place to hide that information... > > Hopefully we can skip the debugging phase and go > directly to the testing > phase. However it would be helpful to know if the > PowerEdge 6500 > encounters any problems without the patch. > > The feedback I have received so far looks promising: > > Andy Farkas wrote: > >> You can download the patch at: > >> http://people.freebsd.org/~ups/ipi4_patch > >> > >> Any feedback is appreciated. > >> > >> Stephan > >> > > I have been hammering the box for the last 4 hours > without > > a panic. > > > > Without your patch, I could easily get a panic by > boot -s then > > fsck. I did this twice (without panic) using your > patch. > > > > Without your patch, I would usually get a panic > during make > > buildworld -j4. So far with your patch its already > done a > > buildworld -j8, and its about to finish a > buildworld -j4. > > (2 buildworld in a row) > > > > This is good indeed. > > > > -andyf > > > > ps. ok to post to list. > > > __________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com