Date: Fri, 03 Dec 1999 19:02:14 -0600 From: Chris Csanady <cc@137.org> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: FreeBSD-current <FreeBSD-current@FreeBSD.ORG> Subject: Re: incorrect irqs with pci devices Message-ID: <38486816.E224F87C@ameslab.gov> References: <Pine.BSF.4.10.9912030952510.23924-100000@salmon.nlsystems.com> <XFMail.991203095543.spock@techfour.net> <199912031656.LAA08053@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Wollman wrote:
>
> <<On Fri, 03 Dec 1999 09:55:43 -0500 (EST), Mike Heffner <spock@techfour.net> said:
>
> > Yes, it is a SMP box, and yes, the devices work fine. I just thought it was odd
> > that the kernel would report incorrect ones.
>
> They are not incorrect. SMP uses a different interrupt system.
They are on my box, where incorrect is defined as the interrupts not reaching
their
supposed destination. I would really like to fix this, but I don't know enough
about exactly what is wrong. Any ideas would really be appreciated, as I would
like to remove my disgusting hack. :)
I have an AMI raid controller that the system reports that it is on irq 11. The
problem is that the interrupts actually go to irq 17. If I hard wire them with
*** pci.c.old Mon Nov 29 19:34:46 1999
--- pci.c Thu Dec 2 17:48:42 1999
***************
*** 347,352 ****
--- 347,356 ----
}
}
}
+ if (cfg->intline == 11) {
+ printf("apic_io: incorrect int 11 -> 17\n");
+ cfg->intline = 17;
+ }
#endif /* APIC_IO */
cfg->mingnt = pci_cfgread(cfg, PCIR_MINGNT, 1);
...everything works fine. I believe the problem has something to do with the
fact that it is a bridged card, but I'm not sure how things should work.
Any thoughts?
Chris
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38486816.E224F87C>