From owner-freebsd-smp Wed Oct 16 12:42:12 2002 Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9662637B407 for ; Wed, 16 Oct 2002 12:42:07 -0700 (PDT) Received: from mail.lambertfam.org (www.lambertfam.org [216.223.196.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id C0EEF43E7B for ; Wed, 16 Oct 2002 12:42:06 -0700 (PDT) (envelope-from lambert@lambertfam.org) Received: from laptop.lambertfam.org (unknown [10.1.0.2]) by mail.lambertfam.org (Postfix) with ESMTP id F04FF35200 for ; Wed, 16 Oct 2002 15:41:58 -0400 (EDT) Received: by laptop.lambertfam.org (Postfix, from userid 1000) id D731F28B09; Wed, 16 Oct 2002 15:41:56 -0400 (EDT) Date: Wed, 16 Oct 2002 15:41:56 -0400 From: Scott Lambert To: FreeBSD-SMP@FreeBSD.org Subject: panic: mpfps Base Table HOSED! Message-ID: <20021016194156.GA81711@laptop.lambertfam.org> Reply-To: FreeBSD-SMP@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I, like at least one other person in the archives, am having panics on attempting to boot an SMP FreeBSD 4.7-RELEASE kernel on an L440GX based P3 motherboard whether the BIOS is set for MP 1.4 or 1.1. The loader loads the kernel then: panic: mpfps Base Table HOSED! mp_lock = 0000000b; cpuid 0; lapic.id = 00000000 Uptime 0s That is hand copied, I may have missed an "=" after cpuid. UP kernel uname -a: FreeBSD www.firstview.com 4.7-RELEASE FreeBSD 4.7-RELEASE #5: Tue Oct 15 19:03:26 EDT 2002 root@ns4.inch.com:/usr/obj/usr/src/sys/GENERIC i386 The other individual from the archives, Jess Fiorelli, seems to have an Adaptec 2100s RAID card. I have an Adaptec 3200S RAID controller with recent firmware. I inherited the box and have been unable to take it down long enough to disassemble it to find out the exact model and brand of the motherboard. I only recently managed to crack the case far enough to see the second CPU. John Baldwin seems to think that the problem with Mr. Fiorelli's box is that some adaptor is loading it's BIOS over the top of the MP table. mptable(1) shows my mptable being FUBAR in a manner similar to Mr. Fiorelli's. I have three devices that seem to load BIOS additions: The Adaptec 3200S: asr0: mem 0xf6000000-0xf7ffffff irq 11 at device 11.1 on pci0 asr0: major=154 asr0: ADAPTEC 3200S FW Rev. 370F, 2 channel, 256 CCBs, Protocol I2O An Adaptec aic7896/97: ahc0: port 0x2000-0x20ff mem 0xf4100000-0xf4100fff irq 10 at device 12.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: Manual LVD Termination ahc0: BIOS eeprom is present ahc0: Secondary High byte termination Enabled ahc0: Secondary Low byte termination Enabled ahc0: Primary Low Byte termination Enabled ahc0: Primary High Byte termination Enabled ahc0: Downloading Sequencer Program... 416 instructions downloaded aic7896/97: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc1: port 0x2400-0x24ff mem 0xf4101000-0xf4101fff irq 10 at device 12.1 on pci0 ahc1: Reading SEEPROM...done. ahc1: Manual LVD Termination ahc1: BIOS eeprom is present ahc1: Secondary High byte termination Enabled ahc1: Secondary Low byte termination Enabled ahc1: Primary Low Byte termination Enabled ahc1: Primary High Byte termination Enabled ahc1: Downloading Sequencer Program... 416 instructions downloaded using shared irq10. aic7896/97: Ultra2 Wide Channel B, SCSI Id=7, 32/253 SCBs An Intel EtherExpress Pro: fxp0: port 0x2800-0x283f mem 0xf4000000-0xf40fffff,0xf4102000-0xf4102fff irq 5 at device 14.0 on pci0 fxp0: using memory space register mapping fxp0: Ethernet address 00:d0:b7:a8:4c:10 fxp0: PCI IDs: 8086 1229 8086 3000 0008 fxp0: Dynamic Standby mode is disabled The motherboard is running a PheonixBIOS 4.0 revision 6 (I think. The 3200S BIOS clears the screen too fast.) Could it be possible to use the BIOS to mark the MP table address space as reserved? I can't afford to have this server down for a quick dig through the BIOS unless there is a chance of success. If it is possible I'd like to have someone smarter than me give me some idea as to what that address space should be. I think it would be the 16 bytes starting at: physical address: 0x000f6ab0 or the 89 bytes starting at: physical address: 0x0009f560 Or are those values already stomped on? Full dmesg.boot of boot -v and the mptable output are at : http://www.lambertfam.org/~lambert/L440GX-SMP/ Not that it matters, the SMP kernel config is GENERIC with SCSI_DELAY 5000 and the smp options un-commented. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message