Date: Tue, 15 Aug 2000 23:34:39 -0700 From: Mike Smith <msmith@freebsd.org> To: Kevin Day <kevind@ikadega.com> Cc: freebsd-smp@freebsd.org Subject: Re: SMP on Compaq Proliant ML530 Message-ID: <200008160634.XAA18007@mass.osd.bsdi.com> In-Reply-To: Your message of "Mon, 14 Aug 2000 16:48:03 CDT." <39986913.E99D87B1@ikadega.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Mike Smith wrote: > > > > MP Config Extended Table Entries: > > > > > > Extended Table HOSED! > > > > This is a bit ugly, but you may be able to improve things by switching OS > > modes in 'advanced' mode in the ECU. Hit Alt-A at the first setup screen > > once you've booted SmartStart and see whether tweaking anything there > > helps. The system will work OK like this though. > > > > I played with that a bit before posting. If I tell it I'm using Windows NT, > my SCSI devices seem to disappear. If I tell it I'm using NetWare, I can > only see the first PCI bus. Telling it I'm running RedHat Linux is the only > way I got this far. There are a few more obscure OS choices there (who still > uses Banyan Vines, especially on a server this size?) that I'll keep trying. Make sure you're in the secret "advanced" mode, and you get a lot more choices. Linux has basically the same expectations about the APIC layout, so it should be a good choice. As was medntioned, Unixware 7 is also a good one. > > > Programming 35 pins in IOAPIC #0 > > > IOAPIC #0 intpin 2 -> irq 0 > > > FreeBSD/SMP: Multiprocessor motherboard > > > cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 > > > cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 > > > io0 (APIC): apic id: 8, version: 0x00220011, at 0xfec00000 > > > > This is OK, although now we'd move the ioapic down to id 2. > > Perhaps this is a carryover from the ML530's bigger brother that has 8 > procs. That would make sense. As Tor pointed out, we wouldn't actually move it - it will Just Work. > > > APIC_IO: Testing 8254 interrupt delivery > > > APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 > > > intpin 2 > > > APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 > > > > This is very typical, hence us having a workaround for it. > > Ok. Perhaps a second test after doing the reroute that says "Workaround > successful" so people like me don't worry quite as much about it? :) The 'routing' message is meant to be the "ok, this is how we deal with it" message - if it doesn't work, things typically hang at that point. (Yes, lame. I'm poking the individual that's currently working on this code. John, are you listening? 8) > > > Everything *seems* ok, but those messages kinda scare me. Has anyone > > > seen anything like this? > > > > Yeah, it's all pretty common. The warning messages are a bit alarming > > though, granted. > > Now if we can only get Compaq to list FreeBSD under the "other" category of > OS's in the startup software. :) *grin* -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] 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?200008160634.XAA18007>