From owner-freebsd-smp Wed Oct 30 13:37:28 1996 Return-Path: owner-smp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA02269 for smp-outgoing; Wed, 30 Oct 1996 13:37:28 -0800 (PST) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA02263 for ; Wed, 30 Oct 1996 13:37:24 -0800 (PST) Received: from localhost (richardc@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with SMTP id NAA03415; Wed, 30 Oct 1996 13:33:38 -0800 Date: Wed, 30 Oct 1996 13:33:36 -0800 (PST) From: Veggy Vinny To: Steve Passe cc: smp@FreeBSD.ORG Subject: Re: SMP Kernel problems In-Reply-To: <199610302125.OAA00873@clem.systemsix.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-smp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 30 Oct 1996, Steve Passe wrote: Hi Steve and everyone, > > On Wed, 30 Oct 1996, Steve Passe wrote: > > > > > > It seems as of October 24, 1996's -current , compiling a SMP > > > > kernel with CONFIG_LINUX now works but there seems to be a problem which > > > > is experience with the SMP kernel and not the -current kernel: > > > > > > > > When the machine comes up and detects the hardware, it pauses at: > > > > > > > > WARNING: mapping PCI INT #10 > > > > > > > > If I hit enter, it continues until it gets to > > > > > > > > sio1: type 16550A > > > > > > > > and freezes. > > > > > > My machine is dead righrt now so I can't check the sources to see where > > > this message is coming from. It might be from my hacks to pci.c, or > > > possibly Stefan has started to add the PCI support I requested (although > > > I haven't seen a merge of -current to the SMP tree so this is doubtful) > > > I should have my machine running by end of day. > > > > > > What hardware is accessed immediately prior to this message?; > > > > Don't remember since my friend is the one who is in front of the > > machines 600 miles away =) and that's the only info he gave... I didn't > > see anything committed to the list except that patch for COMPAT_LINUX > > though. > > > > > By any chance, did you enable SMP_SYMIOXXX (this is not ready yet)? > > > > Nope.... If it was in the kernel config file, I didn't... > > here's the offending line in pci/pci.c: > > --- > int pci_map_int (pcici_t tag, pci_inthand_t *func, void *arg, unsigned > *maskptr) > { > ... > #if defined( SMP ) && defined( SMP_SYMIOXXX ) > if (irq!=19) {printf("WARNING: mapping PCI INT #%d\n",irq);cngetc();} > #endif /* SMP && SMP_SYMIOXXX */ > ... Oh okay... > --- > > SMP_SYMIOXXX is clearly turned on, probably in i386/include/apic.h This won't > work for anyone but me yet, turn it off and this problem should go away. > I am about to commit new code where all the APIC/symmetric IO code is > conditional on "APIC_IO", ie I am going to fold "SMP_SYMIO" & "SMP_SYMIOXXX" > into 1 define and start to request that people turn it on for testing. This > will happen as soon as I get 1 outstanding problem with PCI resolved. > The warning you saw is associated with the bandaid that makes it work for > my particualr hardware. Oh okay so after your commit, would it be turned off? I guess I can just wait until the next merge of -current =) Vince GaiaNet Corporation - Unix Networking Operations - GUS Mailing Lists Admin