From owner-freebsd-smp  Sun Jul 25 18:20:41 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
	by hub.freebsd.org (Postfix) with ESMTP id 4F31914FD8
	for <freebsd-smp@freebsd.org>; Sun, 25 Jul 1999 18:20:27 -0700 (PDT)
	(envelope-from marc@oldserver.demon.nl)
Received: from [212.238.105.241] (helo=genuine)
	by post.mail.nl.demon.net with smtp (Exim 2.02 #1)
	id 118ZRH-0003Fp-00
	for freebsd-smp@FreeBSD.ORG; Mon, 26 Jul 1999 01:20:24 +0000
Message-ID: <02ee01bed705$143b1fe0$0400000a@oldserver.demon.nl>
From: "Marc Schneiders" <marc@oldserver.demon.nl>
To: <freebsd-smp@FreeBSD.ORG>
Subject: Pentium Pro MTRR support enabled, default memory type is uncacheable
Date: Mon, 26 Jul 1999 03:20:42 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_02EB_01BED715.D7919540"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

This is a multi-part message in MIME format.

------=_NextPart_000_02EB_01BED715.D7919540
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Should I worry about the message quoted in subject? Does it mean the =
256K CPU-cache is not working??

Full dmesg below.

TIA!

Marc Schneiders
marc@oldserver.demon.nl


Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #6: Wed Jul 21 16:25:26 CEST 1999
    root@unclad.oldserver.demon.nl:/usr/src/sys/compile/UNCLAD
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium Pro (686-class CPU)
  Origin =3D "GenuineIntel"  Id =3D 0x0x619  Stepping =3D 9
  =
Features=3D0xfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MC=
A,CMOV>
real memory  =3D 268435456 (262144K bytes)
config> en ep0
config> po ep0 0x310
config> ir ep0 10
config> f ep0 0
config> q
avail memory =3D 258437120 (252380K bytes)
Programming 24 pins in IOAPIC #0
FreeBSD/SMP: Multiprocessor motherboard
 cpu0 (BSP): apic id:  1, version: 0x00x40011, at 0x0xfee00000
 cpu1 (AP):  apic id:  0, version: 0x00x40011, at 0x0xfee00000
 io0 (APIC): apic id:  2, version: 0x0x170011, at 0x0xfec00000
Preloaded elf kernel "kernel" at 0xc02ca000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc02ca09c.
VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c1be2 (0xc0001be2)
VESA: S3 Incorporated. 86C325
Pentium Pro MTRR support enabled, default memory type is uncacheable
Probing for PnP devices:
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <PCI host bus adapter> on motherboard
pci0: <PCI bus> on pcib0
chip0: <Intel 82440FX (Natoma) PCI and memory controller> at device 0.0 =
on pci0
isab0: <Intel 82371SB PCI to ISA bridge> at device 7.0 on pci0
chip1: <Intel PIIX3 IDE controller> at device 7.1 on pci0
vga-pci0: <S3 ViRGE graphics accelerator> irq 2 at device 11.0 on pci0
isa0: <ISA bus> on motherboard
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> at fdc0 drive 0
aha0 at port 0x330-0x333,0x330-0x333 irq 11 drq 5 on isa0
aha0: AHA-1540/1542 64 head BIOS FW Rev. 0.8 (ID=3D0x41) SCSI Host =
Adapter, SCSI ID 7, 16 CCBs
atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: <Generic ISA VGA> at port 0x3b0-0x3df iomem 0xa0000-0xbffff on =
isa0
sc0: <System console> on isa0
sc0: VGA <16 virtual consoles, flags=3D0x0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
plip0: <PLIP network interface> on ppbus 0
lpt0: <generic printer> on ppbus 0
lpt0: Interrupt-driven port
ppi0: <generic parallel i/o> on ppbus 0
1 3C5x9 board(s) on ISA found at 0x0x310
ep0 at port 0x310-0x31f iomem 0 irq 10 drq 0 on isa0
ep0: aui/utp/bnc[*BNC*] address 00:a0:24:c4:dc:4d
APIC_IO: Testing 8254 interrupt delivery
APIC_IO: routing 8254 via pin 2
ep0 XXX: driver didn't set ifq_maxlen
Waiting 7 seconds for SCSI devices to settle
SMP: AP CPU #1 Launched!
changing root device to da0s1a
da0 at aha0 bus 0 target 0 lun 0
da0: <QUANTUM FIREBALL ST3.2S 0F0C> Fixed Direct Access SCSI-2 device=20
da0: 3.300MB/s transfers
da0: 3090MB (6328861 512 byte sectors: 64H 32S/T 3090C)
da1 at aha0 bus 0 target 2 lun 0
da1: <NOMAI MCD 540I 5.55> Removable Direct Access SCSI-2 device=20
da1: 3.300MB/s transfers
da1: 515MB (1055416 512 byte sectors: 64H 32S/T 515C)
cd0 at aha0 bus 0 target 1 lun 0
cd0: <PLEXTOR CD-ROM PX-40TS 1.00> Removable CD-ROM SCSI-2 device=20
cd0: 3.300MB/s transfers
cd0: cd present [684220 x 512 byte records]
cd9660: Joliet Extension


------=_NextPart_000_02EB_01BED715.D7919540
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Should I worry about the message quoted =
in subject?=20
Does it mean the 256K CPU-cache is not working??</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Full dmesg below.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>TIA!</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Marc Schneiders</FONT></DIV>
<DIV><FONT face=3DArial size=3D2><A=20
href=3D"mailto:marc@oldserver.demon.nl">marc@oldserver.demon.nl</A></FONT=
></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Copyright (c) 1992-1999 The FreeBSD=20
Project.<BR>Copyright (c) 1982, 1986, 1989, 1991, 1993<BR>The Regents of =
the=20
University of California. All rights reserved.<BR>FreeBSD 4.0-CURRENT =
#6: Wed=20
Jul 21 16:25:26 CEST 1999<BR>&nbsp;&nbsp;&nbsp; <A=20
href=3D"mailto:root@unclad.oldserver.demon.nl:/usr/src/sys/compile/UNCLAD=
">root@unclad.oldserver.demon.nl:/usr/src/sys/compile/UNCLAD</A><BR>Timec=
ounter=20
"i8254"&nbsp; frequency 1193182 Hz<BR>CPU: Pentium Pro (686-class =
CPU)<BR>&nbsp;=20
Origin =3D "GenuineIntel"&nbsp; Id =3D 0x0x619&nbsp; Stepping =3D =
9<BR>&nbsp;=20
Features=3D0xfbff&lt;FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE=
,MCA,CMOV&gt;<BR>real=20
memory&nbsp; =3D 268435456 (262144K bytes)<BR>config&gt; en =
ep0<BR>config&gt; po=20
ep0 0x310<BR>config&gt; ir ep0 10<BR>config&gt; f ep0 0<BR>config&gt; =
q<BR>avail=20
memory =3D 258437120 (252380K bytes)<BR>Programming 24 pins in IOAPIC=20
#0<BR>FreeBSD/SMP: Multiprocessor motherboard<BR>&nbsp;cpu0 (BSP): apic=20
id:&nbsp; 1, version: 0x00x40011, at 0x0xfee00000<BR>&nbsp;cpu1 =
(AP):&nbsp; apic=20
id:&nbsp; 0, version: 0x00x40011, at 0x0xfee00000<BR>&nbsp;io0 (APIC): =
apic=20
id:&nbsp; 2, version: 0x0x170011, at 0x0xfec00000<BR>Preloaded elf =
kernel=20
"kernel" at 0xc02ca000.<BR>Preloaded userconfig_script =
"/boot/kernel.conf" at=20
0xc02ca09c.<BR>VESA: v1.2, 2048k memory, flags:0x0, mode =
table:0xc00c1be2=20
(0xc0001be2)<BR>VESA: S3 Incorporated. 86C325<BR>Pentium Pro MTRR =
support=20
enabled, default memory type is uncacheable<BR>Probing for PnP =
devices:<BR>npx0:=20
&lt;math processor&gt; on motherboard<BR>npx0: INT 16 =
interface<BR>pcib0:=20
&lt;PCI host bus adapter&gt; on motherboard<BR>pci0: &lt;PCI bus&gt; on=20
pcib0<BR>chip0: &lt;Intel 82440FX (Natoma) PCI and memory controller&gt; =
at=20
device 0.0 on pci0<BR>isab0: &lt;Intel 82371SB PCI to ISA bridge&gt; at =
device=20
7.0 on pci0<BR>chip1: &lt;Intel PIIX3 IDE controller&gt; at device 7.1 =
on=20
pci0<BR>vga-pci0: &lt;S3 ViRGE graphics accelerator&gt; irq 2 at device =
11.0 on=20
pci0<BR>isa0: &lt;ISA bus&gt; on motherboard<BR>fdc0: &lt;NEC 72065B or=20
clone&gt; at port 0x3f0-0x3f7 irq 6 drq 2 on isa0<BR>fdc0: FIFO enabled, =
8 bytes=20
threshold<BR>fd0: &lt;1440-KB 3.5" drive&gt; at fdc0 drive 0<BR>aha0 at =
port=20
0x330-0x333,0x330-0x333 irq 11 drq 5 on isa0<BR>aha0: AHA-1540/1542 64 =
head BIOS=20
FW Rev. 0.8 (ID=3D0x41) SCSI Host Adapter, SCSI ID 7, 16 =
CCBs<BR>atkbdc0:=20
&lt;keyboard controller (i8042)&gt; at port 0x60-0x6f on isa0<BR>atkbd0: =
&lt;AT=20
Keyboard&gt; irq 1 on atkbdc0<BR>psm0: &lt;PS/2 Mouse&gt; irq 12 on=20
atkbdc0<BR>psm0: model Generic PS/2 mouse, device ID 0<BR>vga0: =
&lt;Generic ISA=20
VGA&gt; at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0<BR>sc0: =
&lt;System=20
console&gt; on isa0<BR>sc0: VGA &lt;16 virtual consoles,=20
flags=3D0x0x200&gt;<BR>sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on =
isa0<BR>sio0:=20
type 16550A<BR>sio1 at port 0x2f8-0x2ff irq 3 on isa0<BR>sio1: type=20
16550A<BR>ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0<BR>ppc0: =
Generic=20
chipset (EPP/NIBBLE) in COMPATIBLE mode<BR>plip0: &lt;PLIP network =
interface&gt;=20
on ppbus 0<BR>lpt0: &lt;generic printer&gt; on ppbus 0<BR>lpt0: =
Interrupt-driven=20
port<BR>ppi0: &lt;generic parallel i/o&gt; on ppbus 0<BR>1 3C5x9 =
board(s) on ISA=20
found at 0x0x310<BR>ep0 at port 0x310-0x31f iomem 0 irq 10 drq 0 on =
isa0<BR>ep0:=20
aui/utp/bnc[*BNC*] address 00:a0:24:c4:dc:4d<BR>APIC_IO: Testing 8254 =
interrupt=20
delivery<BR>APIC_IO: routing 8254 via pin 2<BR>ep0 XXX: driver didn't =
set=20
ifq_maxlen<BR>Waiting 7 seconds for SCSI devices to settle<BR>SMP: AP =
CPU #1=20
Launched!<BR>changing root device to da0s1a<BR>da0 at aha0 bus 0 target =
0 lun=20
0<BR>da0: &lt;QUANTUM FIREBALL ST3.2S 0F0C&gt; Fixed Direct Access =
SCSI-2 device=20
<BR>da0: 3.300MB/s transfers<BR>da0: 3090MB (6328861 512 byte sectors: =
64H 32S/T=20
3090C)<BR>da1 at aha0 bus 0 target 2 lun 0<BR>da1: &lt;NOMAI MCD 540I =
5.55&gt;=20
Removable Direct Access SCSI-2 device <BR>da1: 3.300MB/s =
transfers<BR>da1: 515MB=20
(1055416 512 byte sectors: 64H 32S/T 515C)<BR>cd0 at aha0 bus 0 target 1 =
lun=20
0<BR>cd0: &lt;PLEXTOR CD-ROM PX-40TS 1.00&gt; Removable CD-ROM SCSI-2 =
device=20
<BR>cd0: 3.300MB/s transfers<BR>cd0: cd present [684220 x 512 byte=20
records]<BR>cd9660: Joliet Extension<BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_02EB_01BED715.D7919540--



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Mon Jul 26  2:21:42 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135])
	by hub.freebsd.org (Postfix) with ESMTP id 6681815335
	for <freebsd-smp@FreeBSD.ORG>; Mon, 26 Jul 1999 02:21:23 -0700 (PDT)
	(envelope-from vallo@matti.ee)
Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87])
	by solaris.matti.ee (8.9.3/8.9.3) with ESMTP id MAA22470;
	Mon, 26 Jul 1999 12:17:51 +0300 (EET DST)
Received: by myhakas.matti.ee (Postfix, from userid 1000)
	id 7F0B91FC4; Mon, 26 Jul 1999 12:18:14 +0300 (EEST)
Date: Mon, 26 Jul 1999 12:18:14 +0300
From: Vallo Kallaste <vallo@matti.ee>
To: Fabio Cesar Gozzo <fabio@iqm.unicamp.br>
Cc: freebsd-smp@FreeBSD.ORG
Subject: Re: Dual PIII motherboard
Message-ID: <19990726121814.C38516@myhakas.matti.ee>
Reply-To: vallo@matti.ee
References: <199907232039.RAA20231@thomson.iqm.unicamp.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <199907232039.RAA20231@thomson.iqm.unicamp.br>; from Fabio Cesar Gozzo on Fri, Jul 23, 1999 at 05:39:32PM -0300
Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?=
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Fri, Jul 23, 1999 at 05:39:32PM -0300, Fabio Cesar Gozzo <fabio@iqm.unicamp.br> wrote:

> Hi,
> I'm planning to buy a dual PIII 550 Mhz and I am
> looking for advices on manufacturer/model.
> I've been using ASUS already, but I was browsing their home
> pages and didn't find a dual board supporting 550 Mhz processors.
> I found an Intel board, but I have seen people complaining
> about the on board NCR SCSI.
> Any suggestions ?
> Thank you,

How about Tyan S1837UANG "Thunderbolt" ? It's excellent board.
-- 

Vallo Kallaste
vallo@matti.ee


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Mon Jul 26  2:30:48 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by hub.freebsd.org (Postfix) with ESMTP id 6F23714E7A
	for <freebsd-smp@FreeBSD.ORG>; Mon, 26 Jul 1999 02:30:39 -0700 (PDT)
	(envelope-from Joachim.Strombergson@emw.ericsson.se)
Received: from poem.emw.ericsson.se (poem.emw.ericsson.se [136.225.49.25])
	by penguin.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.3) with ESMTP id LAA05976;
	Mon, 26 Jul 1999 11:30:04 +0200 (MET DST)
Received: from biff.mo.emw.ericsson.se (biff.mo.emw.ericsson.se [136.225.83.24]) by poem.emw.ericsson.se (8.6.12/8.6.12) with ESMTP id LAA08639; Mon, 26 Jul 1999 11:30:03 +0200
Received: from stewart.mo.emw.ericsson.se (stewart.mo.emw.ericsson.se [136.225.229.138]) by biff.mo.emw.ericsson.se (8.8.8+Sun/SMI-SVR4-biff-1.0) with SMTP
	id LAA09307; Mon, 26 Jul 1999 11:30:01 +0200 (MET DST)
Received: from emw.ericsson.se (localhost [127.0.0.1]) by stewart.mo.emw.ericsson.se (SMI-8.6/SMI-SVR4-esunix-1.3) with ESMTP
	id LAA10047; Mon, 26 Jul 1999 11:30:00 +0200
Message-ID: <379C2A98.73172686@emw.ericsson.se>
Date: Mon, 26 Jul 1999 11:30:00 +0200
From: Joachim Strombergson <Joachim.Strombergson@emw.ericsson.se>
Organization: Ericsson Microwave Systems
X-Mailer: Mozilla 4.08C-EMW [en] (X11; I; SunOS 5.5.1 sun4u)
MIME-Version: 1.0
To: Fabio Cesar Gozzo <fabio@iqm.unicamp.br>,
	"freebsd-smp@FreeBSD.ORG" <freebsd-smp@FreeBSD.ORG>
