Date: Wed, 04 Dec 2002 17:29:33 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-smp@freebsd.org, Michael Richards <michael@fastmail.ca> Subject: Re: Intel SE7500CW2 narrowed down... Message-ID: <3DEEABFD.A40A735E@mindspring.com> References: <XFMail.20021204152439.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > Terry. We are having problems sending _interprocess_interrupts_. > IPI's do _not_ go through the IO APIC. They are sent from one > local APIC over to another local APIC. The problems we are seeing > have nothing to do with I/O interrupts. The box runs fine with one > processor and using the I/O APIC if you ignore the failure of the > AP to respond to the startup IPI. This is the "ServerwWorks related lockup", not the "Second processor does not start, and so does not grab Giant, so system does not lock up" thing, right? The easy way to prove your thesis is to send a broadcast IPI. You only have 2 CPUs in that box, anyway. If it starts working then you are right. I think the serverworks chipset can only run in 2 of the 4 modes, at least as programmed by the BIOS, and goes off in the weeds, otherwise (the first thing an AP does is grab giant, which means it tries to grab the interrupts, as a side effect). It may be that the chipset is plain busted. Note that one of the OS's that works doesn't run in APIC I/O mode at all, and the other OS that works runs in virtual wire mode. Other than tonight, I won't be able to engage in a deep discussion on this for about a week, I think, so get your shots in now. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DEEABFD.A40A735E>