Date: Thu, 03 May 2001 09:50:43 -0700 (PDT) From: John Baldwin <jhb@FreeBSD.org> To: Warner Losh <imp@harmony.village.org> Cc: kevind@ikadega.com, hackers@FreeBSD.org, Kevin Day <toasty@temphost.dragondata.com> Subject: Re: NMI during procfs mem reads (#2) Message-ID: <XFMail.010503095043.jhb@FreeBSD.org> In-Reply-To: <200105031611.f43GB0b64926@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03-May-01 Warner Losh wrote: > 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. Correction, with a spin lock held. It may try to acquire Giant (not sure _why_ it acquires Giant) and then it pukes. Getting a traceback would be most helpful. :) Also, the output of 'show locks' from ddb could help, too. -- John Baldwin <jhb@FreeBSD.org> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ 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?XFMail.010503095043.jhb>