From owner-freebsd-current@FreeBSD.ORG Tue Oct 26 17:18:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8071916A4D0 for ; Tue, 26 Oct 2004 17:18:29 +0000 (GMT) Received: from duchess.speedfactory.net (duchess.speedfactory.net [66.23.201.84]) by mx1.FreeBSD.org (Postfix) with SMTP id B558643D5F for ; Tue, 26 Oct 2004 17:18:28 +0000 (GMT) (envelope-from ups@tree.com) Received: (qmail 13930 invoked by uid 89); 26 Oct 2004 17:18:26 -0000 Received: from duchess.speedfactory.net (66.23.201.84) by duchess.speedfactory.net with SMTP; 26 Oct 2004 17:18:26 -0000 Received: (qmail 13899 invoked by uid 89); 26 Oct 2004 17:18:25 -0000 Received: from unknown (HELO palm.tree.com) (66.23.216.49) by duchess.speedfactory.net with SMTP; 26 Oct 2004 17:18:25 -0000 Received: from [127.0.0.1] (localhost.tree.com [127.0.0.1]) by palm.tree.com (8.12.10/8.12.10) with ESMTP id i9QHIP5R052308; Tue, 26 Oct 2004 13:18:25 -0400 (EDT) (envelope-from ups@tree.com) From: Stephan Uphoff To: John Baldwin In-Reply-To: <200410211705.45147.jhb@FreeBSD.org> References: <20041020221659.33824.qmail@web21124.mail.yahoo.com> <1098320716.20390.416.camel@palm.tree.com> <200410211705.45147.jhb@FreeBSD.org> Content-Type: text/plain Message-Id: <1098811105.20390.16988.camel@palm.tree.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 26 Oct 2004 13:18:25 -0400 Content-Transfer-Encoding: 7bit cc: Nik Azim Azam cc: freebsd-current@FreeBSD.org Subject: Re: number of CPUs and IPI panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2004 17:18:29 -0000 On Thu, 2004-10-21 at 17:05, John Baldwin wrote: > On Wednesday 20 October 2004 09:05 pm, Stephan Uphoff wrote: > > Can you try the attached patch? > > ( Hope it still applies since it is a few weeks old) > > > > If this does not work I have a few more questions next week. > > Unfortunately it can enable interrupts with sched_lock held which can result > in deadlocks due to ithread preemption (IIRC, maybe not as badly with the > newer preemption code.) The code only enables interrupts for TLB shootdowns. In this case it is guaranteed that it holds the smp_ipi_mtx that as a side effect protects it against preemption and holds no other spin mutex. I don't see the problem. I am thinking about implementing the bitmap based stuff be talked about a few weeks ago to avoid having more than one queued IPI of the same type. > > > Stephan > > > > On Wed, 2004-10-20 at 18:16, Nik Azim Azam wrote: > > > sorry for not posting this information earlier. > > > > > > i'm running on SCHED_4BSD, with PREEMPTION. the same > > > panic occours without PREEMPTION. the kernel is > > > generic except that i've removed some devices that i > > > dont need. > > > > > > --- Gavin Atkinson > > > > > > wrote: > > > > On Wed, 20 Oct 2004, Nik Azim Azam wrote: > > > > > hello list, > > > > > > > > > > i'm doing some testing on a 6 cpu pentium II > > > > > > > > overdrive > > > > > > > > > computer with 6-CURRENT. with 6 cpus, the system > > > > > > > > will > > > > > > > > > panic easily with moderate load (previous IPI is > > > > > stuck). i edited sys/i386/sys/param.h file and > > > > > > > > lowered > > > > > > > > > the MAXCPU to 4. now the system is running with 4 > > > > > > > > cpus > > > > > > > > > and it survived a make buildworld + portupgrade at > > > > > > > > the > > > > > > > > > same time. > > > > > > > > > > is this a known problem? i can give more > > > > > > > > information > > > > > > > > > if anyone interested. > > > > > > > > Are you using SCHED_ULE? (I believe it's the default > > > > in 6-CURRENT...) > > > > > > > > If so, try with SCHED_4BSD. ULE has known problems > > > > at the moment. > > > > > > > > Gavin > > > > > > _______________________________ > > > Do you Yahoo!? > > > Declare Yourself - Register online to vote today! > > > http://vote.yahoo.com > > > _______________________________________________ > > > freebsd-current@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > > To unsubscribe, send any mail to > > > "freebsd-current-unsubscribe@freebsd.org"