Subject: Re: Dual PIII motherboard
References: <199907232039.RAA20231@thomson.iqm.unicamp.br> <19990726121814.C38516@myhakas.matti.ee>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by biff.mo.emw.ericsson.se id LAA09307
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Aloha!

Vallo Kallaste wrote:
> On Fri, Jul 23, 1999 at 05:39:32PM -0300, Fabio Cesar Gozzo <fabio@iqm.=
unicamp.br> wrote:
> > Hi,
> > I'm planning to buy a dual PIII 550 Mhz and I am
> > looking for advices on manufacturer/model.
> > I've been using ASUS already, but I was browsing their home
> > pages and didn't find a dual board supporting 550 Mhz processors.
> > I found an Intel board, but I have seen people complaining
> > about the on board NCR SCSI.
> > Any suggestions ?
> > Thank you,
>=20
> How about Tyan S1837UANG "Thunderbolt" ? It's excellent board.

I bought the amazing ABIT BP6 Dual Celeron MB this saturday with two
Celeron 366 PPGAs. It runs several SETIs in FreeBSD SMP at home right
now. Also, I got it to boot and run for ~4 hours in 2*550MHz! In short:
Want a cheap SMP system that works with FreeBSD, get the ABIT BP6 and
some Celerons.

--=20
Med v=E4nlig h=E4lsning, Yours

Joachim Str=F6mbergson - Alltid i harmonisk sv=E4ngning
---------------- Ericsson Microwave Systems AB -----------------
Joachim Str=F6mbergson            http://www.ericsson.se/microwave
     ASIC System on Silicon engineer, nice to CUTE animals.   =20
* Opinions above, expressed or implicit, are strictly personal *
------------- Spamfodder: regeringen@regeringen.se -------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Mon Jul 26 10:13:11 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from horst.bfd.com (horst.bfd.com [12.9.219.10])
	by hub.freebsd.org (Postfix) with ESMTP id 9483114D27
	for <freebsd-smp@FreeBSD.ORG>; Mon, 26 Jul 1999 10:13:07 -0700 (PDT)
	(envelope-from ejs@bfd.com)
Received: from HARLIE.bfd.com (bastion.bfd.com [12.9.219.14])
	by horst.bfd.com (8.9.2/8.9.2) with ESMTP id KAA31775;
	Mon, 26 Jul 1999 10:12:37 -0700 (PDT)
	(envelope-from ejs@bfd.com)
Date: Mon, 26 Jul 1999 10:12:37 -0700 (PDT)
From: "Eric J. Schwertfeger" <ejs@bfd.com>
To: Joachim Strombergson <Joachim.Strombergson@emw.ericsson.se>
Cc: Fabio Cesar Gozzo <fabio@iqm.unicamp.br>,
	"freebsd-smp@FreeBSD.ORG" <freebsd-smp@FreeBSD.ORG>
Subject: Re: Dual PIII motherboard
In-Reply-To: <379C2A98.73172686@emw.ericsson.se>
Message-ID: <Pine.BSF.4.05.9907261004270.15272-100000@harlie.bfd.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Mon, 26 Jul 1999, Joachim Strombergson wrote:

> I bought the amazing ABIT BP6 Dual Celeron MB this saturday with two
> Celeron 366 PPGAs. It runs several SETIs in FreeBSD SMP at home right
> now. Also, I got it to boot and run for ~4 hours in 2*550MHz! In short:
> Want a cheap SMP system that works with FreeBSD, get the ABIT BP6 and
> some Celerons.

I did the same thing this weekend, but am having minor problems, probably
heat related (sig 11 after an hour or so of makedepend/make world in
single-CPU mode). The more cautious may want to go with 333s.  I would
have, but couldn't find OEM 333s, only retail, and Las Vegas is dusty
enough that most fans only last a year at best. Still more heatsink/grease
combo's to try, so I haven't given up on 550, but I'll be happy at
dual-510, quite the jump from dual-PPro200(512k cache). (Yes, I know
overclocking is not for everyone, and certainly not for anyone that isn't
willing to experiment alot to get a stable system).

Now if only there were a way to get the temp/fan RPM data from within
freebsd, so I don't have to reboot to check the CPU temp while I'm
stress-testing :-)  I remember some discussion about that on one of the
other lists, but don't remember there being an answer, and can't even
remember if there is a standard for the hardware interface for that kind
of info.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Mon Jul 26 11:46:59 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90])
	by hub.freebsd.org (Postfix) with ESMTP id 0C7D214BDC
	for <freebsd-smp@freebsd.org>; Mon, 26 Jul 1999 11:46:51 -0700 (PDT)
	(envelope-from tom@embt.com)
Received: from paranor.embt.net (timembt.iinc.com [206.67.169.229])
	by mercury.gfit.net (8.8.8/8.8.8) with SMTP id NAA01426
	for <freebsd-smp@freebsd.org>; Mon, 26 Jul 1999 13:47:29 -0500 (CDT)
	(envelope-from tom@embt.com)
Message-Id: <3.0.3.32.19990726144556.007571b8@mail.embt.com>
X-Sender: tembt@mail.embt.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Mon, 26 Jul 1999 14:45:56 -0400
To: freebsd-smp@freebsd.org
From: Tom Embt <tom@embt.com>
Subject: SMP kernel on dual board with single proc?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Is it possible to build & run an SMP kernel on a DP board with only one CPU
installed?  I know this is kind of a silly thing to do but I was just
wondering if it is possible.

I tried it on my BP6, but got a "panic: NO BSP found!" or something like
that on boot.  If this is indeed possible I can give it another go, and
post my mptable, dmesg, and kernel conf.



Tom Embt
tom@embt.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Mon Jul 26 11:48:55 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP id 14F9214D5B
	for <freebsd-smp@FreeBSD.ORG>; Mon, 26 Jul 1999 11:48:53 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id LAA48210;
	Mon, 26 Jul 1999 11:48:36 -0700 (PDT)
	(envelope-from dillon)
Date: Mon, 26 Jul 1999 11:48:36 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199907261848.LAA48210@apollo.backplane.com>
To: Tom Embt <tom@embt.com>
Cc: freebsd-smp@FreeBSD.ORG
Subject: Re: SMP kernel on dual board with single proc?
References:  <3.0.3.32.19990726144556.007571b8@mail.embt.com>
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

:Is it possible to build & run an SMP kernel on a DP board with only one CPU
:installed?  I know this is kind of a silly thing to do but I was just
:wondering if it is possible.
:
:I tried it on my BP6, but got a "panic: NO BSP found!" or something like
:that on boot.  If this is indeed possible I can give it another go, and
:post my mptable, dmesg, and kernel conf.
:
:Tom Embt
:tom@embt.com

    It should work just fine, simply compile and run a UP kernel on it
    (or perhaps an SMP kernel with NCPU set to 1).  A number of machines 
    at a company I consult for run UP kernels on SMP boxes with only one cpu
    populated.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Mon Jul 26 11:49: 4 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from hotmail.com (f314.hotmail.com [207.82.251.227])
	by hub.freebsd.org (Postfix) with SMTP id 4126A150BC
	for <freebsd-smp@FreeBSD.ORG>; Mon, 26 Jul 1999 11:48:54 -0700 (PDT)
	(envelope-from the_hermit665@hotmail.com)
Received: (qmail 36454 invoked by uid 0); 26 Jul 1999 18:48:48 -0000
Message-ID: <19990726184848.36453.qmail@hotmail.com>
Received: from 216.160.92.86 by www.hotmail.com with HTTP;
	Mon, 26 Jul 1999 11:48:48 PDT
X-Originating-IP: [216.160.92.86]
Reply-To: the_hermit665@hotmail.com
From: "Cosmic 665" <the_hermit665@hotmail.com>
To: freebsd-smp@FreeBSD.ORG
Subject: Overclocking
Date: Mon, 26 Jul 1999 11:48:48 PDT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

It's awsome to hear all the stories about overclocking...  but how stable is 
overclocking "in reality"???   I'm not saying this to be a jerk or anything 
but how much work could & should a CPU take at +50-75% it's clocked state 
(especially a SMP system)??   How long could you run a CPU overclocked, or 
if any of you guys are overclocking what's the longest a system has lasted 
(in years or months)???  I got an ASUS P2B 5A and I was thinking about 
(Maybe) overclocking the 333Mhz chip...  but then again I can't risk buying 
another MB or cpu if I screw up the computer :P


-cosmic-665


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Mon Jul 26 11:50:37 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from wank.necropolis.org (wank.necropolis.org [207.246.128.93])
	by hub.freebsd.org (Postfix) with ESMTP id EB43114FAA
	for <freebsd-smp@FreeBSD.ORG>; Mon, 26 Jul 1999 11:50:35 -0700 (PDT)
	(envelope-from todd@wank.necropolis.org)
Received: from localhost (todd@localhost)
	by wank.necropolis.org (8.9.3/8.9.3) with ESMTP id LAA44432;
	Mon, 26 Jul 1999 11:49:40 -0700 (PDT)
	(envelope-from todd@wank.necropolis.org)
Date: Mon, 26 Jul 1999 11:49:40 -0700 (PDT)
From: Todd Backman <todd@wank.necropolis.org>
To: Tom Embt <tom@embt.com>
Cc: freebsd-smp@FreeBSD.ORG
Subject: Re: SMP kernel on dual board with single proc?
In-Reply-To: <3.0.3.32.19990726144556.007571b8@mail.embt.com>
Message-ID: <Pine.BSF.4.10.9907261148550.44358-100000@wank.necropolis.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


I do not think so.

On Mon, 26 Jul 1999, Tom Embt wrote:

> Is it possible to build & run an SMP kernel on a DP board with only one CPU
> installed?  I know this is kind of a silly thing to do but I was just
> wondering if it is possible.
> 
> I tried it on my BP6, but got a "panic: NO BSP found!" or something like
> that on boot.  If this is indeed possible I can give it another go, and
> post my mptable, dmesg, and kernel conf.
> 
> 
> 
> Tom Embt
> tom@embt.com
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-smp" 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  Mon Jul 26 11:59: 6 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91])
	by hub.freebsd.org (Postfix) with ESMTP id D9C0014CC2
	for <freebsd-smp@FreeBSD.ORG>; Mon, 26 Jul 1999 11:59:04 -0700 (PDT)
	(envelope-from nate@mt.sri.com)
Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100])
	by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA29886;
	Mon, 26 Jul 1999 12:57:09 -0600 (MDT)
	(envelope-from nate@rocky.mt.sri.com)
Received: by mt.sri.com (SMI-8.6/SMI-SVR4)
	id MAA20179; Mon, 26 Jul 1999 12:57:08 -0600
Date: Mon, 26 Jul 1999 12:57:08 -0600
Message-Id: <199907261857.MAA20179@mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Tom Embt <tom@embt.com>
Cc: freebsd-smp@FreeBSD.ORG
Subject: Re: SMP kernel on dual board with single proc?
In-Reply-To: <3.0.3.32.19990726144556.007571b8@mail.embt.com>
References: <3.0.3.32.19990726144556.007571b8@mail.embt.com>
X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> Is it possible to build & run an SMP kernel on a DP board with only one CPU
> installed?  I know this is kind of a silly thing to do but I was just
> wondering if it is possible.

Works fine.  As a matter of fact, I'm sitting in front of one right
now.  The second CPU has been sitting next to me for about 5 months, but
I never get time to install it, and besides most of my development is
done on 2.2.8 which doesn't support SMP..




Nate


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Mon Jul 26 12:43:56 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from horst.bfd.com (horst.bfd.com [12.9.219.10])
	by hub.freebsd.org (Postfix) with ESMTP id 6FEC014DB5
	for <freebsd-smp@FreeBSD.ORG>; Mon, 26 Jul 1999 12:43:54 -0700 (PDT)
	(envelope-from ejs@bfd.com)
Received: from HARLIE.bfd.com (bastion.bfd.com [12.9.219.14])
	by horst.bfd.com (8.9.2/8.9.2) with ESMTP id MAA33241;
	Mon, 26 Jul 1999 12:43:53 -0700 (PDT)
	(envelope-from ejs@bfd.com)
Date: Mon, 26 Jul 1999 12:43:53 -0700 (PDT)
From: "Eric J. Schwertfeger" <ejs@bfd.com>
To: Cosmic 665 <the_hermit665@hotmail.com>
Cc: freebsd-smp@FreeBSD.ORG
Subject: Re: Overclocking
In-Reply-To: <19990726184848.36453.qmail@hotmail.com>
Message-ID: <Pine.BSF.4.05.9907261205510.17960-100000@harlie.bfd.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Mon, 26 Jul 1999, Cosmic 665 wrote:

> It's awsome to hear all the stories about overclocking...  but how stable is 
> overclocking "in reality"???   I'm not saying this to be a jerk or anything 
> but how much work could & should a CPU take at +50-75% it's clocked state 
> (especially a SMP system)??   How long could you run a CPU overclocked, or 
> if any of you guys are overclocking what's the longest a system has lasted 
> (in years or months)???  I got an ASUS P2B 5A and I was thinking about 
> (Maybe) overclocking the 333Mhz chip...  but then again I can't risk buying 
> another MB or cpu if I screw up the computer :P

I'm an overclocker from way back.  The first overclocked CPU I ever dealt
with was a 386DX-16 that ran at 25Mhz without a single glitch until long
after a 386DX25 was useful for anything.

Much of the practicality of overclocking comes from the family of chips.
The same fabrication process is used for PPGA Celerons from 333mhz up to
the latest 500mhz, so I wouldn't expect you to damage CPU or motherboard
overclocking a PPGA 333 by 50%, as long as you didn't tweak the voltage in
order to make it run. It may not work, but I don't think you'd damage
anything.  On the other hand, even the bottom-of-the-line PIII, at 450mhz,
isn't going to overclock far, since the fastest in that family is 
currently 550mhz.  The fact that 100mhz front-side-bus machines have
nowhere to go that isn't overclocking the PCI bus on many
motherboards probably doesn't help either.

Oh, and I consider 50% to be the high end of usable overclocking, and
even that depends on where you're starting from. I know that there are
people that get more, but they don't do it with anything resembling normal
CPU fans, have to hand-pick parts, etc.

