From owner-freebsd-sparc64@FreeBSD.ORG Wed Sep 29 17:15:18 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 B84C016A4CE; Wed, 29 Sep 2004 17:15:18 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8891943D46; Wed, 29 Sep 2004 17:15:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7BF0B51262; Wed, 29 Sep 2004 10:15:40 -0700 (PDT) Date: Wed, 29 Sep 2004 10:15:40 -0700 From: Kris Kennaway To: Andrew Belashov Message-ID: <20040929171540.GA12366@xor.obsecurity.org> 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> <415A6A7A.3070601@orel.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline In-Reply-To: <415A6A7A.3070601@orel.ru> User-Agent: Mutt/1.4.2.1i cc: sparc64@freeBSD.org cc: Ken Smith cc: jhb@freeBSD.org cc: Kris Kennaway 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 17:15:18 -0000 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 29, 2004 at 11:55:38AM +0400, Andrew Belashov wrote: > 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 >=20 > The problem does not arise in the following cases: > kernel build without SMP option; > kernel running on uniprocessor machine (with or without SMP option). Well, Inter-Processor Interrupts do only occur when you are using multiple processors ;-) > The problem is somehow related to Creator 3D. I don't use the console much on the machine where I get the panic (and I don't have syscons or the creator driver compiled in), so all it receives is the output of syslogd via the ofw console. > To reproduce problem I use any program, that generate large output. > For example: "ls -laR /" Kris --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBWu28Wry0BWjoQKURAiO4AKD+msFChhrhGTjKVA3yC8TQIqUnIwCghYaG 02bcnT2CBvu7SDJQsxFiKU0= =qOPk -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi--