From owner-freebsd-stable@FreeBSD.ORG Mon Nov 29 13:49:42 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 0A45216A4CE for ; Mon, 29 Nov 2004 13:49:42 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AF5D43D31 for ; Mon, 29 Nov 2004 13:49:41 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iATDqoml001335; Mon, 29 Nov 2004 06:52:50 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41AB2901.1090102@freebsd.org> Date: Mon, 29 Nov 2004 06:49:53 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Aykut KARA References: In-Reply-To: X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: stable@freebsd.org 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 13:49:42 -0000 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