Overclocking is not something that I recommend to everyone.  In fact, 
I refused to overclock anything that I sold (used to sell hardware) or 
consult on unless the customer specifically requested it and understood
what it meant. Small amounts here and there might be a no-brainer, but it
really does take time and effort to make higher amounts of overclocking
stable.  I'm guessing I'm going to be tweaking my machine for a week at
least before I'm happy that I've gotten as much as I safely can out of it.
I'm hoping to find a combination that is happy at 550mhz, but failing that
506mhz with a  Memory clock of 92mhz and a PCI clock of 31mhz will keep me
quite happy. (92 mhz is a magic number, as the PCI clock divider drops at
91mhz, and I don't want to run the PCI bus at 45.5mhz.  Surprized ABIT
doesn't let me set the PCI divider myself).  

As far as stability goes, I usually test my machines with a 24 hour
"make world" loop.  I've never had a CPU pass that test, and then flake
out at a later date.  The longest-overclocked CPU's I'm currently using
are some PPro 150s that are completely happy at 180 over 3 years later,
though they wouldn't make world at 200, even brand new.  I've got friends
using Pentium 166's at 266, K6-2 233's at 300, etc, that have all been in
use at least a year.

There are things to watch out for.  UDMA drives quite often have a
conniption if your PCI bus is clocked higher than 33.33mhz, and some PCI
cards don't like that either.  Another thing to watch is your AGP clock,
if you're using an AGP video card.

And one thing to keep in mind is that I'm saving less than $150 by
spending all this time fussing with overclocking as compared to just
buying 2 466 Celerons.  I'm mostly doing this just for the sick twisted
sense of having spent less than $400 for something that will be about 
twice as fast as anything we have at work. (Including Marketing's new PIII
:-)

For more advice, I'd suggest checking out some of the hardware sites,
there are even a few dedicated to overclocking.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Mon Jul 26 12:59:54 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id D825714C82
	for <freebsd-smp@FreeBSD.ORG>; Mon, 26 Jul 1999 12:59:49 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA55721;
	Mon, 26 Jul 1999 21:58:22 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: "Eric J. Schwertfeger" <ejs@bfd.com>
Cc: Cosmic 665 <the_hermit665@hotmail.com>, freebsd-smp@FreeBSD.ORG
Subject: Re: Overclocking 
In-reply-to: Your message of "Mon, 26 Jul 1999 12:43:53 PDT."
             <Pine.BSF.4.05.9907261205510.17960-100000@harlie.bfd.com> 
Date: Mon, 26 Jul 1999 21:58:21 +0200
Message-ID: <55719.933019101@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

In message <Pine.BSF.4.05.9907261205510.17960-100000@harlie.bfd.com>, "Eric J. 
Schwertfeger" writes:
>
>Much of the practicality of overclocking comes from the family of chips.
>The same fabrication process is used for PPGA Celerons from 333mhz up to
>the latest 500mhz, so I wouldn't expect you to damage CPU or motherboard
>overclocking a PPGA 333 by 50%, as long as you didn't tweak the voltage in
>order to make it run.

It can be said as simple as this:  "You Are Wrong".  Running the chip
at higher clock will lead to increased heat generation, which isn't a
good thing for your silicon.


Rule #1:
	Do not Overclock.

Rule #2:
	If you overclock, do not complain that things don't work.


--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Mon Jul 26 13:28:31 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from radius.wavefire.com (radius.workfire.net [139.142.95.252])
	by hub.freebsd.org (Postfix) with SMTP id C535014C40
	for <freebsd-smp@freebsd.org>; Mon, 26 Jul 1999 13:28:28 -0700 (PDT)
	(envelope-from swen@wavefire.com)
Received: (qmail 3369 invoked from network); 26 Jul 1999 20:41:24 -0000
Received: from unknown (HELO swen) (139.142.95.222)
  by radius.workfire.net with SMTP; 26 Jul 1999 20:41:24 -0000
Message-Id: <3.0.32.19990726132822.0096a660@mail.wavefire.com>
X-Sender: swen@mail.wavefire.com
X-Mailer: Windows Eudora Pro Version 3.0 (32)
Date: Mon, 26 Jul 1999 13:28:22 -0700
To: freebsd-smp@freebsd.org
From: Swen Kabis <swen@wavefire.com>
Subject: Re: Overclocking 
Mime-Version: 1.0
Content-Type: text/enriched; charset="us-ascii"
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

At 09:58 PM 7/26/99 +0200, you wrote:

>In message <<Pine.BSF.4.05.9907261205510.17960-100000@harlie.bfd.com>, "Eric J. 

>Schwertfeger" writes:

>>

>>Much of the practicality of overclocking comes from the family of chips.

>>The same fabrication process is used for PPGA Celerons from 333mhz up to

>>the latest 500mhz, so I wouldn't expect you to damage CPU or motherboard

>>overclocking a PPGA 333 by 50%, as long as you didn't tweak the voltage in

>>order to make it run.

>

>It can be said as simple as this:  "You Are Wrong".  Running the chip

>at higher clock will lead to increased heat generation, which isn't a

>good thing for your silicon.

>

>

>Rule #1:

>	Do not Overclock.

>

>Rule #2:

>	If you overclock, do not complain that things don't work.


If you have enough airflow in your machine, an overclock on a 333 up to 50% won't conceivably do any damage. But considering the state of computers nowadays, anything can happen.

I personally had a PII 366 die after 3 hours of running... just for the hell of it, so if you can overclock your machine and use some braincells when you do it... more power to you


Swen


 

<bold>~

-----BEGIN GEEK CODE BLOCK-----

GCS/O d-(+) s:+>:- a- C++++ UB++$>++++$ P+ L++>++++$ E--

W++(++) N+ o? K? w--- O- M-- V-- PS+ PE@ Y PGP t++ 5++ X

R* tv++ b+++(+) DI++ D+++ G++ e++ h---->$ r+++ x**

-----END GEEK CODE BLOCK-----</bold>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Mon Jul 26 13:40:25 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131])
	by hub.freebsd.org (Postfix) with ESMTP id 364A215027
	for <freebsd-smp@freebsd.org>; Mon, 26 Jul 1999 13:40:22 -0700 (PDT)
	(envelope-from tlambert@usr02.primenet.com)
Received: (from daemon@localhost)
	by smtp01.primenet.com (8.8.8/8.8.8) id NAA05433;
	Mon, 26 Jul 1999 13:39:45 -0700 (MST)
Received: from usr02.primenet.com(206.165.6.202)
 via SMTP by smtp01.primenet.com, id smtpd005396; Mon Jul 26 13:39:37 1999
Received: (from tlambert@localhost)
	by usr02.primenet.com (8.8.5/8.8.5) id NAA04652;
	Mon, 26 Jul 1999 13:39:35 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199907262039.NAA04652@usr02.primenet.com>
Subject: Re: SMP + XDM = keyboard lockup
To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA)
Date: Mon, 26 Jul 1999 20:39:35 +0000 (GMT)
Cc: bde@zeta.org.au, tlambert@primenet.com, freebsd-smp@freebsd.org,
	yokota@zodiac.mech.utsunomiya-u.ac.jp
In-Reply-To: <199907240817.RAA18855@zodiac.mech.utsunomiya-u.ac.jp> from "Kazutaka YOKOTA" at Jul 24, 99 05:17:28 pm
X-Mailer: ELM [version 2.4 PL25]
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

> >>2)	Why doesn't getty use O_EXCL on the open, such that if
> >>	it can't get an exclusive lock, it fails?  Worst case
> >
> >Perhaps because O_EXCL has no effect for devices under BSD (its effect
> >is implementation-defined except for regular files).
> 
> Isn't this O_EXLOCK rather than O_EXCL?  (open(2)) In any case, we
> don't seem to have exclusive lock for non-regular files. (flock(2))

No.  The "exclusive use bit" (O_EXCL) was used by the first HDB
(Honey-Dan-Ber) UUCP implemetnation, and with the first uugetty
implementation, in order to implement bidirectional tty use for
UUCP (and others).

Here are the (not so) gory details:

The lack of locking for non-regular files is an artifact of
non-regular vnodes being treated differently (struct fileops:
when a vnode isn't really a vnode).

The main problem is that the locks are hung, via VFS calls
which don't work in specfs, off the underlying backing objects
(e.g. a lock list pointer on the in-core copy of the FFS inode
for a file).  This doesn't work in specfs because it doesn't
have real direct access to the backing objects, and those backing
objects don't have a lock list pointer in their structures, anyway.

A (trivial) change to hang the lock list off the vnode instead
would enable both range and file (total available range) locks
on non-regular files (sockets, FIFO's, devices, etc.).

You would then need to either implement VOP_ADVLOCK in specfs,
or you would need to move the locking to a higher layer.  Doing
the latter is problematic because of a desire for future support
for working NFS locking: you still need procedural hooks in NFS
to assert the lock request over the wire to the server.

The way to get around that particular thorn is to move the
VOP_ADVLOCK from a commit-based to a veto-based interface.  Then
everyone (but NFS, for right now) would just say "approved" to
the upper level code.

For this to work, you need to assert the lock locally, but not
coelesce it until everyone has "approved" it, so you can back
it out (if you do not do this, then you can't back it out,
since asserting it would result in possible "upgrades" or
"downgrades" of lock [R -> W], [W -> R], if the locks were
coelesced before a "veto" occurred).

Pretty simple, really.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Mon Jul 26 19:48:57 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP id 1567F150CB
	for <freebsd-smp@FreeBSD.ORG>; Mon, 26 Jul 1999 19:48:51 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id TAA49515;
	Mon, 26 Jul 1999 19:47:33 -0700 (PDT)
	(envelope-from dillon)
Date: Mon, 26 Jul 1999 19:47:33 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199907270247.TAA49515@apollo.backplane.com>
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: "Eric J. Schwertfeger" <ejs@bfd.com>,
	Cosmic 665 <the_hermit665@hotmail.com>, freebsd-smp@FreeBSD.ORG
Subject: Re: Overclocking 
References:  <55719.933019101@critter.freebsd.dk>
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

    This is how fabs generally work in regards to chip speeds:

    * The fab makes a chip

    * The chip is tested.  Due to doping inconsistancies and other issues
      the chips that come off the fab will only test to certain speeds.

    * The chips are placed into buckets based on how fast they test to.

    But then marketing and distribution come into play.  In recent years fabs
    have gotten a lot more reliable and this has resulted in higher and better
    yields.

    So lets say in a 10000 lot Intel winds up with 8000 chips that test to
    500MHz and 2000 that test to 400MHz.  But lets also say that Intel needs
    to ship 5000 500MHz chips and 5000 400MHz chips.  What Intel (and all
    chip manufacturers) will do is throw some of the higher-testing chips 
    into the lower-MHz rating in order to cover their orders.

    When you purchase a 400Mhz chip all you are guarenteed is that it can run
    at 400MHz.  It is possible that your chip was tested to 500MHz but you
    can't tell for sure.  Intel's FAB has gotten good enough that they 
    physically changed the celeron design in order to be able to laser or
    PROM a limit to the frequency multiplier to prevent people from 
    overclocking the chips after people found out that they could do it
    reliably.

    Now, this is why you *DON'T* want to overclock:

    When a chip is tested the frequency limit is determined by a number of
    factors both internal and external.  For example, a single line within
    the register file or a single bit in the cache might be just a tad too
    slow and limit the overall frequency the chip can sustain.  Or it could be
    an external signal that doesn't quite meet spec above a certain frequency.

    The problem is that usually the failure is something relatively minor in
    the chip, but which can have major consequences to the execution of
    instructions.  Worse, the failure condition is not necessarily reliably
    reproduceable.  You may believe that your overclocked chip is working
    correctly, but there is a good chance that it isn't, quite.  If you 
    overclock a chip you can wind up with wierd failures that take days
    or even weeks to show up, or failures that show up as arithmatic 
    miscalculations.  For example, the FP unit might begin to produce
    slightly incorrect results, or certain L1 cache situations might fail
    to the produce the correct data (this was a serious problem with a lot
    of 486's that Intel inadequately tested.  They would work fine w/ Windows,
    but would fail under UNIX because UNIX utilized chip features that would
    tickle the cache bugs).

    In regards to heat dissipation:  Heat dissipation is not usually a 
    problem when you are overclocking a chip but still leave it under the
    maximum clock rating that the manufacturer makes, at least as long as
    the package type remains the same as the package type the manufacturer
    uses in their high-end products.  I think for most Intel cpu's the package
    type is the same for nearly all speed grades of a particular chip class.

    If you overclock a chip beyond the maximum rating sold by the manufacturer
    in the package type in question, you *can* melt it.  Overheating also
    introduces additional noise on the die and, even worse, may cause the
    gates making up the die to slow down.  Thus some people see chips "fail"
    after being on for a period of time, and then work again after the 
    computer's been off for a while.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>

:In message <Pine.BSF.4.05.9907261205510.17960-100000@harlie.bfd.com>, "Eric J. 
:Schwertfeger" writes:
:>
:>Much of the practicality of overclocking comes from the family of chips.
:>The same fabrication process is used for PPGA Celerons from 333mhz up to
:>the latest 500mhz, so I wouldn't expect you to damage CPU or motherboard
:>overclocking a PPGA 333 by 50%, as long as you didn't tweak the voltage in
:>order to make it run.
:
:It can be said as simple as this:  "You Are Wrong".  Running the chip
:at higher clock will lead to increased heat generation, which isn't a
:good thing for your silicon.
:
:
:Rule #1:
:	Do not Overclock.
:
:Rule #2:
:	If you overclock, do not complain that things don't work.
:
:
:--
:Poul-Henning Kamp             FreeBSD coreteam member
:phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
:FreeBSD -- It will take a long time before progress goes too far!
:
:
:To Unsubscribe: send mail to majordomo@FreeBSD.org
:with "unsubscribe freebsd-smp" 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 Jul 27  3:56:43 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7])
	by hub.freebsd.org (Postfix) with ESMTP id DC42D14D11
	for <freebsd-smp@FreeBSD.ORG>; Tue, 27 Jul 1999 03:56:34 -0700 (PDT)
	(envelope-from peter@netplex.com.au)
Received: from netplex.com.au (localhost [127.0.0.1])
	by overcee.netplex.com.au (Postfix) with ESMTP
	id C228D1C9E; Tue, 27 Jul 1999 18:56:33 +0800 (WST)
	(envelope-from peter@netplex.com.au)
X-Mailer: exmh version 2.0.2 2/24/98
To: Nate Williams <nate@mt.sri.com>
Cc: Tom Embt <tom@embt.com>, freebsd-smp@FreeBSD.ORG
Subject: Re: SMP kernel on dual board with single proc? 
In-reply-to: Your message of "Mon, 26 Jul 1999 12:57:08 CST."
             <199907261857.MAA20179@mt.sri.com> 
Date: Tue, 27 Jul 1999 18:56:33 +0800
From: Peter Wemm <peter@netplex.com.au>
Message-Id: <19990727105633.C228D1C9E@overcee.netplex.com.au>
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Nate Williams wrote:
> > Is it possible to build & run an SMP kernel on a DP board with only one CPU
> > installed?  I know this is kind of a silly thing to do but I was just
> > wondering if it is possible.
> 
> Works fine.  As a matter of fact, I'm sitting in front of one right
> now.  The second CPU has been sitting next to me for about 5 months, but
> I never get time to install it, and besides most of my development is
> done on 2.2.8 which doesn't support SMP..

Yes, but that's not what he asked.  He wanted to know if a SMP kernel worked
on a SMP motherboard with one CPU, not if a UP kernel works on a 1 cpu SMP 
motherboard.

I have never tried it, I don't know.  (and can't easily get to a machine to
find out since they are at the bottom of a stack)

> Nate

Cheers,
-Peter



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Tue Jul 27  9:40:44 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP id CA190152AA
	for <freebsd-smp@FreeBSD.ORG>; Tue, 27 Jul 1999 09:40:40 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id JAA54559;
	Tue, 27 Jul 1999 09:39:43 -0700 (PDT)
	(envelope-from dillon)
Date: Tue, 27 Jul 1999 09:39:43 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199907271639.JAA54559@apollo.backplane.com>
To: Peter Wemm <peter@netplex.com.au>
Cc: Nate Williams <nate@mt.sri.com>, Tom Embt <tom@embt.com>,
	freebsd-smp@FreeBSD.ORG
Subject: Re: SMP kernel on dual board with single proc? 
References:  <19990727105633.C228D1C9E@overcee.netplex.com.au>
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

:
:Yes, but that's not what he asked.  He wanted to know if a SMP kernel worked
:on a SMP motherboard with one CPU, not if a UP kernel works on a 1 cpu SMP 
:motherboard.
:
:I have never tried it, I don't know.  (and can't easily get to a machine to
:find out since they are at the bottom of a stack)
:
:> Nate
:
:Cheers,
:-Peter

    Since you have to modify NCPU anyway, I don't see there being much of
    a difference between compiling up an SMP kernel with NCPU=1, and compiling
    up a UP kernel.  I think the question was (and the author can correct me
    if I'm wrong), simply whether it was possible to run FreeBSD on a 
    duel-cpu motherboard which only had one cpu populated.  The answer is yes.

    There is a 'plug' you need to stick into the unused cpu slot, which should
    have come with the motherboard, but that's the only issue I know of.

						-Matt



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Tue Jul 27 11:25:23 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16])
	by hub.freebsd.org (Postfix) with ESMTP id 79A9E14DB7
	for <freebsd-smp@FreeBSD.ORG>; Tue, 27 Jul 1999 11:25:17 -0700 (PDT)
	(envelope-from maniattb@cs.rpi.edu)
Received: from cs.rpi.edu (maniattb@dishwasher.cs.rpi.edu [128.213.8.31])
	by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA65142;
	Tue, 27 Jul 1999 14:24:53 -0400 (EDT)
