From owner-freebsd-stable@FreeBSD.ORG Mon Nov 29 13:35:39 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 9211516A4D0 for ; Mon, 29 Nov 2004 13:35:39 +0000 (GMT) Received: from ns.exe.com.tr (ns2.exe.com.tr [213.204.66.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B22043D60 for ; Mon, 29 Nov 2004 13:35:36 +0000 (GMT) (envelope-from akara@egemenbilgisayar.com.tr) Received: from [213.204.66.201] (account akara@egemenbilgisayar.com.tr HELO geek) by ns.exe.com.tr (CommuniGate Pro SMTP 4.2.6) with ESMTP id 1800966; Mon, 29 Nov 2004 15:35:09 +0200 From: "Aykut KARA" To: Date: Mon, 29 Nov 2004 15:35:16 +0200 Organization: EGEMEN Bilgisayar Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-reply-to: <41AABD07.2080808@alumni.rice.edu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTV2fBVV5gP3rDSTF2rDk1gOgk0wQAPR8Sw 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:35:39 -0000 > > 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