From owner-freebsd-sparc64@FreeBSD.ORG Tue Sep 28 20:00:29 2004 Return-Path: Delivered-To: freebsd-sparc64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A51B16A4CF for ; Tue, 28 Sep 2004 20:00:29 +0000 (GMT) Received: from beagle2.mehnert.org (beagle2.mehnert.org [212.42.235.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4107743D49 for ; Tue, 28 Sep 2004 20:00:28 +0000 (GMT) (envelope-from hannes@mehnert.org) Received: from localhost (port-212-202-198-15.dynamic.qsc.de [212.202.198.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Hannes Mehnert", Issuer "mehnert root CA" (verified OK)) by beagle2.mehnert.org (Postfix) with ESMTP id 090899585D; Tue, 28 Sep 2004 22:00:25 +0200 (CEST) Date: Tue, 28 Sep 2004 22:00:23 +0200 From: Hannes Mehnert To: Ken Smith Message-ID: <20040928200022.GA27626@mehnert.org> References: <20040925070741.GA51297@xor.obsecurity.org> <20040927191430.GA718@electra.cse.Buffalo.EDU> <41591DD4.7000409@orel.ru> <20040928153451.GB27640@electra.cse.Buffalo.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040928153451.GB27640@electra.cse.Buffalo.EDU> User-Agent: Mutt/1.4.2.1i cc: sparc64@freebsd.org Subject: Re: panic: ipi_send: couldn't send ipi X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Sep 2004 20:00:29 -0000 -----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-----