From owner-freebsd-sparc64@FreeBSD.ORG Tue Sep 28 15:34:55 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 C86AE16A4CE for ; Tue, 28 Sep 2004 15:34:55 +0000 (GMT) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D23343D46 for ; Tue, 28 Sep 2004 15:34:55 +0000 (GMT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (localhost [127.0.0.1]) i8SFYrTH029909; Tue, 28 Sep 2004 11:34:53 -0400 (EDT) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i8SFYqVx029907; Tue, 28 Sep 2004 11:34:52 -0400 (EDT) Date: Tue, 28 Sep 2004 11:34:51 -0400 From: Ken Smith To: Andrew Belashov Message-ID: <20040928153451.GB27640@electra.cse.Buffalo.EDU> References: <20040925070741.GA51297@xor.obsecurity.org> <20040927191430.GA718@electra.cse.Buffalo.EDU> <41591DD4.7000409@orel.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41591DD4.7000409@orel.ru> User-Agent: Mutt/1.4.1i cc: Kris Kennaway cc: Ken Smith 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 15:34:55 -0000 On Tue, Sep 28, 2004 at 12:16:20PM +0400, Andrew Belashov wrote: > 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@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 Thank you very much for testing this out. 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'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. Your case seems to be a bit extreme - I'm wondering if it has something to do with the Creator 3D. I don't think it is the only thing that can cause the problem to crop up but it might be something that makes the situation "worse". Kris, was your problem machine one of the machines here? Both of them at least have Creator 3D's in them though how much they'd be touched depends on what your kernel config says. I know you're using the serial consoles but I suppose it's possible there is still some sort of "interference" the Creator 3D's could have given the machine might vaguely touch them at boot time. -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |