From owner-freebsd-sparc64@FreeBSD.ORG Wed Sep 29 07:55:47 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 87FFA16A4CE; Wed, 29 Sep 2004 07:55:47 +0000 (GMT) Received: from tts.orel.ru (tts.orel.ru [213.59.64.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE14743D55; Wed, 29 Sep 2004 07:55:46 +0000 (GMT) (envelope-from bel@orel.ru) Received: from orel.ru (lg.orel.ru [62.33.11.59]) by tts.orel.ru (8.12.10/8.12.10/bel) with ESMTP id i8T7tdBm001724; Wed, 29 Sep 2004 11:55:41 +0400 Message-ID: <415A6A7A.3070601@orel.ru> Date: Wed, 29 Sep 2004 11:55:38 +0400 From: Andrew Belashov Organization: ORIS User-Agent: Mozilla/5.0 (X11; U; FreeBSD sparc64; en-US; rv:1.6) Gecko/20040407 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20040925070741.GA51297@xor.obsecurity.org> <20040927191430.GA718@electra.cse.Buffalo.EDU> <41591DD4.7000409@orel.ru> <20040928153451.GB27640@electra.cse.Buffalo.EDU> <20040928165449.GA3605@xor.obsecurity.org> In-Reply-To: <20040928165449.GA3605@xor.obsecurity.org> X-Enigmail-Version: 0.83.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Zombi-Check: on netra2.orel.ru cc: Ken Smith cc: jhb@freeBSD.org 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: Wed, 29 Sep 2004 07:55:47 -0000 Kris Kennaway wrote: >>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? > > > I don't remember if any of those were SMP, but this was on phk's dual > u60. I applied the patch in PR 66314, and while I haven't had a > repeat of the ipi panic, it did fall over with one of the other panics > I regularly see on this machine. Also, jhb seemed to think there was > an underlying MI problem, and this patch would only delay the > occurence of the panic. > > Kris The problem does not arise in the following cases: kernel build without SMP option; kernel running on uniprocessor machine (with or without SMP option). The problem is somehow related to Creator 3D. To reproduce problem I use any program, that generate large output. For example: "ls -laR /" Andrew