Date: Wed, 04 Dec 2002 15:24:39 -0500 (EST) From: John Baldwin <jhb@FreeBSD.org> To: tlambert2@mindspring.com Cc: freebsd-smp@freebsd.org, Michael Richards <michael@fastmail.ca> Subject: Re: Intel SE7500CW2 narrowed down... Message-ID: <XFMail.20021204152439.jhb@FreeBSD.org> In-Reply-To: <3DEE5F37.000003.43942@ns.interchange.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04-Dec-2002 Michael Richards wrote: >>> I'm not convinced it's a tables problem as I read the spec and >>> verified the CPU entries in this table byte for byte. It appears >>> valid. Besides, Linux works and so do a host of other OSes. More >>> than likely we're just doing something slightly different that >>> happens to work find with all the other boards out there. >>> >>> My next step is to start looking at how linux works and compare >>> it to how FreeBSD doesn't work. >> >> You will find it in the APIC I/O code and the interrupt routing >> code, with a tiny part in the shipset initialization. >> >> You could fix it in FreeBSD by disregarding what the BIOS says, >> and manually initializing the ServerWorks chipset the way FreeBSD >> wants it (i.e. MPSpec v1.4, mode 2 interrupt processing >> compliant). FreeBSD doesn't run in real "virtual wire mode", it >> makes the interrupts follow Giant. 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. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ 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?XFMail.20021204152439.jhb>