From owner-freebsd-current@FreeBSD.ORG Mon Sep 27 21:55:18 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 E8A0716A4CF; Mon, 27 Sep 2004 21:55:18 +0000 (GMT) Received: from green.homeunix.org (pcp04368961pcs.nrockv01.md.comcast.net [69.140.212.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66E2043D2F; Mon, 27 Sep 2004 21:55:18 +0000 (GMT) (envelope-from green@green.homeunix.org) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.1/8.13.1) with ESMTP id i8RLtCsT026425; Mon, 27 Sep 2004 17:55:12 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.1/8.13.1/Submit) id i8RLtB3B026424; Mon, 27 Sep 2004 17:55:11 -0400 (EDT) (envelope-from green) Date: Mon, 27 Sep 2004 17:55:11 -0400 From: Brian Fundakowski Feldman To: John Baldwin Message-ID: <20040927215511.GC24003@green.homeunix.org> References: <20040924230425.GB1164@green.homeunix.org> <20040925101021.A78979@bpgate.speednet.com.au> <200409271635.44017.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200409271635.44017.jhb@FreeBSD.org> User-Agent: Mutt/1.5.6i cc: Andy Farkas cc: freebsd-current@FreeBSD.org cc: current@FreeBSD.org Subject: Re: panic: APIC: Previous IPI is stuck 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: Mon, 27 Sep 2004 21:55:19 -0000 On Mon, Sep 27, 2004 at 04:35:44PM -0400, John Baldwin wrote: > On Friday 24 September 2004 08:24 pm, Andy Farkas wrote: > > I have been having this problem for a few weeks now. Glad I'm not the only > > one. My box is a 4xPPro running 5.3-BETA5. It panics with either ULE > > or 4BSD. > > > > My theory is that a physical IPI gets lost somewhere and the kerenl spins > > waiting for it. But thats just a stab in the dark because nobody cares to > > explain why IPI's would be stuck. > > The panic has to do with a previous IPI not finished being sent from the same > CPU. I've yet to determine why this happens. You can try editing > sys/i386/i386/local_apic.c and turning on 'DETECT_DEADLOCK' (I think it is > just commented out) and seeing if that improves stability. I also see this > on a 4xPIIXeon system I use for testing. Can KTR logging be leveraged to find the root cause(s) of these deadlocks, or is it just so wildly unpredictable that it would be of no use? -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\