Date: Thu, 24 Nov 2005 10:48:50 +0100 From: Stefan Bethke <stb@lassitu.de> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm Message-ID: <0E77DBEA-B698-47D4-AEFC-AB78DB5EC255@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <stb@lassitu.de> Fon +49 170 346 0140
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0E77DBEA-B698-47D4-AEFC-AB78DB5EC255>