Date: Tue, 28 Sep 2004 22:00:23 +0200 From: Hannes Mehnert <hannes@mehnert.org> To: Ken Smith <kensmith@cse.Buffalo.EDU> Cc: sparc64@freebsd.org Subject: Re: panic: ipi_send: couldn't send ipi Message-ID: <20040928200022.GA27626@mehnert.org> In-Reply-To: <20040928153451.GB27640@electra.cse.Buffalo.EDU> References: <20040925070741.GA51297@xor.obsecurity.org> <20040927191430.GA718@electra.cse.Buffalo.EDU> <41591DD4.7000409@orel.ru> <20040928153451.GB27640@electra.cse.Buffalo.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On Tue, Sep 28, 2004 at 11:34:51AM -0400, Ken Smith wrote: > Unless someone thinks this would be a problem I'll wait another couple > of days and if nobody else has any further input I'll leave the existing > code as-is but bump the max retries to 5000 for the 5.3 release. I've patched my sun e450 with 2 * 300 MHz with your patch. So far no kernel messages about increasing max_ipi_retries. > I'm still curious about what the underlying problem is but it'll take some > time to track down I think. I did manage to find a machine to test > this on late yesterday and some initial attempts at triggering the > problem by generating a lot of disk I/O didn't seem to trigger it. I got it on a server running some jails after ~1 week uptime (until I used the patch attached to PR 66314). Best Regards, Hannes Mehnert -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBWcLRRcuNlziBjRwRAjKoAJwJUggt9pa5b+zR4RIl4pPx1fQF0wCguQuK blzlFrmlum5Qix6GH/Herfg= =GmcQ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040928200022.GA27626>