Date: Tue, 2 Apr 2002 16:03:20 -0500 (EST) From: Kenneth Culver <culverk@alpha.yumyumyum.org> To: Coleman Kane <cokane@FreeBSD.ORG> Cc: FreeBSD-smp <smp@FreeBSD.ORG>, FreeBSD-stable <stable@FreeBSD.ORG>, Chris <crisc@vmunix.com> Subject: Re: Interrupt delivery on SMP 760MPX board 4.5-R/4-S Message-ID: <20020402160203.K47643-100000@alpha.yumyumyum.org> In-Reply-To: <20020402145540.A14822@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> I believe it has something to do with the APIC on this board. I have a > production Dual PIII VIA server running 4.2 to compare to and I noticed a > few things: > 1) This Dual Athlon machine is still routing 16 INT's in ICU-fashion > 2) The ExtINT pin on the PIII system, in local INTs, is routed via a > PCI bus, but the Athlon System routs this via the ISA bus. I think > this is wrong. > 3) Furthermore, all INTs are routed in ISA-fashion and the Bus in mptable > is ISA (except NMI). There are no PCI routing pins listed at all (A-D). > 4) The 5.0-CURRENT dmesg/mptable dump from the GUINNESS reference board > also displays this behavior, which makes me think that it perhaps doesn't > completely work, a bridged PCI card like my DFE-570TX might be worth a try. > > Ideally, from what I can see, PCI devices that are attached via > IntA,B,C,D,etc.. and handled by the I/O APIC instead of the 8259's should > be running off irq's > 15. They should also have PCI bus attachments for > INTs listed in mptable. This is probably worth looking into, I grazed over > the MP 1.4 spec, as well as some AMD tech docs. It would appear that for > some reason, the INT is routed, but the OS doesn't set up the APIC properly, > or maybe this is expected to be the job of the BIOS... Either way, it > seems as if the Dual Athlon boards (at least ones I've seen) do not fully > work yet. > Even with all that said, my Dual Proc PII 333, based on an intel mobo, does not work right with FreeBSD 4.5, and broke in between 4.4 and 4.5. It works but does not support the dual channel card. I don't know what caused this but I do know this is the behavior I'm seeing. :-) Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020402160203.K47643-100000>