panic: ipi_send: couldn't send ipi

[Andrew Belashov]

Ken Smith wrote:
> Would someone(s) who have been having this problem mind trying
> the following patch?  I'm a bit nervous about just "blindly"
> raising the IPI_RETRIES constant to something huge, I would
> like to try and track this down a bit to find out a bit more
> about what's going on.
> 
> This patch is a bit weird, but it should report on the console
> when it finds a need to bump the number of retries (and it's
> starting off with a higher default number than before - the
> PR that someone cited reported test numbers in the 2000 range
> with that test patch).  If you find that it stops the panic's
> I'm interested in finding what it winds up bumping the loop
> counter to, and if anyone knows what sort of activity triggers
> the delays in the ipi delivery I'm interested...
> 
> I've compile-tested this but I'm afraid I sorta loaned my test
> MP machines to someone for a while so I can't try to exercise
> this here at the moment.  :-(

I have install this patch.

Hardware: Sun Ultra 60 Creator 3D, 2 x UltraSparc IIi @ 450 MHz, 1 GB memory.

OS: FreeBSD bel.localdomain 5.2-CURRENT FreeBSD 5.2-CURRENT #32:
Tue Sep 28 11:14:38 MSD 2004
bel at bel.localdomain:/usr/obj/usr/src/sys/SUNC3D  sparc64

Messages from console:

cpu_ipi_send: raised ipi_retries_max to 2000
cpu_ipi_send: raised ipi_retries_max to 3000