Date: Mon, 27 Sep 2004 17:55:11 -0400 From: Brian Fundakowski Feldman <green@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: panic: APIC: Previous IPI is stuck Message-ID: <20040927215511.GC24003@green.homeunix.org> In-Reply-To: <200409271635.44017.jhb@FreeBSD.org> References: <20040924230425.GB1164@green.homeunix.org> <20040925101021.A78979@bpgate.speednet.com.au> <200409271635.44017.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. \,,,,,,,,,,,,,,,,,,,,,,\
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040927215511.GC24003>