From owner-freebsd-smp Sun Oct 11 09:06:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09317 for freebsd-smp-outgoing; Sun, 11 Oct 1998 09:06:57 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09311 for ; Sun, 11 Oct 1998 09:06:53 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id SAA16296 for ; Sun, 11 Oct 1998 18:01:51 +0200 (CEST) To: smp@FreeBSD.ORG Subject: sys/i386/conf/SMP-GENERIC From: Poul-Henning Kamp Date: Sun, 11 Oct 1998 18:01:49 +0200 Message-ID: <16294.908121709@critter.freebsd.dk> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Could somebody more current on the issues please update SMP-GENERIC from GENERIC ? it is WAY out of date! -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Oct 12 05:53:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16954 for freebsd-smp-outgoing; Mon, 12 Oct 1998 05:53:15 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from lexmark.lexmark.com (interlock2.lexmark.com [192.146.101.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA16945 for ; Mon, 12 Oct 1998 05:53:11 -0700 (PDT) (envelope-from fireston@lexmark.com) Received: by interlock2.lexmark.com id AA09420 (InterLock SMTP Gateway 3.0 for freebsd-smp@FreeBSD.ORG); Mon, 12 Oct 1998 08:52:57 -0400 Message-Id: <199810121252.AA09420@interlock2.lexmark.com> Received: by interlock2.lexmark.com (Protected-side Proxy Mail Agent-1); Mon, 12 Oct 1998 08:52:57 -0400 From: Mik Firestone Subject: Current panics with SMP, a 7880 and a 7895 To: freebsd-smp@FreeBSD.ORG Date: Mon, 12 Oct 1998 08:52:51 +0000 (GMT) Reply-To: fireston@lexmark.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ originally sent to -current, reposted here by suggestion ] I am running a Dual Pentium Pro on an PR440FX with an AIC 7880 on board. I also have a 2940 Dual PCI card installed ( 7895 chipset ). If I boot an SMP kernel, it panics while probing the external chain on the Dual card. The kernel is freshly installed from a locally built 1998-10-07, somewhere around 4:00 am EDT. Now, it gets more interesting. The same kernel config minus the SMP options will boot. The same kernel config MINUS the 7895 chip boots as well. Methinks CAM does not like SMP and 7895 chips. Further, we ( being somewhat bored and having some spare parts ) decided to throw a normal 2940 card ( 7880 chipset ) in the machine a it booted without complaint. Did I mention we think CAM, SMP and 7895 just don't play well together? Following is the dump and the trace. Fatal trap 12:Page fault while in kernel mode mp_lock=00000002; cpuid=0; lapic.id=00000000 fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xf0220ae4 stack pointer = 0x10:0xf0d89e1c frame pointer = 0x10:0xf0d89e3c code segement = base of 0x0, limit of 0xfffff, type 0x1b = DPL 0, press 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 0() interupt mask = net tty bio cam <- SMP: XXX kernel: type 12 trap, code = 0 stopped at _INTREN+0x2c: movl %ecx,0(%edx) TRACE: [ on the following revisions: * $Id: kern_intr.c,v 1.20 1998/09/26 14:25:31 dfr Exp $ * $Id: pci_compat.c,v 1.11 1998/09/15 08:21:09 gibbs Exp $ * $Id: pci.c,v 1.89 1998/09/16 08:28:11 dfr Exp $ * $Id: ahc_pci.c,v 1.1 1998/09/15 07:25:33 gibbs Exp $ * $Id: autoconf.c,v 1.106 1998/09/15 10:03:42 gibbs Exp $ * $Id: init_main.c,v 1.96 1998/09/14 19:56:40 sos Exp $ and slighty reformatted ] _INTREN(a,f011f874,f15e0000,f028b654,0) @ _INTREN+0x2c _add_intrdesc(idesc=f1350e80) at _add_intrdesc+0x29 [../kern/kern_intr.c:203] _intr_connect(idesc=f1350e80) at _intr_connect+0x2e [../kern/kern_intr.c:274] _pci_map_int(config=f15d4988,func=f011f874,arg=f15e0000,maskptr=f028b654) at _pci_map_int+0x30 [ pci/pci_compat.c:182 ] _ahc_pci_attach(config_id=f105d4988,unit=2) at _ahc_pci_attach+0x5d7 [ pci/ahc_pci.c:489] _pci_drvattach(dinfo=f15d4980) at _pci_drvattach+0x5f [ pci/pci_compat.c:368] _pci_addcfg(dinfo==f15d4980) at _pci_addcfg+0xcf [ pci/pci.c:475 ] _pci_probebus( bus=0 ) at _pci_probebus+0x53 [ pci/pci.c:522 ] _pci_probe( parent=0 ) at _pci_probe+0x39 [ pci/pci.c:552 ] _pci_configure() at _pci_configure+0xa _configure( dummy = 0 ) at _configure+0x27 [ i386/i386/autoconf.c: 235 ] _main( framep = f0d89fb8 ) at _main+0x86 [ kern/init_main.c: 187 ] begin() at begin+0x54 -- Mik Firestone fireston@lexmark.com If ever I become an Evil Overlord: I will never utter the sentence "But before I kill you, there's just one thing I want to know." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Oct 12 09:47:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21772 for freebsd-smp-outgoing; Mon, 12 Oct 1998 09:47:14 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from rfc.comm.harris.com (adm01.rfc.comm.harris.com [147.177.128.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21636 for ; Mon, 12 Oct 1998 09:46:47 -0700 (PDT) (envelope-from bad2@rfc.comm.harris.com) Received: from fep01.rfc.comm.harris.com (fep01.rfc.comm.harris.com [147.177.0.9]) by rfc.comm.harris.com (8.9.1/8.9.1) with SMTP id MAA60142 for ; Mon, 12 Oct 1998 12:46:31 -0400 Date: Mon, 12 Oct 1998 12:46:31 -0400 (EDT) From: Bernard A Doehner To: freebsd-smp@FreeBSD.ORG Subject: Re: Majordomo results In-Reply-To: <199810121641.JAA20884@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org subscribe freebsd-smp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Oct 12 14:23:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18080 for freebsd-smp-outgoing; Mon, 12 Oct 1998 14:23:17 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from rfc.comm.harris.com (adm01.rfc.comm.harris.com [147.177.128.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18071 for ; Mon, 12 Oct 1998 14:23:14 -0700 (PDT) (envelope-from bad2@rfc.comm.harris.com) Received: from fep01.rfc.comm.harris.com (fep01.rfc.comm.harris.com [147.177.0.9]) by rfc.comm.harris.com (8.9.1/8.9.1) with SMTP id RAA115230 for ; Mon, 12 Oct 1998 17:22:59 -0400 Date: Mon, 12 Oct 1998 17:22:59 -0400 (EDT) From: Bernard A Doehner To: smp@FreeBSD.ORG Subject: Status of SMP on PII Slot 1 and Slot 2. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Gang: My K6 based server didn't survive the move.. Flakey motherboard, and I now have some disposable income to throw in the way of a PII SMP motherboard/system (assuming FreeBSD/SMP works with it). Any recommendations? I thought the newest PII's now come with 512K of L2 cache, so they should be acceptable for SMP work, NO? Or are PPro's (assuming they could be found) still better? Thanks.. Best Regards, Bernie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Oct 13 06:49:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25470 for freebsd-smp-outgoing; Tue, 13 Oct 1998 06:49:00 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA25418 for ; Tue, 13 Oct 1998 06:48:41 -0700 (PDT) (envelope-from eoin@maths.tcd.ie) Received: from boole.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 13 Oct 98 14:48:25 +0100 (BST) To: freebsd-smp@FreeBSD.ORG cc: nops@maths.tcd.ie Subject: dual PII 450 Iwill DBL00 and DBS100 Date: Tue, 13 Oct 1998 14:48:25 +0100 From: Eoin Lawless Message-ID: <9810131448.aa21100@salmon.maths.tcd.ie> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We are trying to use a dual PII 450 Iwill motherboard with FreeBSD (sources current to 9 October, using elf). We've tried both the DBL100 and DBS100. Unfortunately the second processor does not seem to behave correctly. It runs, but only at about 1% of the correct speed. This is even reported by the CD provided with the motherboard (which boots a Linux kernel). The motherboard does run correctly with NT. This leads us to believe that the BIOS is not enabeling the second CPU correctly. Also NT reports a MPS of 1.4 while FreeBSD and Linux report 1.1 regardless of the setting in the BIOS. We have tried enabling and disabling APM in the bios and kernel, but this had no affect. Has anyone else had success with either of these boards? (The mail archives do report success with Iwill boards and PPros) dmesg and mptable output below: =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f57b0 signature: '_MP_' length: 16 bytes version: 1.1 checksum: 0x80 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f1400 signature: 'PCMP' base table length: 292 version: 1.1 checksum: 0xfa OEM ID: 'OEM00000' Product ID: 'PROD00000000' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 28 local APIC address: 0xfee00000 extended table length: 0 extended table checksum: 0 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 6 5 2 0xfbff 1 0x11 AP, usable 6 5 2 0xfbff -- Bus: Bus ID Type 0 PCI 1 PCI 2 ISA -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 2 0 2 0 INT conforms conforms 2 1 2 1 INT conforms conforms 2 0 2 2 INT conforms conforms 2 3 2 3 INT conforms conforms 2 4 2 4 INT conforms conforms 2 5 2 5 INT conforms conforms 2 6 2 6 INT conforms conforms 2 7 2 7 INT active-hi edge 2 8 2 8 INT conforms conforms 2 9 2 9 INT conforms conforms 2 10 2 10 INT conforms conforms 2 11 2 11 INT conforms conforms 2 12 2 12 INT conforms conforms 2 13 2 13 INT conforms conforms 2 14 2 14 INT conforms conforms 2 15 2 15 INT active-lo level 0 15:A 2 16 INT active-lo level 0 18:A 2 18 INT active-lo level 0 20:A 2 19 SMI conforms conforms 2 0 2 23 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 0 0:A 255 0 NMI conforms conforms 0 0:A 255 1 ------------------------------------------------------------------------------- # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=3 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs =============================================================================== Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-BETA #1: Mon Oct 12 20:53:26 BST 1998 iedowse@gosset.maths.tcd.ie:/usr/src/sys/compile/GOSSET Timecounter "i8254" frequency 1193182 Hz cost 3038 ns CPU: Pentium II (quarter-micron) (686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff> real memory = 268435456 (262144K bytes) avail memory = 258637824 (252576K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 chip3: rev 0x01 int d irq 255 on pci0.7.2 chip4: rev 0x02 on pci0.7.3 vga0: rev 0x00 int a irq 16 on pci0.15.0 fxp0: rev 0x02 int a irq 18 on pci0.18.0 fxp0: Ethernet address 00:a0:c9:e1:c4:5b ahc0: rev 0x00 int a irq 19 on pci0.20.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found mse0 not found at 0x23c psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface apm0 flags 0x20 on isa apm: found APM BIOS version 1.2 SMP: AP CPU #1 Launched! da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 40.0MB/s transfers (20.0MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8683MB (17783249 512 byte sectors: 255H 63S/T 1106C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: 40.0MB/s transfers (20.0MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 8683MB (17783249 512 byte sectors: 255H 63S/T 1106C) changing root device to da0s1a (da0:ahc0:0:0:0): tagged openings now 38 ---- Eoin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Oct 13 17:46:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03459 for freebsd-smp-outgoing; Tue, 13 Oct 1998 17:46:59 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from pozo.pozo.com (pozo.pozo.com [207.201.8.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03442; Tue, 13 Oct 1998 17:46:56 -0700 (PDT) (envelope-from mantar@netcom.com) Received: from dual (DUAL [192.168.0.2]) by pozo.pozo.com (8.9.1/8.9.1) with SMTP id RAA00288; Tue, 13 Oct 1998 17:46:40 -0700 (PDT) (envelope-from mantar@netcom.com) Message-Id: <4.1.19981013171511.00a2b100@192.168.0.1> X-Sender: null@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 13 Oct 1998 17:46:39 -0700 To: current@FreeBSD.ORG From: Manfred Antar Subject: Panic when rebooting with current kernel Cc: smp@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For the past day every time I reboot (shutdown -r now) I get boot called on cpu#0 syncing disks... 3 done panic: rslock: cpu: 1, addr:0xf5b49f88, lock: 0x01000001 mp_lock = 01000001; cpuid = 1; lapic.id = 0c000000 Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.98 This happens with both aout and elf kernels. This is an SMP Intel PR440FX with a DPT (no-raid) controller. The sources are current as 5pm Oct 13 PDT. A kernel from 24 hours ago works fine. There were alot of changes to the sys tree in the past day. I try backing out to 1 day ago. And see if i can find the change that caused this Manfred ============================== || mantar@netcom.com || || pozo@infinex.com || || Ph. (415) 681-6235 || ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Oct 13 18:15:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08763 for freebsd-smp-outgoing; Tue, 13 Oct 1998 18:15:01 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08751; Tue, 13 Oct 1998 18:14:56 -0700 (PDT) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id SAA09441; Tue, 13 Oct 1998 18:14:40 -0700 (PDT) Date: Tue, 13 Oct 1998 18:14:40 -0700 (PDT) From: Chris Timmons To: Manfred Antar cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Panic when rebooting with current kernel In-Reply-To: <4.1.19981013171511.00a2b100@192.168.0.1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've filed this as kern/8309, which contains a trace (I have a core, -g'd kernel and the aout gdb if anybody wants them :) I will say that this was the first time I built a kernel slightly out of sync with the world, so I am going to go back and do that to make sure there isn't something goofy in that regard. -Chris On Tue, 13 Oct 1998, Manfred Antar wrote: > For the past day every time I reboot (shutdown -r now) I get > > boot called on cpu#0 > > > syncing disks... 3 done > panic: rslock: cpu: 1, addr:0xf5b49f88, lock: 0x01000001 > mp_lock = 01000001; cpuid = 1; lapic.id = 0c000000 > Debugger("panic") > Stopped at Debugger+0x35: movb $0,in_Debugger.98 > > This happens with both aout and elf kernels. > This is an SMP Intel PR440FX with a DPT (no-raid) controller. > The sources are current as 5pm Oct 13 PDT. > A kernel from 24 hours ago works fine. There were alot of changes > to the sys tree in the past day. I try backing out to 1 day ago. > And see if i can find the change that caused this > Manfred > ============================== > || mantar@netcom.com || > || pozo@infinex.com || > || Ph. (415) 681-6235 || > ============================== > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Oct 13 18:32:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11265 for freebsd-smp-outgoing; Tue, 13 Oct 1998 18:32:37 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11248; Tue, 13 Oct 1998 18:32:34 -0700 (PDT) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id DAA14893; Wed, 14 Oct 1998 03:32:18 +0200 (CEST) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id DAA29240; Wed, 14 Oct 1998 03:32:17 +0200 (MET DST) Message-ID: <19981014033216.03772@follo.net> Date: Wed, 14 Oct 1998 03:32:16 +0200 From: Eivind Eklund To: Chris Timmons , Manfred Antar Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Panic when rebooting with current kernel References: <4.1.19981013171511.00a2b100@192.168.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: ; from Chris Timmons on Tue, Oct 13, 1998 at 06:14:40PM -0700 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Oct 13, 1998 at 06:14:40PM -0700, Chris Timmons wrote: > > I've filed this as kern/8309, which contains a trace (I have a core, -g'd > kernel and the aout gdb if anybody wants them :) > > I will say that this was the first time I built a kernel slightly out of > sync with the world, so I am going to go back and do that to make sure > there isn't something goofy in that regard. You're not supposed to be able to trigger a panic() by being out of sync, so it is a bug no matter what. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Oct 14 09:01:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12006 for freebsd-smp-outgoing; Wed, 14 Oct 1998 09:01:31 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from uruk.org (ns.uruk.org [198.145.95.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA11998 for ; Wed, 14 Oct 1998 09:01:27 -0700 (PDT) (envelope-from erich@uruk.org) Received: from uruk.org [127.0.0.1] by uruk.org with esmtp (Exim 0.53 #1) id E0zTTKv-0001cb-00; Wed, 14 Oct 1998 08:59:41 -0700 To: Eoin Lawless cc: freebsd-smp@FreeBSD.ORG Subject: Re: dual PII 450 Iwill DBL00 and DBS100 In-reply-to: Your message of "Tue, 13 Oct 1998 14:48:25 BST." <9810131448.aa21100@salmon.maths.tcd.ie> Date: Wed, 14 Oct 1998 08:59:40 -0700 From: Erich Boleyn Message-Id: Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Eoin Lawless wrote: > We are trying to use a dual PII 450 Iwill motherboard with FreeBSD > (sources current to 9 October, using elf). We've tried both the > DBL100 and DBS100. Unfortunately the second processor does not > seem to behave correctly. It runs, but only at about 1% of the > correct speed. This is even reported by the CD provided with the > motherboard (which boots a Linux kernel). > > The motherboard does run correctly with NT. This leads us to believe > that the BIOS is not enabeling the second CPU correctly. Also NT reports > a MPS of 1.4 while FreeBSD and Linux report 1.1 regardless of the > setting in the BIOS. Hmmm... I know there have been updates of the MP Spec since 1.4, but I didn't think any of them changed how the version numbers were checked. Is there a special NT MP "hal.dll" version that you run with the machine? (I've seen this for a few machines... the manufacturer gives a floppy with a special NT HAL layer to fix hardware bugs/improve their specific machine) If nothing else, I have an SMP BIOS checker that runs outside of an OS I'd like you to try. -- Erich Stefan Boleyn \_ Mad Scientist -- CyberMuffin \__ http://www.uruk.org/ Motto: "I'll live forever or die trying" --------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Oct 14 10:46:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27519 for freebsd-smp-outgoing; Wed, 14 Oct 1998 10:46:23 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA27514 for ; Wed, 14 Oct 1998 10:46:21 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from hamilton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 14 Oct 98 18:46:03 +0100 (BST) To: freebsd-smp@FreeBSD.ORG cc: nops@maths.tcd.ie Date: Wed, 14 Oct 1998 18:46:03 +0100 From: Ian Dowse Message-ID: <9810141846.aa07903@salmon.maths.tcd.ie> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Subject: Re: dual PII 450 Iwill DBL00 and DBS100 In-reply-to: Your message of "Tue, 13 Oct 1998 14:48:25 BST." <9810131448.aa21100@salmon.maths.tcd.ie> -------- In message <9810131448.aa21100@salmon.maths.tcd.ie>, Eoin Lawless writes: > >We are trying to use a dual PII 450 Iwill motherboard with FreeBSD >(sources current to 9 October, using elf). We've tried both the >DBL100 and DBS100. Unfortunately the second processor does not >seem to behave correctly. It runs, but only at about 1% of the >correct speed. We've just figured out what is causing this. There are two problems: 1. The BIOS in the DBL100 (and DBS100) motherboard does not set up the MTRRs for the second CPU correctly. All the variable-range MTRRs in the AP contain 0. (I haven't checked the fixed ones yet) 2. Due to some broken code in i386/pmap.c, FreeBSD does not copy the MTRRs from the BSP to the AP. It checks cpu == CPU_686 instead of cpu_class == CPUCLASS_686 to determine if the MTRRs are present. The cpu is now detected as CPU_PII, so the MTRRs are never programmed. The patch below fixes this. BTW is the getmtrr() in ap_init() necessary? As far as I can see this will just overwrite the global PPro_vmtrr array with the APs MTRR register contents - this isn't a problem as such because init_secondary writes the contents of PPro_vmtrr to the AP first, but seems unnecessary. Ian --- pmap.c.orig Wed Oct 14 18:20:27 1998 +++ pmap.c Wed Oct 14 18:21:32 1998 @@ -459,7 +459,7 @@ { int i; - if (cpu == CPU_686) { + if (cpu_class == CPUCLASS_686) { for(i = 0; i < NPPROVMTRR; i++) { PPro_vmtrr[i].base = rdmsr(PPRO_VMTRRphysBase0 + i * 2); PPro_vmtrr[i].mask = rdmsr(PPRO_VMTRRphysMask0 + i * 2); @@ -472,7 +472,7 @@ { int i; - if (cpu == CPU_686) { + if (cpu_class == CPUCLASS_686) { wbinvd(); for(i = 0; i < NPPROVMTRR; i++) { wrmsr(PPRO_VMTRRphysBase0 + i * 2, PPro_vmtrr[i].base); @@ -485,7 +485,7 @@ pmap_setvidram(void) { #if 0 - if (cpu == CPU_686) { + if (cpu_class == CPUCLASS_686) { wbinvd(); /* * Set memory between 0-640K to be WB @@ -508,7 +508,7 @@ unsigned long long base; unsigned long long mask; - if (cpu != CPU_686) + if (cpu_class != CPUCLASS_686) return; free = -1; @@ -2819,7 +2819,7 @@ cpu_invlpg(&prv_CPAGE3); #if defined(I686_CPU) - if (cpu == CPU_686) + if (cpu_class == CPUCLASS_686) i686_pagezero(&prv_CPAGE3); else #endif @@ -2840,7 +2840,7 @@ } #if defined(I686_CPU) - if (cpu == CPU_686) + if (cpu_class == CPUCLASS_686) i686_pagezero(CADDR2); else #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Oct 15 01:02:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA20407 for freebsd-smp-outgoing; Thu, 15 Oct 1998 01:02:37 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA20402 for ; Thu, 15 Oct 1998 01:02:35 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:EA8HjuHn5NLxkFls2QgRDZ54NLhJlJeF@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id RAA17816 for ; Thu, 15 Oct 1998 17:02:17 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id RAA22137; Thu, 15 Oct 1998 17:03:30 +0900 (JST) Message-Id: <199810150803.RAA22137@zodiac.mech.utsunomiya-u.ac.jp> To: smp@FreeBSD.ORG cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: VM86, VESA support in SMP Date: Thu, 15 Oct 1998 17:03:29 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The VESA BIOS support initially didn't work in the SMP box because of some bugs in VM86 code. Now that they seem to be fixed, do anybody still see problems? I certainly have no trouble in my SMP box. Shall we remove the following line from LINT? # To include support for VESA video modes --> # Dont use together with SMP!! options VESA # needs VM86 defined too!! Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Oct 15 01:34:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23452 for freebsd-smp-outgoing; Thu, 15 Oct 1998 01:34:31 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [212.242.40.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23446 for ; Thu, 15 Oct 1998 01:34:29 -0700 (PDT) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.9.1/8.9.1) id KAA12503; Thu, 15 Oct 1998 10:34:01 +0200 (CEST) (envelope-from sos) Message-Id: <199810150834.KAA12503@sos.freebsd.dk> Subject: Re: VM86, VESA support in SMP In-Reply-To: <199810150803.RAA22137@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Oct 15, 98 05:03:29 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Thu, 15 Oct 1998 10:34:01 +0200 (CEST) Cc: smp@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In reply to Kazutaka YOKOTA who wrote: > The VESA BIOS support initially didn't work in the SMP box because of > some bugs in VM86 code. > > Now that they seem to be fixed, do anybody still see problems? I > certainly have no trouble in my SMP box. I still run with the patch in kern_clock.c, but I'm not sure its needed anymore, besides that it works just fine... > Shall we remove the following line from LINT? > > # To include support for VESA video modes > --> # Dont use together with SMP!! > options VESA # needs VM86 defined too!! Dependent on the mentioned clock fix, yes... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end? .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Oct 15 17:52:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07588 for freebsd-smp-outgoing; Thu, 15 Oct 1998 17:52:30 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA07571; Thu, 15 Oct 1998 17:52:17 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:DMInZ1TD6/Ls/A01OQSOZcuw6sL+GpVZ@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id JAA19284; Fri, 16 Oct 1998 09:51:58 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id JAA16906; Fri, 16 Oct 1998 09:53:11 +0900 (JST) Message-Id: <199810160053.JAA16906@zodiac.mech.utsunomiya-u.ac.jp> To: sos@FreeBSD.ORG cc: smp@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: VM86, VESA support in SMP In-reply-to: Your message of "Thu, 15 Oct 1998 10:34:01 +0200." <199810150834.KAA12503@sos.freebsd.dk> References: <199810150834.KAA12503@sos.freebsd.dk> Date: Fri, 16 Oct 1998 09:53:10 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >In reply to Kazutaka YOKOTA who wrote: >> The VESA BIOS support initially didn't work in the SMP box because of >> some bugs in VM86 code. >> >> Now that they seem to be fixed, do anybody still see problems? I >> certainly have no trouble in my SMP box. > >I still run with the patch in kern_clock.c, but I'm not sure its >needed anymore, besides that it works just fine... Oh. I have that patch too in my box. I nearly fotgot :-) I recall tegge said that he was thinking of a better way of fixing this, but I don't think we have seen the fix being committed to the source tree. We had better keep the LINT file as it is... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sat Oct 17 15:25:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03162 for freebsd-smp-outgoing; Sat, 17 Oct 1998 15:25:35 -0700 (PDT) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03155 for ; Sat, 17 Oct 1998 15:25:33 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id SAA00351; Sat, 17 Oct 1998 18:24:56 -0400 (EDT) Date: Sat, 17 Oct 1998 18:24:56 -0400 (EDT) From: Chuck Robey To: Karl Pielorz cc: freebsd-smp@FreeBSD.ORG Subject: Re: Latest kernel In-Reply-To: <36290E93.139108FE@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 17 Oct 1998, Karl Pielorz wrote: > > I have 192M of swap, in two 96M partitions. I have 64M of memory. That > > ought to be hoards and hoards more than I need. > > Yes, that's fine - I thought you might have had 96Mb of RAM :-) [deletions] > Ahh... I've just seen something I should have seen before... When it becomes time in the kernel to do the dump, I see in ddb the following (paraphrased because I handcopied it down): other_cpus = 00000002 stopped_cpus = 00000000 stop_cpu() failed. I think this might be a smp deal, so I am moving this thread to smp. To remind folks, I am trying to generate a kernel dump here, and the size and placement of my swap is fine. I just don't get the dump. It's not a savecore thing, the dump never occurs at all, so savecore can handly restore it. Why? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message