From owner-freebsd-current Wed Jun 2 13:58:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 792CE14F60; Wed, 2 Jun 1999 13:58:09 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id VAA08673; Wed, 2 Jun 1999 21:58:11 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Wed, 2 Jun 1999 21:58:11 +0100 (BST) From: Doug Rabson To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@freebsd.org, hackers@freebsd.org Subject: Re: Finding out what function an interrupt is tied to.. In-Reply-To: <199906021425.WAA02267@bandicoot.prth.tensor.pgs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Jun 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > I'm having some problems since when the newbus code went in, in that > my sound card doesn't seem to be interrupting anymore (PAS16, Voxware > drivers). So what I'd like to do is look at the kernel and see > if an interrupt actually has a function associated with it, and if > it's being masked out. Any ideas? Of course, this would have to happen > just as I learnt to rip my music CD's into mp3s. I suggest that you start by putting print statements (or using the kernel debugger) to find out what is going on in nexus_setup_intr() (i386/i386/nexus.c). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message