Date: Thu, 03 May 2001 10:11:00 -0600 From: Warner Losh <imp@harmony.village.org> To: Kevin Day <toasty@temphost.dragondata.com> Cc: hackers@FreeBSD.ORG, kevind@ikadega.com Subject: Re: NMI during procfs mem reads (#2) Message-ID: <200105031611.f43GB0b64926@harmony.village.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105031611.f43GB0b64926>