Message-Id: <199907271824.OAA65142@cs.rpi.edu>
X-Mailer: exmh version 2.0.1 12/23/97
To: freebsd-smp@FreeBSD.ORG
Cc: maniattb@cs.rpi.edu
Subject: Dual Processor Motherboards
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 27 Jul 1999 14:24:50 -0400
From: Bill Maniatty <maniattb@cs.rpi.edu>
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hello There:

I apologize if you have seen this already in freebsd-hardware, but
I thought this forum might be appropriate for this sort of discussion
as well.

I was looking to make an affordable, yet high performance home machine
using a dual processor board.  I want to be able to run the most recent
stable release, and was going to get Intel based processors.  I would
like the processors to be fairly speedy, say 400-500 MHZ.  Since I'm going
to live with the system for quite a while, I might want it to be kind
of fast (but not prohibitively expensive).

I had the following questions:
1) Do people have specific recommendations about boards to buy/don't buy?
2) A local vendor is pushing Soyo boards at a $239 which is below the $400+
   prices I have seen quoted for an AsusTek P2B-DS board.  I assume they
   mean a SY-D6IBA or SY-D6IBA2.  Anybody have any experiences with such
   a board?
3) Multiple people in the hardware mailing list suggested the ABIT BP6 for
   dual Celeron machines (overclocking 300 MHZ processors).  Another also
   mentioned (but had not tried) the MSI 6120 board.

Regards:

Bill Maniatty
-- 
------------------------------------
Dr. William (Bill) A. Maniatty
Assistant Professor
Department of Computer Science
University at Albany
Albany, NY 12222
e-mail (at RPI): maniattb@cs.rpi.edu
e-mail (at SUNYA): maniatty@cs.albany.edu 
URL: http://www.cs.rpi.edu/~maniattb
-------------------------------------




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Tue Jul 27 12:19:10 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252])
	by hub.freebsd.org (Postfix) with ESMTP id 7457215289
	for <freebsd-smp@FreeBSD.ORG>; Tue, 27 Jul 1999 12:18:58 -0700 (PDT)
	(envelope-from olli@dorifer.heim3.tu-clausthal.de)
Received: (from olli@localhost)
	by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA05590
	for freebsd-smp@FreeBSD.ORG; Tue, 27 Jul 1999 21:17:28 +0200 (CEST)
	(envelope-from olli)
Date: Tue, 27 Jul 1999 21:17:28 +0200 (CEST)
From: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>
Message-Id: <199907271917.VAA05590@dorifer.heim3.tu-clausthal.de>
To: freebsd-smp@FreeBSD.ORG
Subject: Re: SMP kernel on dual board with single proc?
Organization: Administration Heim 3
Reply-To: freebsd-smp@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: TIN [version 1.2 RZTUC(3) PL2]
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Once I booted an SMP kernel (with NCPU=2) on an SMP board with
only one processor installed.  It worked fine.  Obviously, it
automatically reverts to single-processor if only one is
detected, instead of trying to schedule processes on the slot1
terminator.  ;-)

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
                                         (Terry Pratchett)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Tue Jul 27 12:23:59 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145])
	by hub.freebsd.org (Postfix) with ESMTP id 02B751522A
	for <freebsd-smp@FreeBSD.ORG>; Tue, 27 Jul 1999 12:23:57 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00538
	for <freebsd-smp@FreeBSD.ORG>; Tue, 27 Jul 1999 12:18:46 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199907271918.MAA00538@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: freebsd-smp@FreeBSD.ORG
Subject: Re: SMP kernel on dual board with single proc? 
In-reply-to: Your message of "Tue, 27 Jul 1999 21:17:28 +0200."
             <199907271917.VAA05590@dorifer.heim3.tu-clausthal.de> 
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Tue, 27 Jul 1999 12:18:45 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> =

> Once I booted an SMP kernel (with NCPU=3D2) on an SMP board with
> only one processor installed.  It worked fine.  Obviously, it
> automatically reverts to single-processor if only one is
> detected, instead of trying to schedule processes on the slot1
> terminator.  ;-)

Until extremely recently, this would not have worked.  If you recall =

doing this more than a few weeks ago, your recollection is faulty.

-- =

\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Tue Jul 27 12:42:39 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252])
	by hub.freebsd.org (Postfix) with ESMTP id 155F914C1B
	for <freebsd-smp@FreeBSD.ORG>; Tue, 27 Jul 1999 12:42:26 -0700 (PDT)
	(envelope-from olli@dorifer.heim3.tu-clausthal.de)
Received: (from olli@localhost)
	by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA06647
	for freebsd-smp@FreeBSD.ORG; Tue, 27 Jul 1999 21:41:42 +0200 (CEST)
	(envelope-from olli)
Date: Tue, 27 Jul 1999 21:41:42 +0200 (CEST)
From: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>
Message-Id: <199907271941.VAA06647@dorifer.heim3.tu-clausthal.de>
To: freebsd-smp@FreeBSD.ORG
Subject: SMP on Gigabyte 6BXD -- works
Organization: Administration Heim 3
Reply-To: freebsd-smp@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: TIN [version 1.2 RZTUC(3) PL2]
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hi,

The SMP web page at www.freebsd.org invites to send reports
about working hardware to the freebsd-smp list, so here is my
report.  If there's anyone in charge of maintaing the list of
working SMP hardware on the web site, he/she can add this.

Mainboard:   Gigabyte 6BXD (intel 440BX chipset, 2 x slot1)
Processors:  2 x Celeron-466, using MSI-6905 slot adapters

make -j 8 buildworld (with -O -pipe and NOSUIDPERL, /usr/src in
an MFS, /usr/obj on an IBM DCAS (Fast-SCSI, 5400 rpm) with
soft-updates enabled):
   2741.92s user  1331.91s system  147% cpu  45:56.80 total

I also used an MSI-6120N mainboard instead of the Gigabyte one
for some time, but it had a somewhat worse memory bandwidth.
So if you have to choose between Gigabyte and MSI, then get a
Gigabyte mainboard.

Furthermore, I had both Celerons (Celeroni?) running at 525 MHz
(75 instead of 66 MHz FSB) for a few weeks, it was rock-stable
(I guess I was lucky to get two "good" ones).
However, I "downgraded" back to the native 466 MHz because the
box will go into serious use soon, and reliability is the most
important thing.  The above buildworld was done at the normal
clockrate of 466 MHz, of course.

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
                                         (Terry Pratchett)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Tue Jul 27 12:51:12 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252])
	by hub.freebsd.org (Postfix) with ESMTP id AFE3115384
	for <freebsd-smp@FreeBSD.ORG>; Tue, 27 Jul 1999 12:51:04 -0700 (PDT)
	(envelope-from olli@dorifer.heim3.tu-clausthal.de)
Received: (from olli@localhost)
	by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA06932
	for freebsd-smp@FreeBSD.ORG; Tue, 27 Jul 1999 21:50:56 +0200 (CEST)
	(envelope-from olli)
Date: Tue, 27 Jul 1999 21:50:56 +0200 (CEST)
From: Oliver Fromme <olli@dorifer.heim3.tu-clausthal.de>
Message-Id: <199907271950.VAA06932@dorifer.heim3.tu-clausthal.de>
To: freebsd-smp@FreeBSD.ORG
Subject: Re: SMP kernel on dual board with single proc?
Organization: Administration Heim 3
Reply-To: freebsd-smp@FreeBSD.ORG
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: TIN [version 1.2 RZTUC(3) PL2]
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Mike Smith wrote in list.freebsd-smp:
 > > Once I booted an SMP kernel (with NCPU=2) on an SMP board with
 > > only one processor installed.  It worked fine.  Obviously, it
 > > automatically reverts to single-processor if only one is
 > > detected, instead of trying to schedule processes on the slot1
 > > terminator.  ;-)
 > 
 > Until extremely recently, this would not have worked.  If you recall 
 > doing this more than a few weeks ago, your recollection is faulty.

No, not that long ago.

olli@dao-lin-hay:~> uname -a
FreeBSD dao-lin-hay.heim3.tu-clausthal.de 4.0-CURRENT FreeBSD
4.0-CURRENT #1: Mon Jul 19 06:52:57 CEST 1999
olli@dao-lin-hay.heim3.tu-clausthal.de:/usr/src/sys/compile/DAOLINHAY
i386

Regards
   Oliver

-- 
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de)

"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
                                         (Terry Pratchett)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Tue Jul 27 13:24:55 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32])
	by hub.freebsd.org (Postfix) with SMTP id 3E052154FE
	for <freebsd-smp@FreeBSD.ORG>; Tue, 27 Jul 1999 13:24:52 -0700 (PDT)
	(envelope-from dscheidt@enteract.com)
Received: (qmail 90432 invoked from network); 27 Jul 1999 20:24:36 -0000
Received: from shell-1.enteract.com (dscheidt@207.229.143.40)
  by pop3-3.enteract.com with SMTP; 27 Jul 1999 20:24:36 -0000
Date: Tue, 27 Jul 1999 15:24:35 -0500 (CDT)
From: David Scheidt <dscheidt@enteract.com>
To: Bill Maniatty <maniattb@cs.rpi.edu>
Cc: freebsd-smp@FreeBSD.ORG
Subject: Re: Dual Processor Motherboards
In-Reply-To: <199907271824.OAA65142@cs.rpi.edu>
Message-ID: <Pine.NEB.3.96.990727151552.5827B-100000@shell-1.enteract.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, 27 Jul 1999, Bill Maniatty wrote:

> I had the following questions:
> 1) Do people have specific recommendations about boards to buy/don't buy?
> 2) A local vendor is pushing Soyo boards at a $239 which is below the $400+
>    prices I have seen quoted for an AsusTek P2B-DS board.  I assume they
>    mean a SY-D6IBA or SY-D6IBA2.  Anybody have any experiences with such
>    a board?
> 3) Multiple people in the hardware mailing list suggested the ABIT BP6 for
>    dual Celeron machines (overclocking 300 MHZ processors).  Another also
>    mentioned (but had not tried) the MSI 6120 board.

There is also the Gigabyte 6XBD.  The  non-builtin SCSI versions can be had 
for less than $150.  Mine has been rock solid, running 2 PII -400s.  


David



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Tue Jul 27 13:42:12 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from allied.org (broken.ne.mediaone.net [24.218.77.215])
	by hub.freebsd.org (Postfix) with SMTP id 4FB771523E
	for <freebsd-smp@FreeBSD.ORG>; Tue, 27 Jul 1999 13:42:05 -0700 (PDT)
	(envelope-from j3@allied.org)
Received: (qmail 8231 invoked from network); 27 Jul 1999 21:40:10 -0000
Received: from dyn19.cello-us.com (HELO dimension-m166a) (208.212.48.52)
  by broken.ne.mediaone.net with SMTP; 27 Jul 1999 21:40:10 -0000
Message-Id: <3.0.6.32.19990727163928.008230d0@broken.ne.mediaone.net>
X-Sender: j3@broken.ne.mediaone.net
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Tue, 27 Jul 1999 16:39:28 -0400
To: David Scheidt <dscheidt@enteract.com>,
	Bill Maniatty <maniattb@cs.rpi.edu>
From: j3 <j3@allied.org>
Subject: Re: Dual Processor Motherboards
Cc: freebsd-smp@FreeBSD.ORG
In-Reply-To: <Pine.NEB.3.96.990727151552.5827B-100000@shell-1.enteract.c
 om>
References: <199907271824.OAA65142@cs.rpi.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>> I had the following questions:
>> 1) Do people have specific recommendations about boards to buy/don't buy?

I would reccomend against the Tyan Thunder 100.  Call it bad luck, but
through no fault of my own (misuse, trauma, etc) my SIXTH board in a year
is arriving tomorrow.  I have had 2 bad PS/2 Keyboard Ports, a failed PS/2
mouse port, a bad SCSI controller, and most recently a bad IDE controller.
Perhaps my reseller just got a bad batch, but this has been insane.

	-Jeff Casimir



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Tue Jul 27 14: 2:10 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90])
	by hub.freebsd.org (Postfix) with ESMTP id BE64E14E11
	for <freebsd-smp@freebsd.org>; Tue, 27 Jul 1999 14:02:02 -0700 (PDT)
	(envelope-from tom@embt.com)
Received: from paranor.embt.net (timembt.iinc.com [206.67.169.229])
	by mercury.gfit.net (8.8.8/8.8.8) with SMTP id QAA22674
	for <freebsd-smp@freebsd.org>; Tue, 27 Jul 1999 16:03:20 -0500 (CDT)
	(envelope-from tom@embt.com)
Message-Id: <3.0.3.32.19990727170147.0075e828@mail.embt.com>
X-Sender: tembt@mail.embt.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Tue, 27 Jul 1999 17:01:47 -0400
To: freebsd-smp@freebsd.org
From: Tom Embt <tom@embt.com>
Subject: Re: SMP kernel on dual board with single proc? 
In-Reply-To: <19990727105633.C228D1C9E@overcee.netplex.com.au>
References: <Your message of "Mon, 26 Jul 1999 12:57:08 CST."             <199907261857.MAA20179@mt.sri.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

At 06:56 PM 7/27/99 +0800, you wrote:
>Nate Williams wrote:
>> > Is it possible to build & run an SMP kernel on a DP board with only
one CPU
>> > installed?  I know this is kind of a silly thing to do but I was just
>> > wondering if it is possible.
>> 
>> Works fine.  As a matter of fact, I'm sitting in front of one right
>> now.  The second CPU has been sitting next to me for about 5 months, but
>> I never get time to install it, and besides most of my development is
>> done on 2.2.8 which doesn't support SMP..
>
>Yes, but that's not what he asked.  He wanted to know if a SMP kernel worked
>on a SMP motherboard with one CPU, not if a UP kernel works on a 1 cpu SMP 
>motherboard.
>

Correct, I am asking if it can be done with an _SMP_ kernel, I already run
a regular UP kernel on this board no problem (hence this is not a pressing
issue I was just wondering if it could be done).

Panic msg from bootup (copied by hand) :

panic: NO BSP found!
mp_lock = 00000009; cpuid = 0; lapic.id = 00000000
Automatic reboot in 15 seconds - press a key on the console to abort


Hardware:

Abit BP6 dual-Socket 370 mobo (great board, BTW)*
One SL36C Celeron 366 PPGA CPU populating the "CPU #1" socket
In BIOS: MPS version = 1.4

* The BP6 doesn't use any sort of terminator for the empty socket, and will
work with the CPU in either one


Snippet of kernel conf:

machine		"i386"
cpu			"I686_CPU"
ident		"PARANOR-072799a-S"	# <-- CHANGE THIS!!
maxusers	16

options		SMP
options		APIC_IO

options		NCPU=1
options		NBUS=3
options		NAPIC=1
options		NINTR=24


MPTable:


============================================================================
===

MPTable, version 2.0.15

----------------------------------------------------------------------------
---

MP Floating Pointer Structure:

  location:			BIOS
  physical address:		0x000f5b30
  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:		288
  version:			1.1
  checksum:			0xfc
  OEM ID:			'OEM00000'
  Product ID:			'PROD00000000'
  OEM table pointer:		0x00000000
  OEM table size:		0
  entry count:			29
  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	 6	 5	 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	 7:A	      2	  19
		INT	active-lo       level	     0	 9:A	      2	  19
		INT	active-lo       level	     0	19:A	      2	  18
		INT	active-lo       level	     0	19:B	      2	  18
		INT	active-lo       level	     1	 0:A	      2	  16
		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=1			# number of CPUs
#options		NBUS=3			# number of busses
#options		NAPIC=1			# number of IO APICs
#options		NINTR=24		# number of INTs

============================================================================
===




Shall I assume it is not possible to run an SMP kernel on this system w/o
another CPU?

Thanks,


Tom Embt
tom@embt.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Tue Jul 27 15:41:17 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from hotmail.com (f236.hotmail.com [207.82.251.127])
	by hub.freebsd.org (Postfix) with SMTP id 8A7D714F0F
	for <freebsd-smp@FreeBSD.ORG>; Tue, 27 Jul 1999 15:41:09 -0700 (PDT)
	(envelope-from the_hermit665@hotmail.com)
