From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 09:48:49 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 B8B1016A41F for ; Thu, 24 Nov 2005 09:48:49 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 852A543D66 for ; Thu, 24 Nov 2005 09:48:48 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from [127.0.0.1] (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.3/8.12.9) with ESMTP id jAO9mlqS072511; Thu, 24 Nov 2005 10:48:47 +0100 (CET) (envelope-from stb@lassitu.de) In-Reply-To: <20051124093616.GA18522@xor.obsecurity.org> References: <002801c5f081$f01ff200$642a15ac@smiley> <4384F807.6050105@samsco.org> <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> <20051124062624.GA15944@xor.obsecurity.org> <858BF11C-E2B4-404B-B502-26AD49F5C962@lassitu.de> <20051124093616.GA18522@xor.obsecurity.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0E77DBEA-B698-47D4-AEFC-AB78DB5EC255@lassitu.de> Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Thu, 24 Nov 2005 10:48:50 +0100 To: Kris Kennaway X-Mailer: Apple Mail (2.746.2) Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 24 Nov 2005 09:48:49 -0000 Am 24.11.2005 um 10:36 schrieb Kris Kennaway: > On Thu, Nov 24, 2005 at 10:28:59AM +0100, Stefan Bethke wrote: >> >> Am 24.11.2005 um 07:26 schrieb Kris Kennaway: >> >>> On Thu, Nov 24, 2005 at 06:24:17AM +0100, Stefan Bethke wrote: >>>> Am 24.11.2005 um 00:15 schrieb Scott Long: >>>> >>>>> I've directly observed it on 7501WV2 and 7520BD2 boards. I don't >>>>> know if it's a problem that will affect other board configurations >>>>> or cousin chipsets like the 7505 and 7525. >>>> >>>> We've got a Tyan i7501 Pro that we have had stability issues with >>>> since the beginning. Is it thinkable that the interrupt masking >>>> could lead to a hard lock (no break to debugger possible)? >>> >>> Sounds like a different problem. Enable KDB_STOP_NMI in your >>> kernel, >>> which should let you break to DDB. >> >> Unfortunatly, no luck: can't break into the debugger with the option >> compiled into the kernel and debug.kdb.stop_cpus_with_nmi=1 set in >> loader.conf either. > > I've never encountered this..is it possible this hardware is faulty? Quite possible, although we've swapped everything except for the CPUs. We've got a replacement mainboard we'll try next. Stefan -- Stefan Bethke Fon +49 170 346 0140