Date: Fri, 06 Jun 2003 11:45:48 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: dmlb@dmlb.org Cc: freebsd-hackers@freebsd.org Subject: Re: interrupt handlers in -current Message-ID: <20030606.114548.66168059.imp@bsdimp.com> In-Reply-To: <XFMail.20030606182456.dmlb@dmlb.org> References: <20030605.170134.132933173.imp@bsdimp.com> <XFMail.20030606182456.dmlb@dmlb.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <XFMail.20030606182456.dmlb@dmlb.org>
Duncan Barclay <dmlb@dmlb.org> writes:
:
: On 05-Jun-2003 M. Warner Losh wrote:
: > In message: <XFMail.20030605220236.dmlb@dmlb.org>
: > Duncan Barclay <dmlb@dmlb.org> writes:
: >
: > It may also be the case that the interrupt for this isn't being
: > properly routed. 5.1-BETA has a bug that, for some laptop machines,
: > interrupts aren't properly routed. 5.1-RELEASE has fixed this.
:
: I think that this must be it. I had the blindingly obvious idea of looking
: at the chips interrupt mask in the watchdog (which is getting called). The
: chip has posted a TX complete interrupt. The kernel hasn't done anything
: with it so I assume it isn't routed.
:
: Until I get back from travelling and can install 5.1R, this at least gives me a
: hook to continue driver development - fairly icky though using the
: watchdog to trigger the interrupt handler!
If you have sources, you can rebuild a kernel. Remove the ifdef
__ia64__ from pci.c near line 815.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030606.114548.66168059.imp>