Received: (qmail 11371 invoked by uid 0); 27 Jul 1999 22:39:48 -0000
Message-ID: <19990727223948.11370.qmail@hotmail.com>
Received: from 216.160.92.86 by www.hotmail.com with HTTP;
	Tue, 27 Jul 1999 15:38:49 PDT
X-Originating-IP: [216.160.92.86]
Reply-To: the_hermit665@hotmail.com
From: "Cosmic 665" <the_hermit665@hotmail.com>
To: freebsd-smp@FreeBSD.ORG
Subject: Re: Dual Processor Motherboards
Date: Tue, 27 Jul 1999 15:38:49 PDT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org



> >> I had the following questions:
> >> 1) Do people have specific recommendations about boards to buy/don't 
>buy?
>
>I would reccomend against the Tyan Thunder 100.  Call it bad luck, but
>through no fault of my own (misuse, trauma, etc) my SIXTH board in a year
>is arriving tomorrow.  I have had 2 bad PS/2 Keyboard Ports, a failed PS/2
>mouse port, a bad SCSI controller, and most recently a bad IDE controller.
>Perhaps my reseller just got a bad batch, but this has been insane.
>
>	-Jeff Casimir


Add any ALTON's to the list as well...  DON'T get any board from 
www.pcwave.com or it's china distributor www.pcchips.com.  Not only do these 
boards suck I believe they contain invalid FCC id's.  They allways die in 
some way-shape-or form.  Also, the Dual-333Mhz (NON-Celeron.. tried that..) 
System I'm running often halts while loading the Kernel...  Dies *sometimes* 
when leaving X & dies when returning to X from a VC in X (that could be 
totally X related).  The voltage and I/O cards on most of the "Super Socket 
7's " *Like to die* after +90 days (just in time for the warranty to be up 
:P).  I've used a total of 8 of them... all but the Dual-CPU system I'm on 
now has failed... (knock on wood this one won't fail *There is a god ... 
there is a GOD :P*).  A dead giveaway on this motherboard is if the *BOX* 
says *MainBoard* Accross the side.... run... There's a Subliminal message to 
those letters that SAY "Mainboard & "Super Socket 7 accross the box"..  The 
hidden message is "DEAD-BOARD" and "SUPER FUCK-YOU-7"!!!!  sorry about the 
profanity :P ... this is only true...


don't get got.......


-Cosmic-665



______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Tue Jul 27 16:36:41 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134])
	by hub.freebsd.org (Postfix) with ESMTP id 893FC14F50
	for <freebsd-smp@FreeBSD.ORG>; Tue, 27 Jul 1999 16:36:37 -0700 (PDT)
	(envelope-from tlambert@usr01.primenet.com)
Received: (from daemon@localhost)
	by smtp04.primenet.com (8.8.8/8.8.8) id QAA01610;
	Tue, 27 Jul 1999 16:36:35 -0700 (MST)
Received: from usr01.primenet.com(206.165.6.201)
 via SMTP by smtp04.primenet.com, id smtpd001491; Tue Jul 27 16:36:25 1999
Received: (from tlambert@localhost)
	by usr01.primenet.com (8.8.5/8.8.5) id QAA02119;
	Tue, 27 Jul 1999 16:36:03 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199907272336.QAA02119@usr01.primenet.com>
Subject: Re: SMP kernel on dual board with single proc?
To: tom@embt.com (Tom Embt)
Date: Tue, 27 Jul 1999 23:36:02 +0000 (GMT)
Cc: freebsd-smp@FreeBSD.ORG
In-Reply-To: <3.0.3.32.19990727170147.0075e828@mail.embt.com> from "Tom Embt" at Jul 27, 99 05:01:47 pm
X-Mailer: ELM [version 2.4 PL25]
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

> >Yes, but that's not what he asked.  He wanted to know if a SMP kernel worked
> >on a SMP motherboard with one CPU, not if a UP kernel works on a 1 cpu SMP 
> >motherboard.
> 
> Correct, I am asking if it can be done with an _SMP_ kernel, I already run
> a regular UP kernel on this board no problem (hence this is not a pressing
> issue I was just wondering if it could be done).
> 
> Panic msg from bootup (copied by hand) :
> 
> panic: NO BSP found!

If you are using a slot-architecture board, then you need a
terminator in the empty slot.

In general, "BSP" means "Boot System Processor" and "AP" means
"Auxillary Processor" -- in other words, it thinks it can't
find the BIOS designated boot processor.

You may find that swapping slots fixes the problem (if, as Mike
Smith said, you are running a -current that is no more than two
weeks old).

For standard slot processers (e.g., my dual P90), the BIOS has
always given the right information to the BP (including the APIC
ID), so it has been rare that it would not run with one processor
removed (the last time was the first time somone kicked it up
from 2 to 4 processors).


> Shall I assume it is not possible to run an SMP kernel on this system w/o
> another CPU?

1)	How old is the build?

2)	Socket 370 = needs terminator, IIRC...


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Wed Jul 28  1:21: 9 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135])
	by hub.freebsd.org (Postfix) with ESMTP id B1BF914F47
	for <freebsd-smp@FreeBSD.ORG>; Wed, 28 Jul 1999 01:20:59 -0700 (PDT)
	(envelope-from vallo@matti.ee)
Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87])
	by solaris.matti.ee (8.9.3/8.9.3) with ESMTP id LAA08224;
	Wed, 28 Jul 1999 11:20:22 +0300 (EET DST)
Received: by myhakas.matti.ee (Postfix, from userid 1000)
	id 6930E96; Wed, 28 Jul 1999 11:20:25 +0300 (EEST)
Date: Wed, 28 Jul 1999 11:20:25 +0300
From: Vallo Kallaste <vallo@matti.ee>
To: j3 <j3@allied.org>
Cc: David Scheidt <dscheidt@enteract.com>,
	Bill Maniatty <maniattb@cs.rpi.edu>, freebsd-smp@FreeBSD.ORG
Subject: Re: Dual Processor Motherboards
Message-ID: <19990728112025.A74699@myhakas.matti.ee>
Reply-To: vallo@matti.ee
References: <199907271824.OAA65142@cs.rpi.edu> <Pine.NEB.3.96.990727151552.5827B-100000@shell-1.enteract.c om> <3.0.6.32.19990727163928.008230d0@broken.ne.mediaone.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <3.0.6.32.19990727163928.008230d0@broken.ne.mediaone.net>; from j3 on Tue, Jul 27, 1999 at 04:39:28PM -0400
Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?=
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Tue, Jul 27, 1999 at 04:39:28PM -0400, j3 <j3@allied.org> wrote:

> >> 1) Do people have specific recommendations about boards to buy/don't buy?
> 
> I would reccomend against the Tyan Thunder 100.  Call it bad luck, but
> through no fault of my own (misuse, trauma, etc) my SIXTH board in a year
> is arriving tomorrow.  I have had 2 bad PS/2 Keyboard Ports, a failed PS/2
> mouse port, a bad SCSI controller, and most recently a bad IDE controller.
> Perhaps my reseller just got a bad batch, but this has been insane.

Yes, exactly same for Thunder 100. Three boards subsequently failed
within one year for me, all had same failure, one of the processor
current stabilizator smoked. They can call it bad luck or whatever but
it must be some design fault. I think so because machines were
different, one had two PII 400 processors and the other one PII 450,
this is nothing to do with processors, the speed of processors and power
supplies. I refused to get the fourth and spent some money for newer
Thunderbolt as slightly more expensive replacement. I hope the newer
model has better design, unfortunately I have no alternative to Tyan
boards because here are no other resellers which sell SMP boards. Of
course here are other resellers which claim they sell but as far as I
tried they all have great purvey problems.
-- 

Vallo Kallaste
vallo@matti.ee


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Wed Jul 28  1:25:38 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90])
	by hub.freebsd.org (Postfix) with ESMTP id 8C2B814F46
	for <freebsd-smp@freebsd.org>; Wed, 28 Jul 1999 01:25:33 -0700 (PDT)
	(envelope-from tom@embt.com)
Received: from paranor.embt.net (timembt.iinc.com [206.67.169.229])
	by mercury.gfit.net (8.8.8/8.8.8) with SMTP id DAA15103
	for <freebsd-smp@freebsd.org>; Wed, 28 Jul 1999 03:26:15 -0500 (CDT)
	(envelope-from tom@embt.com)
Message-Id: <3.0.3.32.19990728042442.007617f0@mail.embt.com>
X-Sender: tembt@mail.embt.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date: Wed, 28 Jul 1999 04:24:42 -0400
To: freebsd-smp@freebsd.org
From: Tom Embt <tom@embt.com>
Subject: Re: SMP kernel on dual board with single proc?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>If you are using a slot-architecture board, then you need a
>terminator in the empty slot.
>
>In general, "BSP" means "Boot System Processor" and "AP" means
>"Auxillary Processor" -- in other words, it thinks it can't
>find the BIOS designated boot processor.

Ahh, that's what it means. :)

>You may find that swapping slots fixes the problem (if, as Mike
>Smith said, you are running a -current that is no more than two
>weeks old).

Already tried that.  Not eager to keep swapping, as I don't want to make a
mess of the thermal goop between the heatsink & CPU (it's not the drying
kind).

>For standard slot processers (e.g., my dual P90), the BIOS has
>always given the right information to the BP (including the APIC
>ID), so it has been rare that it would not run with one processor
>removed (the last time was the first time somone kicked it up
>from 2 to 4 processors).
>
>
>> Shall I assume it is not possible to run an SMP kernel on this system w/o
>> another CPU?
>
>1)	How old is the build?

cvsup'ed Tuesday 7/27 3.2-STABLE just to be sure, still panics

>2)	Socket 370 = needs terminator, IIRC...

Hmm, I've never heard of a 370 terminator before..  I suspect that the mobo
might be auto-terminating the unpopulated socket and disabling some of the
APIC hardware.

When using 1 CPU on a MP board, is it normal that the board require a
particular socket/slot to be populated first?  This board does not, so I am
wondering if perhaps the logic required to enable this "feature" is
throwing off some of the SMP functionality (which of course would normally
not be needed in a UP situation anyway).  Keep in mind this is naive
speculation be someone who has no experience with SMP anything whatsoever.

>
>					Terry Lambert
>					terry@lambert.org

Oh bother, I should probably just get another processor while they're still
available.  Then it _better_ work! ;)



Tom Embt
tom@embt.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Wed Jul 28  3:53: 4 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110])
	by hub.freebsd.org (Postfix) with ESMTP id 3B25014F06
	for <freebsd-smp@FreeBSD.ORG>; Wed, 28 Jul 1999 03:52:59 -0700 (PDT)
	(envelope-from Joachim.Strombergson@emw.ericsson.se)
Received: from poem.emw.ericsson.se (poem.emw.ericsson.se [136.225.49.25])
	by penguin.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.3) with ESMTP id MAA20223;
	Wed, 28 Jul 1999 12:50:26 +0200 (MET DST)
Received: from biff.mo.emw.ericsson.se (biff.mo.emw.ericsson.se [136.225.83.24]) by poem.emw.ericsson.se (8.6.12/8.6.12) with ESMTP id MAA20605; Wed, 28 Jul 1999 12:50:26 +0200
Received: from stewart.mo.emw.ericsson.se (stewart.mo.emw.ericsson.se [136.225.229.138]) by biff.mo.emw.ericsson.se (8.8.8+Sun/SMI-SVR4-biff-1.0) with SMTP
	id MAA02397; Wed, 28 Jul 1999 12:50:17 +0200 (MET DST)
Received: from emw.ericsson.se (localhost [127.0.0.1]) by stewart.mo.emw.ericsson.se (SMI-8.6/SMI-SVR4-esunix-1.3) with ESMTP
	id MAA10473; Wed, 28 Jul 1999 12:50:16 +0200
Message-ID: <379EE068.BE2C9058@emw.ericsson.se>
Date: Wed, 28 Jul 1999 12:50:16 +0200
From: Joachim Strombergson <Joachim.Strombergson@emw.ericsson.se>
Organization: Ericsson Microwave Systems
X-Mailer: Mozilla 4.08C-EMW [en] (X11; I; SunOS 5.5.1 sun4u)
MIME-Version: 1.0
To: Terry Lambert <tlambert@primenet.com>
Cc: "freebsd-smp@FreeBSD.ORG" <freebsd-smp@FreeBSD.ORG>
Subject: Re: SMP kernel on dual board with single proc?
References: <199907272336.QAA02119@usr01.primenet.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by biff.mo.emw.ericsson.se id MAA02397
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Hello!

Terry Lambert wrote:
> If you are using a slot-architecture board, then you need a
> terminator in the empty slot.
>
> > Shall I assume it is not possible to run an SMP kernel on this system=
 w/o
> > another CPU?
>=20
> 1)      How old is the build?
>=20
> 2)      Socket 370 =3D needs terminator, IIRC...

The ABIT BP6 works nicely with only one CPU plugged in without a socket
terminator in the spare socket.

--=20
Med v=E4nlig h=E4lsning, Yours

Joachim Str=F6mbergson - Alltid i harmonisk sv=E4ngning
---------------- Ericsson Microwave Systems AB -----------------
Joachim Str=F6mbergson            http://www.ericsson.se/microwave
     ASIC System on Silicon engineer, nice to CUTE animals.   =20
* Opinions above, expressed or implicit, are strictly personal *
------------- Spamfodder: regeringen@regeringen.se -------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Wed Jul 28  7:50:35 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from allied.org (broken.ne.mediaone.net [24.218.77.215])
	by hub.freebsd.org (Postfix) with SMTP id 210AA14BF4
	for <freebsd-smp@FreeBSD.ORG>; Wed, 28 Jul 1999 07:50:21 -0700 (PDT)
	(envelope-from j3@allied.org)
Received: (qmail 5837 invoked from network); 28 Jul 1999 15:50:17 -0000
Received: from dyn19.cello-us.com (HELO dimension-m166a) (208.212.48.52)
  by broken.ne.mediaone.net with SMTP; 28 Jul 1999 15:50:17 -0000
Message-Id: <3.0.6.32.19990728104922.007a3a40@broken.ne.mediaone.net>
X-Sender: j3@broken.ne.mediaone.net
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Wed, 28 Jul 1999 10:49:22 -0400
To: "Gary D. Margiotta" <gary@tbe.net>
From: j3 <j3@allied.org>
Subject: Re: Dual Processor Motherboards (Abit BP6)
Cc: freebsd-smp@FreeBSD.ORG
In-Reply-To: <Pine.BSF.4.10.9907271724310.21148-100000@surreal.vrhost.co
 m>
References: <3.0.6.32.19990727163928.008230d0@broken.ne.mediaone.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>If you're looking for price/performance, get the Abit BP6 and run dual
>celerons on it... a lot of people have had quite good results with them,
>and for price, I'd say the dual 366 PPGA is the best deal...
>
>______________________________________________________________
>-Gary Margiotta				Voice:	(973) 835-7855
>TBE Internet Services			Fax:	(973) 835-4755
>http://www.tbe.net			E-Mail:	gary@tbe.net
>


I have been following the BP6 and the rumors of Intel changing the celeron
fab to disable (permanently) SMP operation.  I quote from
http://www.bxboards.com :
__
My rather tounge-in-cheek comment that the "for uniprocessor systems only"
marking could just be a cheap trick from Intel to make people think twice
about going dual Celeron could well be right! Some reports are filtering
through that CPU's with this box marking are still dual SMP capable and
even the Celeron 500, which was reported to have this locking - as a direct
response to Abit's BP6 - seem also to work. Right now, as always in these
cases, the picture is confusing. My advice would be to hunt down pre-July
Celeron's for now to be on the safe-side. I personally still believe that
Intel will not tolerate dual SMP Celerons much longer... 

Update: A couple of vendors have written to me confirming this. 

Steve from UKGamers wrote: 

Saw your post on your site. For your reader's information I have tried week
26 celerons in SMP and they work ok. By my calculation that makes 1st week
july ok for now. 

PCNut wrote: 

