From owner-freebsd-smp Wed Nov 27 13:02:54 1996 Return-Path: owner-smp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA12162 for smp-outgoing; Wed, 27 Nov 1996 13:02:54 -0800 (PST) Received: from clem.systemsix.com (clem.systemsix.com [198.99.86.131]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA12155 for ; Wed, 27 Nov 1996 13:02:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by clem.systemsix.com (8.6.12/8.6.12) with SMTP id OAA16661; Wed, 27 Nov 1996 14:02:34 -0700 Message-Id: <199611272102.OAA16661@clem.systemsix.com> X-Authentication-Warning: clem.systemsix.com: Host localhost didn't use HELO protocol X-Mailer: exmh version 1.6.5 12/11/95 From: Steve Passe To: Terje Normann Marthinussen cc: freebsd-smp@freebsd.org Subject: Re: cvs commit: sys/i386/i386 locore.s swtch.s sys/i386/include pmap.h In-reply-to: Your message of "Wed, 27 Nov 1996 21:38:28 +0100." <199611272038.VAA04476@slibo.cc.uit.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 27 Nov 1996 14:02:34 -0700 Sender: owner-smp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, > >the program 'mptable' (on the SMP web page) will analyze your > >board and create a definitive "options" list for your config file. The > ... > Yes, I know of mptable, used it to find the right number. > But don't you already examine the table when you discover that NBUS is > to low? yes, you could go on to count them, but there are a half dozen other options that also might need tuning, requireing more code to handle them. Its just an arbitrary decision on my part, there is no technical reason it can't be done. --- > >--- > >> However then came: > >> BIOS basemem (633K) != RTC basemem (640K), setting to BIOS value > >> unknown bus type: 'XPRESS' > >> > >> Followed by panic... > >> Argh, haven't had time to study what it would like to know about the bus. > >> If it is something special, anyone that has enough information to do > >> something about it? > >> ... > >> Well, it worked in earlier releases, so I quickly commented out the panic() > >> and continued. Just didn't have the patience :) > > > >if you don't need to use anything on the XPRESS bus it should be simple, > >I'll look at it later today... > > Well, I'm not really sure what the XPRESS bus is. I'm a bit new to these > machines. I would suspect it to be the system bus? > > If so, I would suspect that the PCI busses and CPU cards are already on it? > The only slots in it that is non pci/eisa are those that the CPU > and memory cards are plugged into. the CPU/memory might be whats on the XXPRESS bus. you have 2 PCI busses, as well as an EISA bus in addition to the XPRESS bus: --- Bus: Bus ID Type 0 PCI 1 PCI 18 XPRESS 19 EISA -- I/O APICs: APIC ID Version State Address 14 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID INT# ExtINT active-hi edge 19 0 14 0 INT active-hi edge 19 1 14 1 INT active-hi edge 19 0 14 2 INT active-hi edge 19 3 14 3 INT active-hi edge 19 4 14 4 INT active-hi edge 19 5 14 5 INT active-hi edge 19 6 14 6 INT conforms level 19 7 14 7 INT active-hi edge 19 8 14 8 INT active-hi edge 19 9 14 9 INT conforms level 19 10 14 10 INT conforms level 19 11 14 11 INT active-hi edge 19 12 14 12 INT active-hi edge 19 13 14 13 INT active-hi edge 19 14 14 14 INT active-hi edge 19 15 14 15 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID INT# ExtINT active-hi edge 19 0 255 0 NMI active-hi edge 0 0:A 255 1 --- none of the above entries use the XPRESS bus id (18) so nothing important appears to be on the XPRESS bus. I suspect your problems are a bug in the >2 CPU stuff, its only a few hours old at this point and neither Peter or I have a 4 CPU machine for testing. we'll be dependant on testers like yourself to get past this one! -- Steve Passe | powered by smp@csn.net | FreeBSD -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzHe7tEAAAEEAM274wAEEdP+grIrV6UtBt54FB5ufifFRA5ujzflrvlF8aoE 04it5BsUPFi3jJLfvOQeydbegexspPXL6kUejYt2OeptHuroIVW5+y2M2naTwqtX WVGeBP6s2q/fPPAS+g+sNZCpVBTbuinKa/C4Q6HJ++M9AyzIq5EuvO0a8Rr9AAUR tBlTdGV2ZSBQYXNzZSA8c21wQGNzbi5uZXQ+ =ds99 -----END PGP PUBLIC KEY BLOCK-----