From owner-freebsd-hackers Thu May 3 9:11:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 6C16F37B424 for ; Thu, 3 May 2001 09:11:06 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.11.3/8.11.1) with ESMTP id f43GB0b64926; Thu, 3 May 2001 10:11:01 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200105031611.f43GB0b64926@harmony.village.org> To: Kevin Day Subject: Re: NMI during procfs mem reads (#2) Cc: hackers@FreeBSD.ORG, kevind@ikadega.com In-reply-to: Your message of "Thu, 03 May 2001 10:51:32 CDT." <200105031551.KAA74358@temphost.dragondata.com> References: <200105031551.KAA74358@temphost.dragondata.com> Date: Thu, 03 May 2001 10:11:00 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200105031551.KAA74358@temphost.dragondata.com> Kevin Day writes: : The PCI target itself isn't doing anything like that, but it's possible that : the PCI-PCI bridge we're going through might be. In any case, getting the : NMI isn't really all that bad, it's stopping the chipset from getting hung : on a infinite retry. My only concern is the NMI handler while in the kernel : may be too aggressive in causing a panic. Yes. The NMI handler is a little too agressive about panicing. Also, current has problems where sometimes it will panic when the nmi happens with GIANT held. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message