Just FYI, I have tested about 10 week 27 C366 chips tonight, they are OEM
chips made in Malaysia; which I doubt is much different from the retail
version. They work just fine on BP6 in SMP mode, cooking along at 2 x
550Mhz as we speak. Just thought you may like to know, Intel has yet
disable the SMP on these Celeron chips, just change the label on the retail
boxed processors. :) 
__

So, the longetivity of Celeron SMP is murky water, no one really knows what
is coming.  If you are thinking about building a BP6 system though, I would
advise you to buy your chips now.  Prices won't drop much lower then they
already are for the 300-366 range, and the 400-466 will probably only go
down $20 or so in the coming months.  If you are waiting for 500 mhz, good
luck.

     -Jeff Casimir

PS: Can anyone reccomend a FAQ/Step-by-step on setting up a FreeBSD
(uniprocessor) box as a firewall/DNS solution?  I am an "intelligent newb"
when it comes to software, I am mostly a hardware geek.  Thanks.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Wed Jul 28 11:11:50 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from bofh.dermak.pl (bofh.dermak.pl [212.160.174.2])
	by hub.freebsd.org (Postfix) with ESMTP id E9B4E14C3F
	for <freebsd-smp@FreeBSD.ORG>; Wed, 28 Jul 1999 11:11:43 -0700 (PDT)
	(envelope-from jacke@bofh.pl)
Received: from localhost (jacke@localhost)
	by bofh.dermak.pl (8.9.3/8.9.3) with ESMTP id UAA72705;
	Wed, 28 Jul 1999 20:11:23 +0200 (CEST)
	(envelope-from jacke@bofh.pl)
Date: Wed, 28 Jul 1999 20:11:20 +0200 (CEST)
From: Jakub Klausa <jacke@bofh.pl>
X-Sender: jacke@bofh.dermak.pl
To: Vallo Kallaste <vallo@matti.ee>
Cc: freebsd-smp@FreeBSD.ORG
Subject: Re: Dual Processor Motherboards
In-Reply-To: <19990728112025.A74699@myhakas.matti.ee>
Message-ID: <Pine.BSF.4.10.9907282005310.55957-100000@bofh.dermak.pl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

-----BEGIN PGP SIGNED MESSAGE-----

On Wed, 28 Jul 1999, Vallo Kallaste wrote:

=> 
=> Yes, exactly same for Thunder 100. Three boards subsequently failed
=> within one year for me, all had same failure, one of the processor

Quite strange, comparing to one of my SMP systems running on Tyan Thunder
100 for over a year now and showing not even a sign of problems. 
If it would be possible to buy Tyan mbs here, in .pl i'd certainly do
that, though, unfortunetly it's quite hard.

(The system with that Tyan mb has 2xPII400,512MB RAM, and quite a load of
disks. It's load rather rarely gets under 1)

Kuba
- -- 
        Jakub Klausa, JK762-RIPE, jacke@bofh.pl, WBS core team member
* <inof> "The Complete Idiot's Guide to Linux with Cdrom" (Barnes & Noble) *

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQCVAwUBN59Hyk54q5P/Kvv1AQH8LQP/bcldBmo8MgEFHF5BuikJ+8aHZFRDw+Ro
Dxpc8hWkHU1Y0oA34M4trYRPR+vshvi+8DOvQ76TgAQhewLn2v0h+Yds5EtkXIaU
4w72amKtIESmy/gJfcZMeOnP/lbAl4YY07XA5urTO1moneYHtpjukgLrzp23TOvI
Zy15WDW2Tfg=
=iDO6
-----END PGP SIGNATURE-----



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Wed Jul 28 11:35:33 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135])
	by hub.freebsd.org (Postfix) with ESMTP id 97D3114FD3
	for <freebsd-smp@FreeBSD.ORG>; Wed, 28 Jul 1999 11:35:29 -0700 (PDT)
	(envelope-from vallo@matti.ee)
Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87])
	by solaris.matti.ee (8.9.3/8.9.3) with ESMTP id VAA28752;
	Wed, 28 Jul 1999 21:34:21 +0300 (EET DST)
Received: by myhakas.matti.ee (Postfix, from userid 1000)
	id B5E85A3; Wed, 28 Jul 1999 21:34:22 +0300 (EEST)
Date: Wed, 28 Jul 1999 21:34:22 +0300
From: Vallo Kallaste <vallo@matti.ee>
To: Jakub Klausa <jacke@bofh.pl>
Cc: freebsd-smp@FreeBSD.ORG
Subject: Re: Dual Processor Motherboards
Message-ID: <19990728213422.A80991@myhakas.matti.ee>
Reply-To: vallo@matti.ee
References: <19990728112025.A74699@myhakas.matti.ee> <Pine.BSF.4.10.9907282005310.55957-100000@bofh.dermak.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <Pine.BSF.4.10.9907282005310.55957-100000@bofh.dermak.pl>; from Jakub Klausa on Wed, Jul 28, 1999 at 08:11:20PM +0200
Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?=
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Wed, Jul 28, 1999 at 08:11:20PM +0200, Jakub Klausa <jacke@bofh.pl> wrote:

> => Yes, exactly same for Thunder 100. Three boards subsequently failed
> => within one year for me, all had same failure, one of the processor
> 
> Quite strange, comparing to one of my SMP systems running on Tyan Thunder
> 100 for over a year now and showing not even a sign of problems. 
> If it would be possible to buy Tyan mbs here, in .pl i'd certainly do
> that, though, unfortunetly it's quite hard.
> 
> (The system with that Tyan mb has 2xPII400,512MB RAM, and quite a load of
> disks. It's load rather rarely gets under 1)

Hmm, I even had different versions of Thunder 100 boards which smoked in
same fashion. I had In-Box processors with integrated cooling and the
case was properly cooled also. I have no clue what happened. I'm annoyed
because the latest board went to hell and one of my PII-400 together with
it. I'm still waiting for replacement processors to arrive :-( What a
mess.
-- 

Vallo Kallaste
vallo@matti.ee


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Wed Jul 28 12: 2:19 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from sbridge.highvoltage.com (voltage.high-voltage.com [205.243.158.175])
	by hub.freebsd.org (Postfix) with SMTP id B33BB1502C
	for <freebsd-smp@freebsd.org>; Wed, 28 Jul 1999 12:02:04 -0700 (PDT)
	(envelope-from BMCGROARTY@high-voltage.com)
Date: Wed, 28 Jul 1999 13:55 -0600
From: "Brian McGroarty" <BMCGROARTY@high-voltage.com>
To: freebsd-smp@freebsd.org
Subject: RE:  Re: Dual Processor Motherboards
Message-ID: <78166768FA40D31186D30008C7333C82@high-voltage.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On the flip side, I've been using a Tyan Tiger 100 for well over half a year
now without a hitch. I've got two Celeron 300As on socket adapters, in SMP,
running at 504mhz apiece, 512mb of RAM. My roommate is running a similar
configuration with PIIIs instead of the Celerons, also no problems.

Have others' experiences been good with the Tiger 100?


 -----Original Message-----
From: Vallo Kallaste [mailto:vallo@matti.ee]
Sent: Wednesday, July 28, 1999 12:34 PM
To: Brian McGroarty; Jakub Klausa
Cc: freebsd-smp
Subject: Re: Dual Processor Motherboards


Hmm, I even had different versions of Thunder 100 boards which smoked in
same fashion. I had In-Box processors with integrated cooling and the
case was properly cooled also. I have no clue what happened. I'm annoyed
because the latest board went to hell and one of my PII-400 together with
it. I'm still waiting for replacement processors to arrive :-( What a
mess.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Wed Jul 28 12:49:28 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from fire.starkreality.com (fire.starkreality.com [208.24.48.226])
	by hub.freebsd.org (Postfix) with ESMTP id 92B4515033
	for <freebsd-smp@FreeBSD.ORG>; Wed, 28 Jul 1999 12:49:17 -0700 (PDT)
	(envelope-from caesar@starkreality.com)
Received: from GRAIL (grail.remote.starkreality.com [208.24.48.232])
	by fire.starkreality.com (8.9.3/8.9.2) with SMTP id OAA10587;
	Wed, 28 Jul 1999 14:49:08 -0500 (CDT)
Message-Id: <4.1.19990728144709.00a7f038@imap.colltech.com>
X-Sender: caesar@fire.starkreality.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 28 Jul 1999 14:48:25 -0500
To: "Brian McGroarty" <BMCGROARTY@high-voltage.com>,
	freebsd-smp@FreeBSD.ORG
From: "William S. Duncanson" <caesar@starkreality.com>
Subject: RE:  Re: Dual Processor Motherboards
In-Reply-To: <78166768FA40D31186D30008C7333C82@high-voltage.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Mine's been rock solid for about a year now.  Dual PII 300's, no overclocking.

At 13:55 7/28/99 -0600, Brian McGroarty wrote:
>On the flip side, I've been using a Tyan Tiger 100 for well over half a year
>now without a hitch. I've got two Celeron 300As on socket adapters, in SMP,
>running at 504mhz apiece, 512mb of RAM. My roommate is running a similar
>configuration with PIIIs instead of the Celerons, also no problems.
>
>Have others' experiences been good with the Tiger 100?
>
>
> -----Original Message-----
>From: Vallo Kallaste [mailto:vallo@matti.ee]
>Sent: Wednesday, July 28, 1999 12:34 PM
>To: Brian McGroarty; Jakub Klausa
>Cc: freebsd-smp
>Subject: Re: Dual Processor Motherboards
>
>
>Hmm, I even had different versions of Thunder 100 boards which smoked in
>same fashion. I had In-Box processors with integrated cooling and the
>case was properly cooled also. I have no clue what happened. I'm annoyed
>because the latest board went to hell and one of my PII-400 together with
>it. I'm still waiting for replacement processors to arrive :-( What a
>mess.
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-smp" 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  Wed Jul 28 13:12: 7 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from eagle.phc.igs.net (eagle.phc.igs.net [207.210.17.201])
	by hub.freebsd.org (Postfix) with ESMTP id 0B6F61544C
	for <freebsd-smp@FreeBSD.ORG>; Wed, 28 Jul 1999 13:11:58 -0700 (PDT)
	(envelope-from eagle@phc.igs.net)
Received: from localhost (eagle@localhost)
	by eagle.phc.igs.net (8.9.3/8.9.3) with ESMTP id QAA04085;
	Wed, 28 Jul 1999 16:11:40 -0400 (EDT)
	(envelope-from eagle@phc.igs.net)
X-Authentication-Warning: eagle.phc.igs.net: eagle owned process doing -bs
Date: Wed, 28 Jul 1999 16:11:39 -0400 (EDT)
From: Rob Garrett <eagle@phc.igs.net>
To: Todd Backman <todd@wank.necropolis.org>
Cc: Tom Embt <tom@embt.com>, freebsd-smp@FreeBSD.ORG
Subject: Re: SMP kernel on dual board with single proc?
In-Reply-To: <Pine.BSF.4.10.9907261148550.44358-100000@wank.necropolis.org>
Message-ID: <Pine.BSF.4.10.9907281610270.366-100000@eagle.phc.igs.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org



On Mon, 26 Jul 1999, Todd Backman wrote:

> 
> I do not think so.
> 
> On Mon, 26 Jul 1999, Tom Embt wrote:
> 
> > Is it possible to build & run an SMP kernel on a DP board with only one CPU
> > installed?  I know this is kind of a silly thing to do but I was just
> > wondering if it is possible.
> > 
> > I tried it on my BP6, but got a "panic: NO BSP found!" or something like
> > that on boot.  If this is indeed possible I can give it another go, and
> > post my mptable, dmesg, and kernel conf.
> > 
> > 
> > 
> > Tom Embt
> > tom@embt.com

	I have run smp kernels on smp mother boards with a single cpu, in
the past. havent had a smp box without at least two proccessors in a while
so..

Rob



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Thu Jul 29 18:45:13 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from mail.zuhause.org (c2-178.xtlab.com [205.215.217.178])
	by hub.freebsd.org (Postfix) with ESMTP
	id C710A14E74; Thu, 29 Jul 1999 18:44:50 -0700 (PDT)
	(envelope-from bruce@zuhause.mn.org)
Received: by mail.zuhause.org (Postfix, from userid 1001)
	id 16D6D7C31; Thu, 29 Jul 1999 20:44:22 -0500 (CDT)
From: Bruce Albrecht <bruce@zuhause.mn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14241.885.945134.868473@celery.zuhause.org>
Date: Thu, 29 Jul 1999 20:44:21 -0500 (CDT)
To: Koen Schreel <K.R.A.M.Schreel@wtb.tue.nl>
Cc: emulation@FreeBSD.ORG, Julian Elischer <julian@whistle.com>,
	freebsd-smp@FreeBSD.ORG
Subject: Re: wine and SMP
In-Reply-To: <379F0404.B3017FE8@wtb.tue.nl>
References: <379F0404.B3017FE8@wtb.tue.nl>
X-Mailer: VM 6.72 under 20.4 "Emerald" XEmacs  Lucid
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Koen Schreel writes:
 > Hi,
 > 
 > I'm having trouble running wine with an SMP kernel. It compiles fine,
 > but when I start wine, it just 'hangs' without an error message.
 > Pressing ctrl-c returns to the prompt. One line is added to the dmesg
 > output like:
 > 
 > shared address space fork attempted: pid: 2252
 > 
 > Using a non-SMP kernel works OK.

It's because the 3.2-stable kernel doesn't currently support forks with
shared address space.  It appears that this has been fixed for -current,
but I don't know when, if ever, 3.2 will be fixed, since it's been
broken since at least March 2.

It looks like Julian Elischer was the last person to commit anything to
sys/kern/kern_fork.c in -stable, so he may know if there are any plans
to fix this before 4.0 is released.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Thu Jul 29 21:26:17 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
	by hub.freebsd.org (Postfix) with ESMTP
	id EDA1814EDA; Thu, 29 Jul 1999 21:26:13 -0700 (PDT)
	(envelope-from alc@cs.rice.edu)
Received: (from alc@localhost)
	by cs.rice.edu (8.9.0/8.9.0) id XAA07342;
	Thu, 29 Jul 1999 23:26:04 -0500 (CDT)
Date: Thu, 29 Jul 1999 23:26:04 -0500
From: Alan Cox <alc@cs.rice.edu>
To: Bruce Albrecht <bruce@zuhause.mn.org>
Cc: Koen Schreel <K.R.A.M.Schreel@wtb.tue.nl>, emulation@freebsd.org,
	Julian Elischer <julian@whistle.com>, freebsd-smp@freebsd.org
Subject: Re: wine and SMP
Message-ID: <19990729232604.K10860@cs.rice.edu>
References: <379F0404.B3017FE8@wtb.tue.nl> <14241.885.945134.868473@celery.zuhause.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5us
In-Reply-To: <14241.885.945134.868473@celery.zuhause.org>; from Bruce Albrecht on Thu, Jul 29, 1999 at 08:44:21PM -0500
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Thu, Jul 29, 1999 at 08:44:21PM -0500, Bruce Albrecht wrote:
> 
> It's because the 3.2-stable kernel doesn't currently support forks with
> shared address space.  It appears that this has been fixed for -current,
> but I don't know when, if ever, 3.2 will be fixed, since it's been
> broken since at least March 2.
> 

It requires Luoqi's megapatch of April 28.

Alan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Thu Jul 29 21:54: 3 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from poboxer.pobox.com (ferg5200-1-29.cpinternet.com [208.149.16.29])
	by hub.freebsd.org (Postfix) with ESMTP
	id A9245156B7; Thu, 29 Jul 1999 21:53:41 -0700 (PDT)
	(envelope-from alk@poboxer.pobox.com)
Received: (from alk@localhost)
	by poboxer.pobox.com (8.9.3/8.9.1) id XAA02642;
	Thu, 29 Jul 1999 23:51:18 -0500 (CDT)
	(envelope-from alk)
From: Anthony Kimball <anthony.kimball@eastmail2.East.Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 29 Jul 1999 23:51:18 -0500 (CDT)
X-Face: \h9Jg:Cuivl4S*UP-)gO.6O=T]]@ncM*tn4zG);)lk#4|lqEx=*talx?.<li^!8ecK]}3L-
	6`ZQW3}kxy*5]B<KA"&iBl58"/$W-0PP`B7c%'XczR)8T0VN47L`rQlu8qBIX4TJ|v'D%:k7GO%v4A
	Os>Gk,dMQU2)ptPC17cpBzm(l'M|H8BUF1&]dDCxZ.c~Wy6-j,^V1E(NtX$FpkkdnJixsJHE95JlhO
	5\M3jh'YiO7KPCn0~W`Ro44_TB@&JuuqRqgPL'0/{):7rU-%.*@/>q?1&Ed
Reply-To: anthony.kimball@eastmail2.East.Sun.COM
To: alc@cs.rice.edu
Cc: emulation@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG
Subject: Re: wine and SMP
References: <379F0404.B3017FE8@wtb.tue.nl>
	<14241.885.945134.868473@celery.zuhause.org>
	<19990729232604.K10860@cs.rice.edu>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14241.11852.781566.816784@avalon.east>
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Quoth Alan Cox on Thu, 29 July:
: > 
: > It's because the 3.2-stable kernel doesn't currently support forks with
: > shared address space. 
: > 
: 
: It requires Luoqi's megapatch of April 28.
: 

I was still bleeding then, and not on stable yet. A basic search of
the mail archives divulges nothing (search "Stable" for "Luoqi" and
"patch"), nor does www.freebsd.org/~luoqi show spoor.  Where can I
find this megapatch and its description?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Thu Jul 29 22:18: 1 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4D10A14DF4; Thu, 29 Jul 1999 22:17:57 -0700 (PDT)
	(envelope-from alc@cs.rice.edu)
Received: (from alc@localhost)
	by cs.rice.edu (8.9.0/8.9.0) id AAA08130;
	Fri, 30 Jul 1999 00:17:53 -0500 (CDT)
Date: Fri, 30 Jul 1999 00:17:53 -0500
From: Alan Cox <alc@cs.rice.edu>
To: Anthony Kimball <anthony.kimball@eastmail2.East.Sun.COM>,
	Bruce Albrecht <bruce@zuhause.mn.org>
Cc: emulation@freebsd.org, freebsd-smp@freebsd.org
Subject: Re: wine and SMP
Message-ID: <19990730001753.M10860@cs.rice.edu>
References: <379F0404.B3017FE8@wtb.tue.nl> <14241.885.945134.868473@celery.zuhause.org> <19990729232604.K10860@cs.rice.edu> <14241.11852.781566.816784@avalon.east>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.5us
In-Reply-To: <14241.11852.781566.816784@avalon.east>; from Anthony Kimball on Thu, Jul 29, 1999 at 11:51:18PM -0500
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Luoqi's megapatch existed for -CURRENT only, and was applied
to -CURRENT on April 28th.  I doubt that we'll ever backport
it to -STABLE.

Alan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Fri Jul 30  4:55:49 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from freya.circle.net (morrigu.circle.net [209.95.64.11])
	by hub.freebsd.org (Postfix) with ESMTP id EAD2E14D07
	for <freebsd-smp@freebsd.org>; Fri, 30 Jul 1999 04:55:45 -0700 (PDT)
	(envelope-from tcobb@staff.circle.net)
Received: by freya.circle.net with Internet Mail Service (5.5.2232.9)
	id <PYHD3FTR>; Fri, 30 Jul 1999 07:49:16 -0400
Message-ID: <A0CFA284C004D211B7EE0060082F32A41F281E@freya.circle.net>
From: tcobb@staff.circle.net
To: freebsd-smp@freebsd.org
Subject: Apache process wedges one processor under load
Date: Fri, 30 Jul 1999 07:49:06 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

System is running 3.2 (tried both RELEASE and STABLE) on
a Supermicro P6DBU motherboard with two PIII 550 processors.

System has 1GB ECC RAM and a DPT RAID controller, the 
kernel config and mptable output is at the end of this
email.

The box is a heavily-used production web server, running apache
and apache-ssl.  In usually under 6 hours, one of the apache
processes (not the primary one) wedges CPU 0,
forcing all other processes to run on CPU 1.

Trying to truss the wedging process produces nothing, and the
process is unkillable.  It also causes problems if I try
to reboot, as it doesn't seem to be able to close down CPU 0.

Also, as a strange aside, mptable gives me an "Extended table HOSED"
when I run the bios at 1.4, but works fine at 1.1.  The wedging problem
happens no matter which APIC level I'm running.

Is this a known problem?  What other details can I provide
that would help?

Thanks in advance!


-Troy Cobb
 Circle Net, Inc.
 http://www.circle.net

MPTABLE and kernel config output follows:

============================================================================
===

MPTable, version 2.0.15

----------------------------------------------------------------------------
---

MP Floating Pointer Structure:

  location:			BIOS
  physical address:		0x000fb4f0
  signature:			'_MP_'
  length:			16 bytes
  version:			1.4
  checksum:			0x1d
  mode:				Virtual Wire

----------------------------------------------------------------------------
---

MP Config Table Header:

  physical address:		0x000f2450
  signature:			'PCMP'
  base table length:		268
  version:			1.4
  checksum:			0x63
  OEM ID:			'INTEL   '
  Product ID:			'440BX       '
  OEM table pointer:		0x00000000
  OEM table size:		0
  entry count:			25
  local APIC address:		0xfee00000
  extended table length:	16
  extended table checksum:	234

----------------------------------------------------------------------------
---

MP Config Base Table Entries:

--
Processors:	APIC ID	Version	State		Family	Model	Step
Flags
		 0	 0x11	 BSP, usable	 6	 7	 3
0x387fbff
		 1	 0x11	 AP, usable	 6	 7	 3
0x387fbff
--
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	  12	      2	  12
		INT	 conforms    conforms	     2	  13	      2	  13
		INT	 conforms    conforms	     2	  14	      2	  14
		INT	active-lo       level	     2	  15	      2	  16
		INT	active-lo       level	     2	  11	      2	  17
		INT	active-lo       level	     2	  10	      2	  18
		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

----------------------------------------------------------------------------
---

MP Config Extended Table Entries:

Extended Table HOSED!



machine		"i386"
cpu		"I686_CPU"
ident		"CHANDRA030"
maxusers	128

options		INET			#InterNETworking
options		FFS			#Berkeley Fast Filesystem
options		FFS_ROOT		#FFS usable as root device [keep
this!]
options		PROCFS			#Process filesystem
options		"COMPAT_43"		#Compatible with BSD 4.3 [KEEP
THIS!]
options		SCSI_DELAY=8000		#Be pessimistic about Joe SCSI
device
options		USERCONFIG		#boot -c editor
options		VISUAL_USERCONFIG	#visual boot -c editor
#options         PQ_LARGECACHE           # color for 512k/16k cache
options         NMBCLUSTERS=8192

# Mandatory: SMP
options         SMP                     # Symmetric MultiProcessor Kernel
options         APIC_IO                 # Symmetric (APIC) I/O
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

config		kernel	root on da0

controller	isa0
controller	pnp0
controller	pci0

controller	fdc0	at isa? port "IO_FD1" bio irq 6 drq 2
disk		fd0	at fdc0 drive 0

#controller	ahc0
controller      dpt0
options		DPT_LOST_IRQ
controller	scbus0

device		da0

# atkbdc0 controlls both the keyboard and the PS/2 mouse
controller	atkbdc0	at isa? port IO_KBD tty
device		atkbd0	at isa? tty irq 1
device		vga0	at isa? port ? conflicts

# syscons is the default console driver, resembling an SCO console
device		sc0	at isa? tty
device		npx0	at isa? port IO_NPX irq 13

device		sio0	at isa? port "IO_COM1" flags 0x10 tty irq 4
device		sio1	at isa? port "IO_COM2" tty irq 3

device		xl0

pseudo-device	loop
pseudo-device	ether
pseudo-device	pty	16
pseudo-device	gzip		# Exec gzipped a.out's
pseudo-device   ccd     2
pseudo-device	speaker

options         "MAXDSIZ=(512*1024*1024)"
options         "DFLDSIZ=(256*1024*1024)"

options         "ICMP_BANDLIM"

options         SYSVSHM
options         SYSVSEM
options         SYSVMSG


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Fri Jul 30  7:18:26 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from mail.zuhause.org (c2-178.xtlab.com [205.215.217.178])
	by hub.freebsd.org (Postfix) with ESMTP
	id BD6C714C08; Fri, 30 Jul 1999 07:18:19 -0700 (PDT)
	(envelope-from bruce@zuhause.mn.org)
Received: by mail.zuhause.org (Postfix, from userid 1001)
	id C9E0A7C32; Fri, 30 Jul 1999 09:18:18 -0500 (CDT)
From: Bruce Albrecht <bruce@zuhause.mn.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14241.46122.663977.293230@celery.zuhause.org>
Date: Fri, 30 Jul 1999 09:18:18 -0500 (CDT)
To: Alan Cox <alc@cs.rice.edu>
Cc: emulation@freebsd.org, freebsd-smp@freebsd.org
Subject: Re: wine and SMP
In-Reply-To: <19990730001753.M10860@cs.rice.edu>
References: <379F0404.B3017FE8@wtb.tue.nl>
	<14241.885.945134.868473@celery.zuhause.org>
	<19990729232604.K10860@cs.rice.edu>
	<14241.11852.781566.816784@avalon.east>
	<19990730001753.M10860@cs.rice.edu>
X-Mailer: VM 6.72 under 20.4 "Emerald" XEmacs  Lucid
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Alan Cox writes:
 > Luoqi's megapatch existed for -CURRENT only, and was applied
 > to -CURRENT on April 28th.  I doubt that we'll ever backport
 > it to -STABLE.

There should be a note added to the wine port to say that it doesn't
work for SMP kernels in 3.2.  I guess it's time to start following
-current again.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Fri Jul 30 10:41:11 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from horst.bfd.com (horst.bfd.com [12.9.219.10])
	by hub.freebsd.org (Postfix) with ESMTP id 0D29E14CC9
	for <freebsd-smp@FreeBSD.ORG>; Fri, 30 Jul 1999 10:41:05 -0700 (PDT)
	(envelope-from ejs@bfd.com)
Received: from HARLIE.bfd.com (bastion.bfd.com [12.9.219.14])
	by horst.bfd.com (8.9.2/8.9.2) with ESMTP id KAA81497
	for <freebsd-smp@FreeBSD.ORG>; Fri, 30 Jul 1999 10:40:35 -0700 (PDT)
	(envelope-from ejs@bfd.com)
Date: Fri, 30 Jul 1999 10:40:34 -0700 (PDT)
From: "Eric J. Schwertfeger" <ejs@bfd.com>
To: "freebsd-smp@FreeBSD.ORG" <freebsd-smp@FreeBSD.ORG>
Subject: SMP and the Celeron
Message-ID: <Pine.BSF.4.05.9907301022080.12170-100000@harlie.bfd.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


(All of this is just my opinion, feel free to disagree or kibitz.  With
the recent threads, I thought that this needs to be said so that readers
can make informed decisions).

After having played with a dual Celeron system, and owning a dual PPro
w/512K cache per CPU, it would seem that the Celeron box benefits less
from SMP than the PPro box does.

The make world time on the PPro box is much less under SMP, but for the
Celeron box, it's only 20% faster.  (BTW, how is 49min37sec for a 3.2R 
make world on a single-HD system?)  Still, a single Celeron does a make
world faster than the dual PPro box (possibly due to lame IDE HD in dual
PPro box).

After having played around with it, it seems to come down to memory
bandwidth.  Since the Celerons have a quarter the L2 cache of the
PPros I've got, they are probably more dependant on memory bandwidth for
performance, and SMP just adds to the problem with bus contention.

Processes that tend to fit in the L2 Celeron cache, such as gzip, do
approach an 80-90% improvement with SMP, but overall, I'm seeing more of a
40-50% improvement.

Between this and the rumors that Intel is going to disable Celeron SMP in
the next Celeron revision, I have to consider Celeron SMP an interesting
experiment, but not something you'd actually use in a production
environment.  It's a good way to experiment with SMP for SMP's sake, but
unless you're doing the kind of stuff that does fit in the L2 cache, the
performance gain isn't what you'd hope for.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Fri Jul 30 12:29:57 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.218.96.75])
	by hub.freebsd.org (Postfix) with ESMTP id CF68715208
	for <freebsd-smp@FreeBSD.ORG>; Fri, 30 Jul 1999 12:29:45 -0700 (PDT)
	(envelope-from jim@thehousleys.net)
Received: from thehousleys.net (housley@localhost [127.0.0.1])
	by thehousleys.net (8.9.3/8.9.3) with ESMTP id PAA04179
	for <freebsd-smp@FreeBSD.ORG>; Fri, 30 Jul 1999 15:29:25 -0400 (EDT)
	(envelope-from jim@thehousleys.net)
Message-ID: <37A1FD14.CC862D4E@thehousleys.net>
Date: Fri, 30 Jul 1999 15:29:24 -0400
From: "James E. Housley" <jim@thehousleys.net>
X-Mailer: Mozilla 4.51 [en] (X11; U; FreeBSD 3.2-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: "freebsd-smp@FreeBSD.ORG" <freebsd-smp@FreeBSD.ORG>
Subject: Re: SMP and the Celeron
References: <Pine.BSF.4.05.9907301022080.12170-100000@harlie.bfd.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

"Eric J. Schwertfeger" wrote:
> 
> Between this and the rumors that Intel is going to disable Celeron SMP in
> the next Celeron revision, I have to consider Celeron SMP an interesting
> experiment, but not something you'd actually use in a production
> environment.  It's a good way to experiment with SMP for SMP's sake, but
> unless you're doing the kind of stuff that does fit in the L2 cache, the
> performance gain isn't what you'd hope for.
> 
I would agree almost completely.  I am running an overclocked dual celeron system for a "local production" server.  With one of my initial goal of getting SMP running affordably.  The next step of 2xPIII-? processors is more afforable down the line where I only have to buy them and not them PLUS everything else.

Jim
-- 
 James E. Housley                            PGP:   1024/03983B4D
 System Supply, Inc.                         2C 3F 3A 0D A8 D8 C3 13
 Pager: pagejim@notepage.com                 7C F0 B5 BF 27 8B 92 FE 

"The box said 'Requires Windows 95, NT, or better,' so I installed FreeBSD"


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Fri Jul 30 17:27:18 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0510E14E5F; Fri, 30 Jul 1999 17:27:14 -0700 (PDT)
	(envelope-from wwoods@cybcon.com)
Received: from freebsd.cybcon.com (usr1-4.cybcon.com [205.147.75.5])
	by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id RAA09225;
	Fri, 30 Jul 1999 17:27:12 -0700 (PDT)
Message-ID: <XFMail.990730172726.wwoods@cybcon.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
Date: Fri, 30 Jul 1999 17:27:26 -0700 (PDT)
Reply-To: wwoods@cybcon.com
From: William Woods <wwoods@cybcon.com>
To: freebsd-questions@freebsd.org, freebsd-smp@freebsd.org
Subject: CPU Useage
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Is there any app like xosview that shows the percentage of CPU use on a dual
CPU system?

----------------------------------
E-Mail: William Woods <wwoods@cybcon.com>
Date: 30-Jul-99
Time: 17:26:51

This message was sent by XFMail
----------------------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Fri Jul 30 17:44:14 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7683814BE1; Fri, 30 Jul 1999 17:44:11 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from localhost (doug@localhost)
	by dt011n65.san.rr.com (8.8.8/8.8.8) with ESMTP id RAA08577;
	Fri, 30 Jul 1999 17:41:31 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Date: Fri, 30 Jul 1999 17:41:31 -0700 (PDT)
From: Doug <Doug@gorean.org>
X-Sender: doug@dt011n65.san.rr.com
To: William Woods <wwoods@cybcon.com>
Cc: freebsd-questions@freebsd.org, freebsd-smp@freebsd.org
Subject: Re: CPU Useage
In-Reply-To: <XFMail.990730172726.wwoods@cybcon.com>
Message-ID: <Pine.BSF.4.05.9907301740530.8572-100000@dt011n65.san.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Fri, 30 Jul 1999, William Woods wrote:

> Is there any app like xosview that shows the percentage of CPU use on a dual
> CPU system?

	Doesn't xosview do it for you? It works fine for me on the dual
cpu systems I've used it on.

Doug



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Fri Jul 30 18:27:38 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5])
	by hub.freebsd.org (Postfix) with ESMTP
	id E264E14F2E; Fri, 30 Jul 1999 18:27:30 -0700 (PDT)
	(envelope-from wwoods@cybcon.com)
