Date: Tue, 22 Jun 2004 17:22:44 -0400 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-current@FreeBSD.org Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: > panic: APIC: Previous IPI is stupcmka Message-ID: <200406221722.44505.jhb@FreeBSD.org> In-Reply-To: <20040622094338.GA12675@xor.obsecurity.org> References: <20040622044142.GA8571@xor.obsecurity.org> <20040622094338.GA12675@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 22 June 2004 05:43 am, Kris Kennaway wrote: > On Mon, Jun 21, 2004 at 09:41:42PM -0700, Kris Kennaway wrote: > > > panic: APIC: Previous IPI is stupcmka > > > u_clpauziydf i=x :0 ;s p > > > cnD efbourg g5e0r0(0"0p0a0n0i > > > ") > > > > I updated this smp machine -current tonight, played with mutex > > profiling a bit, and it died after an hour or so of package building > > load. It hung here. > > This happened again under similar circumstances (running a cvs update > with some network stuff going on). Similar interleaved panic message: > > _anic: APIC: Previous IPI is stpumcakp > nlcapzuyifdi x=: 0s;p u > i Dfeobru g5g0e0r0(0"0p0a0n > c") Seems the two CPUs are deadlocked waiting on each other. The first sent a pmap_lazyfixup IPI to the second but the second has interrupts disabled as it is trying to send an IPI as well. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200406221722.44505.jhb>