From owner-freebsd-hackers Thu May 3 9:53:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id D1A1E37B43F for ; Thu, 3 May 2001 09:53:19 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f43GpSG71881; Thu, 3 May 2001 09:51:28 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200105031611.f43GB0b64926@harmony.village.org> Date: Thu, 03 May 2001 09:50:43 -0700 (PDT) From: John Baldwin To: Warner Losh Subject: Re: NMI during procfs mem reads (#2) Cc: kevind@ikadega.com, hackers@FreeBSD.org, Kevin Day Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 -- 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