From owner-freebsd-stable@FreeBSD.ORG Mon Nov 29 17:05:46 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF9A116A4CE for ; Mon, 29 Nov 2004 17:05:46 +0000 (GMT) Received: from duchess.speedfactory.net (duchess.speedfactory.net [66.23.201.84]) by mx1.FreeBSD.org (Postfix) with SMTP id 02BA843D39 for ; Mon, 29 Nov 2004 17:05:46 +0000 (GMT) (envelope-from ups@tree.com) Received: (qmail 18394 invoked by uid 89); 29 Nov 2004 17:05:39 -0000 Received: from duchess.speedfactory.net (66.23.201.84) by duchess.speedfactory.net with SMTP; 29 Nov 2004 17:05:39 -0000 Received: (qmail 32554 invoked by uid 89); 29 Nov 2004 16:59:24 -0000 Received: from unknown (HELO palm.tree.com) (66.23.216.49) by duchess.speedfactory.net with SMTP; 29 Nov 2004 16:59:24 -0000 Received: from [127.0.0.1] (localhost.tree.com [127.0.0.1]) by palm.tree.com (8.12.10/8.12.10) with ESMTP id iATGxO9k022041; Mon, 29 Nov 2004 11:59:24 -0500 (EST) (envelope-from ups@tree.com) From: Stephan Uphoff To: Scott Long In-Reply-To: <41AB2901.1090102@freebsd.org> References: <41AB2901.1090102@freebsd.org> Content-Type: text/plain Message-Id: <1101747564.11465.2867.camel@palm.tree.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 29 Nov 2004 11:59:24 -0500 Content-Transfer-Encoding: 7bit cc: stable@freebsd.org cc: Aykut KARA Subject: Re: SMP support problem - panic: APIC: Previous IPI is stuck X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 17:05:47 -0000 On Mon, 2004-11-29 at 08:49, Scott Long wrote: > Aykut KARA wrote: > >>>We are using FreeBSD 5.3R on our quad(4) cpu server. Our problem is, > >>>which I mentioned in subject line, "panic: APIC: Previous IPI is > >>>stuck". When server gives such an error, it stops responding ... > >>> > >>>I have searched all mailing lists but I can not find a solution except > >>>disabling SMP support in kernel which can not handle the traffic. What > >>>can be done in this situation? I will be pleased for your advises... > > > > > >>You sure you searched the mailing lists? ;-) > > > > > >>Stephan Uphoff produced a patch that might fix it and posted to current@ > > > > about it 2 weeks ago: > > > > http://lists.freebsd.org/pipermail/freebsd-current/2004-November/043156.html > > > > > >>Jon > > > > > > Yes i have already read this but it says that: > > > > "The patch is a proof of concept and therefore not optimized". > > > > How can i try such a patch on o working remote high priority server? > > Furthermore, there is no information in the main FreeBSD site about this > > patch. I just want to learn that is there any way that guarantees to fix > > this error? > > > > AyKuT > > > > The patch represents work that is ongoing to fix the problem. You can > either help with that process by trying that patch, or wait patiently > until someone else tries the patch for you and declares it good. There > is no information on the FreeBSD website about this patch because, well, > it's a work in progress. And there are no guarantees anywhere that > any of this will work at all for you. We even specify that clearly in > our license =-) > > Scott Hi, I just posed a new patch on current. http://lists.freebsd.org/pipermail/freebsd-current/2004-November/043697.html The last fix seems to have worked for all testers and this is the promised optimized version. I am highly confident that this will be the final solution but need feedback from testers as I can not reproduce the problem locally. Stephan