Received: from freebsd.cybcon.com (pm3b-9.cybcon.com [205.147.75.74])
	by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id SAA11873;
	Fri, 30 Jul 1999 18:26:23 -0700 (PDT)
Message-ID: <XFMail.990730182622.wwoods@cybcon.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <Pine.BSF.4.05.9907301740530.8572-100000@dt011n65.san.rr.com>
Date: Fri, 30 Jul 1999 18:26:22 -0700 (PDT)
Reply-To: wwoods@cybcon.com
From: William Woods <wwoods@cybcon.com>
To: Doug <Doug@gorean.org>
Subject: Re: CPU Useage
Cc: freebsd-smp@freebsd.org, freebsd-questions@freebsd.org
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Not here, there is only one meter for both CPU's...


On 31-Jul-99 Doug wrote:
> On Fri, 30 Jul 1999, William Woods wrote:
> 
>> Is there any app like xosview that shows the percentage of CPU use on a dual
>> CPU system?
> 
>       Doesn't xosview do it for you? It works fine for me on the dual
> cpu systems I've used it on.
> 
> Doug

----------------------------------
E-Mail: William Woods <wwoods@cybcon.com>
Date: 30-Jul-99
Time: 18:20:50

This message was sent by XFMail
----------------------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Sat Jul 31  8:19:18 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from freya.circle.net (morrigu.circle.net [209.95.64.11])
	by hub.freebsd.org (Postfix) with ESMTP
	id 975F515113; Sat, 31 Jul 1999 08:19:04 -0700 (PDT)
	(envelope-from tcobb@staff.circle.net)
Received: by freya.circle.net with Internet Mail Service (5.5.2232.9)
	id <PYHD3GFQ>; Sat, 31 Jul 1999 11:13:21 -0400
Message-ID: <A0CFA284C004D211B7EE0060082F32A41F2830@freya.circle.net>
From: tcobb@staff.circle.net
To: blapp@attic.ch, freebsd-current@freebsd.org
Cc: freebsd-smp@freebsd.org
Subject: RE: network got stuck during high nfs-load
Date: Sat, 31 Jul 1999 11:13:19 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
Content-Type: text/plain;
	charset="windows-1252"
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I'm now getting a similar thing with the latest -STABLE build.
NFS isn't involved, but this is on a heavily used webserver.
NIC is a 3COM 3C905b.

Ifconfig up and down works for about 5 packets, that's it.  netstat
was showing either errors inbound, or absolutely nothing.

This happens about once per day now, on this machine.  I've
had to switch back to a UP kernel to avoid this (and another
bug about processes getting wedged on a processor).

I think this is an SMP problem, so I've included freebsd-smp
in the reply.


-Troy Cobb
 Circle Net, Inc.
 http://www.circle.net

>   -----Original Message-----
>   From: Martin Blapp [mailto:blapp@attic.ch]
>   Sent: Saturday, July 31, 1999 9:57 AM
>   To: freebsd-current@freebsd.org
>   Subject: network got stuck during high nfs-load
>   
>   
>   
>   Hi driver gurus,
>   
>   Today I had heavy NFS-load on my CURRENT-SMP machine while compiling
>   world. Suddenly all NFS-Clients stopped working. I was't 
>   able to ping 
>   the server from inside my  /29 subnet, same with ping the 
>   others from
>   the server itself. I changed cables, plugged them  in and 
>   out, did some
>   ifconfig up down, deleted routes and added them again ... 
>   nothing.  But
>   the card was still sending from time to time (once a 
>   second) with 100%
>   load many 0 bytes - like some waves: 
>   
>   (tcp-dump from same subnet, MAC Adress 0:a0:cc:66:32:97 is 
>   the NFS-Server)
>   ------------------------------------------------------------
>   --------------
>   
>   13:53:41.673733 0:a0:cc:66:32:97 > 0:a0:cc:66:32:97 null 
>   test/C len=43
>                            0000 0000 0000 0000 0000 0000 0000 0000
>                            0000 0000 0000 0000 0000 0000 0000 0000
>                            0000 0000 0000 0000 0000 00
>   
>   13:53:41.773706 0:a0:cc:66:32:97 > 0:a0:cc:66:32:97 null 
>   test/C len=43
>                            0000 0000 0000 0000 0000 0000 0000 0000
>                            0000 0000 0000 0000 0000 0000 0000 0000
>                            0000 0000 0000 0000 0000 00    
>   
>   It looks like a endless loop somewhere in the de0-driver ...
>   
>   I was able to ping the machine from itself via loopback and 
>   via the local
>   ip. No stucked processes at all, the running make 
>   buildworld was still
>   running. Also the load was normal, I couldn't see some 
>   special behaviour ...
>   
>   I paniced the server and made a crashdump. If anybody is 
>   interested in
>   this strange behaviour, just write me back ... After a 
>   reboot, all worked
>   again, but that's not a good solution ;)
>   
>   Martin
>   
>   PS: cvsup is from yesterday (30.7.1999) at 22:00 CET and I included
>   a backtrace and a dmesg from my server ...
>   
>   backtrace from debug.kernel
>   ---------------------------
>   
>   #0  boot (howto=260) at ../../kern/kern_shutdown.c:291
>   #1  0xc01538c9 in panic (fmt=0xc0277c14 "from debugger")
>       at ../../kern/kern_shutdown.c:505
>   #2  0xc012df19 in db_panic (addr=-1071398025, have_addr=0, count=-1,
>       modif=0xff80dddc "") at ../../ddb/db_command.c:434
>   #3  0xc012deb7 in db_command (last_cmdp=0xc02a6f30, 
>   cmd_table=0xc02a6d90,
>       aux_cmd_tablep=0xc02c572c) at ../../ddb/db_command.c:334
>   #4  0xc012df7e in db_command_loop () at ../../ddb/db_command.c:456
>   #5  0xc012ffbb in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71
>   #6  0xc023c0c2 in kdb_trap (type=3, code=0, regs=0xff80ded0)
>       at ../../i386/i386/db_interface.c:157
>   #7  0xc02524a0 in trap (frame={tf_fs = 24, tf_es = 16, 
>   tf_ds = 16, tf_edi
>   = 0,
>         tf_esi = -1070741376, tf_ebp = -8331496, tf_isp = -8331524,
>         tf_ebx = -1070741376, tf_edx = -1070689184, tf_ecx = 16777217,
>         tf_eax = 38, tf_trapno = 3, tf_err = 0, tf_eip = 
>   -1071398025, tf_cs
>   = 8,
>         tf_eflags = 582, tf_esp = -1071030749, tf_ss = -1071045718})
>       at ../../i386/i386/trap.c:534
>   #8  0xc023c377 in Debugger (msg=0xc02923aa "manual escape 
>   to debugger")
>       at machine/cpufunc.h:64
>   #9  0xc0236d7c in scgetc (sc=0xc02c3ca0, flags=2)
>       at ../../dev/syscons/syscons.c:3813
>   #10 0xc0232529 in sckbdevent (thiskbd=0xc02db0a0, event=0, 
>   arg=0xc02c3ca0)
>       at ../../dev/syscons/syscons.c:688
>   #11 0xc022bd77 in atkbd_intr (kbd=0xc02db0a0, arg=0x0)
>       at ../../dev/kbd/atkbd.c:535
>   #12 0xc02692d7 in atkbd_isa_intr (arg=0xc05a2100) at
>   ../../isa/atkbd_isa.c:125
>   
>   dmesg-output
>   ------------
>   
>   Copyright (c) 1992-1999 The FreeBSD Project.
>   Copyright (c) 1982, 1986, 1989, 1991, 1993
>           The Regents of the University of California. All 
>   rights reserved.
>   FreeBSD 4.0-CURRENT #1: Fri Jul 30 21:31:06 CEST 1999
>       root@fuchur.lan.attic.ch:/usr/src/sys/compile/FUCHUR 
>   Timecounter "i8254"  frequency 1193182 Hz
>   CPU: Pentium/P55C (586-class CPU)
>     Origin = "GenuineIntel"  Id = 0x543  Stepping = 3
>     Features=0x8003bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,APIC,MMX>
>   real memory  = 67108864 (65536K bytes)
>   avail memory = 61652992 (60208K bytes)
>   Programming 24 pins in IOAPIC #0
>   FreeBSD/SMP: Multiprocessor motherboard
>    cpu0 (BSP): apic id:  0, version: 0x00030010, at 0xfee00000
>    cpu1 (AP):  apic id:  1, version: 0x00030010, at 0xfee00000
>    io0 (APIC): apic id:  2, version: 0x00170011, at 0xfec00000
>   Preloaded elf kernel "kernel" at 0xc0340000.
>   Intel Pentium detected, installing workaround for F00F bug
>   Probing for PnP devices:
>   npx0: <math processor> on motherboard
>   npx0: INT 16 interface
>   pcib0: <Host to PCI bridge> on motherboard
>   pci0: <PCI bus> on pcib0
>   isab0: <Intel 82371SB PCI to ISA bridge> at device 7.0 on pci0
>   ide_pci0: <Intel PIIX3 Bus-master IDE controller> at device 
>   7.1 on pci0
>   de0: <Digital 21140A Fast Ethernet> irq 17 at device 9.0 on pci0
>   de0: 21140A [10-100Mb/s] pass 2.0
>   de0: address 00:a0:cc:66:32:97
>   vga-pci0: <Matrox MGA 1024SG/1064SG/1164SG graphics 
>   accelerator> irq 18 at
>   device 10.0 on pci0 
>   ahc0: <Adaptec aic7880 Ultra SCSI adapter> irq 19 at device 
>   12.0 on pci0
>   ahc0: Using left over BIOS settings
>   ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs
>   isa0: <ISA bus> on motherboard
>   fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f7 irq 6 drq 2 on isa0
>   fdc0: FIFO enabled, 8 bytes threshold
>   fd0: <1440-KB 3.5" drive> on fdc0 drive 0
>   wdc0 at port 0x1f0-0x1f7 irq 14 on isa0
>   wdc0: unit 0 (atapi): <TOSHIBA CD-ROM XM-6202B/1110>, 
>   removable, accel,
>   ovlap, dma, iordis
>   wcd0: drive speed 5512KB/sec, 256KB cache
>   wcd0: supported read types: CD-R, CD-RW, CD-DA
>   wcd0: Audio: play, 255 volume levels
>   wcd0: Mechanism: ejectable tray
>   wcd0: Medium: CD-ROM 120mm data disc loaded, unlocked
>   wdc0: unit 1 (atapi): <IOMEGA  ZIP 100       ATAPI/23.D>, 
>   removable, intr,
>   iordis
>   wfd0: medium type unknown (no disk)
>   wfd0: buggy Zip drive, 64-block transfer limit set
>   atkbdc0: <keyboard controller (i8042)> at port 0x60-0x6f on isa0
>   atkbd0: <AT Keyboard> irq 1 on atkbdc0
>   vga0: <Generic ISA VGA> at port 0x3b0-0x3df iomem 
>   0xa0000-0xbffff on isa0  
>   sc0: VGA <16 virtual consoles, flags=0x200>
>   sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
>   sio0: type 16550A
>   sio1 at port 0x2f8-0x2ff irq 3 on isa0
>   sio1: type 16550A
>   ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0
>   ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
>   ppc0: FIFO with 16/16/16 bytes threshold
>   ppb0: IEEE1284 device found /NIBBLE
>   Probing for PnP devices on ppbus0:
>   ppbus0: <Hewlett-Packard HP LaserJet 5MP> HP ENHANCED 
>   PCL5,PJL,POSTSCRIPT
>   plip0: <PLIP network interface> on ppbus 0
>   lpt0: <generic printer> on ppbus 0
>   lpt0: Interrupt-driven port
>   ppi0: <generic parallel i/o> on ppbus 0
>   APIC_IO: Testing 8254 interrupt delivery
>   APIC_IO: routing 8254 via pin 2
>   IP packet filtering initialized, divert enabled, rule-based 
>   forwarding
>   enabled, default to accept, logging limited to 100 packets/entry
>   DUMMYNET initialized (990504)
>   BRIDGE 981214, have 6 interfaces
>   -- index 1 de0 type 6 phy 0 addrl 6 addr 00.a0.cc.66.32.97
>   IP Filter: initialized.  Default = pass all, Logging = enabled
>   Waiting 15 seconds for SCSI devices to settle 
>   SMP: AP CPU #1 Launched!
>   de0: enabling 10baseT port   
>   
>   
>   
>   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  Sat Jul 31  8:59:27 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16])
	by hub.freebsd.org (Postfix) with ESMTP
	id D81A214D2E; Sat, 31 Jul 1999 08:59:12 -0700 (PDT)
	(envelope-from maniattb@cs.rpi.edu)
Received: from cs.rpi.edu (maniattb@dishwasher.cs.rpi.edu [128.213.8.31])
	by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id LAA45437;
	Sat, 31 Jul 1999 11:58:53 -0400 (EDT)
Message-Id: <199907311558.LAA45437@cs.rpi.edu>
X-Mailer: exmh version 2.0.1 12/23/97
To: wwoods@cybcon.com
Cc: Doug <Doug@gorean.org>, freebsd-smp@FreeBSD.ORG,
	freebsd-questions@FreeBSD.ORG, maniattb@cs.rpi.edu
Subject: Re: CPU Useage 
In-reply-to: Your message of "Fri, 30 Jul 1999 18:26:22 PDT."
             <XFMail.990730182622.wwoods@cybcon.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 31 Jul 1999 11:58:51 -0400
From: Bill Maniatty <maniattb@cs.rpi.edu>
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

I think xcpustate will show dual cpu usage.

Regards:

Bill





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message


From owner-freebsd-smp  Sat Jul 31  9:22:56 1999
Delivered-To: freebsd-smp@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id 85FC214F7C; Sat, 31 Jul 1999 09:22:54 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id JAA99944;
	Sat, 31 Jul 1999 09:22:38 -0700 (PDT)
	(envelope-from dillon)
Date: Sat, 31 Jul 1999 09:22:38 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199907311622.JAA99944@apollo.backplane.com>
To: tcobb@staff.circle.net
Cc: blapp@attic.ch, freebsd-current@FreeBSD.ORG,
	freebsd-smp@FreeBSD.ORG
Subject: Re: RE: network got stuck during high nfs-load
References:  <A0CFA284C004D211B7EE0060082F32A41F2830@freya.circle.net>
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

    The way I usually handle pseudo users via sendmail is to route
    them via a dummy subdomain.

    So, for example, my main server is 'apollo.backplane.com'.  I route
    mail destined for 'pop.apollo.backplane.com' to my special pop mail
    backend.

    My /etc/aliases and other forwarding tables then simply map the 
    usernames that I want to route to the dummy domain.  For example,
    the pop user 'fubar' would be mapped to 'fubar@pop.apollo.backplane.com',
    where 'fubar' does not exist in the password file or anything like that.

    In sendmail, it is a simple addition to ruleset 98:

R$+ + $* < @ pplus . $=w > $*		$#popplus $: $1 < @ pplus . $3 > $4
R$+ + $* < @ pplus . $=w . > $*		$#popplus $: $1 < @ pplus . $3 > $4

R$* < @ pplus . $=w > $*		$#popplus $: $1 < @ pplus . $2 > $3
R$* < @ pplus . $=w . > $*		$#popplus $: $1 < @ pplus . $2 > $3


    And then add the new mailer:

Mpopplus,	P=/usr/local/bin/dpopmail, F=SDEFhlMsu, S=10/30, R=20/40,  
		U=dpop, A=dpopmail $u   

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message