From owner-freebsd-drivers@FreeBSD.ORG Thu Feb 9 16:03:26 2006 Return-Path: X-Original-To: freebsd-drivers@freebsd.org Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C585D16A420 for ; Thu, 9 Feb 2006 16:03:26 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id E18D643D46 for ; Thu, 9 Feb 2006 16:03:25 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 8093746 for multiple; Thu, 09 Feb 2006 11:02:38 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k19G3NQt067979; Thu, 9 Feb 2006 11:03:23 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-drivers@freebsd.org Date: Thu, 9 Feb 2006 10:17:52 -0500 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200602091017.53802.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1281/Wed Feb 8 14:59:33 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: Kernel Event Help in Tracing. (NMI ISA 30, EISA ff) X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Feb 2006 16:03:26 -0000 On Wednesday 08 February 2006 11:38, Mark Ackroyd wrote: > Hiya, > > I have FreeBSD 6 installed on a server Dell PE750 that used for IVR, it > has Asterisk installed, Including the latest version of Zaptel for the > Digium card. When the driver actually starts doing any work, it kicks out > loads and loads of kernel syslog messages containing just "NMI ISA 30, > EISA ff", there is another guy on the Asterisk-BSD mailing list that has > this problem, but no-one is any the wiser on it. I have been sat going > through the source code for the Zaptel driver all afternoon, and I don't > think the message is coming from there. Anyone seen this before or point > to the right place in the Kernel where these messages could be generating > from. > > it only starts to do it, when the E1 line starts putting down traffic, > loading unloading and general init, it doesn't do it. > > Anyone got any thoughts on this? The message is from the isa_nmi() function in sys/i386/isa/nmi.c. What is happening is that yuor machine is raising an NMI (normally used to indicate hardware errors like ECC failures, etc.). Perhaps the card is asserting PERR# or SERR#? I'm not sure if those would trigger an NMI or not though, it might depend on the chipset. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org