From owner-freebsd-smp Mon Jul 5 12:59:26 1999 Delivered-To: freebsd-smp@freebsd.org Received: from gera.nix.nns.ru (ns.nns.ru [194.135.102.10]) by hub.freebsd.org (Postfix) with ESMTP id 2460A14F1A for ; Mon, 5 Jul 1999 12:59:21 -0700 (PDT) (envelope-from dflit@nns.ru) Received: (from dflit@localhost) by gera.nix.nns.ru (8.9.1a/8.7.3) id XAA03329 for freebsd-smp@freebsd.org; Mon, 5 Jul 1999 23:59:20 +0400 (MSD) To: freebsd-smp@freebsd.org Message-ID: Organization: National Electronic Library Date: Mon, 5 Jul 1999 23:59:20 +0400 (MSD) X-Mailer: Mail/@ [v2.45 FreeBSD] From: Dmitry Flitmann Reply-To: dflit@nns.ru Error-to: dflit@nns.ru Subject: Intel SC450NX hangs under high disk/memory load (2) Lines: 45 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi there - again :) I've read kern/11330 bug report from the GNATS database, and tried to compile kernel which uses only 512M RAM. Everything seems to work fine. Any ideas - are there any problems with memory over 512M - either kernel, or maybe some drivers/controllers? >We've got a "fast" computer for our database: >Intel SC450NX, 2xXeon/500MHz/512K cache, >1G RAM (4x256 50ns ECC EDO Buffered DRAM from Samsung), SymBios U2W SCSI onboard, >2xPCI, 3x18G Seagate Cheetah, >OS - FreeBSD 3.2-STABLE - also tried 3.1,3.2-RELEASE, 4.0-CURRENT. > >At first, we had to patch NCR driver - then it worked fine for some time. > >Under high load disks/memory load (copying a large directory tree from >one disk to another - ~200Mb, ~150K files) a problem appears - >after ~15 minutes of hard work the system hangs - >it does not create any new processes anymore. > >When we try ktrace, it shows last operation "namei" (while opening >file for reading). > >3.2-RELEASE & -STABLE & 4.0-CURRENT die silently, >3.1 reports "Page fault while in kernel mode". > >fault virtual address diffes, once it was 0x0. > >Our first idea was that the problem is in a patched ncr driver, so we >have replaced SymBios with Adaptec 2940U2W, but effect persists. > >CPU load is not very high, there are not a lot of processes, >and no one keeps a lot of files open simultaneously. >? >MAXUSERS is 512 (or 256) > >We tried both SMP and single-processor kernels. Sincerely, Dmitry Flitman National News Service/National Electronic Library. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Jul 5 22: 1:15 1999 Delivered-To: freebsd-smp@freebsd.org Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14]) by hub.freebsd.org (Postfix) with ESMTP id 6EFEE15141 for ; Mon, 5 Jul 1999 22:01:07 -0700 (PDT) (envelope-from andymac@bullseye.apana.org.au) Received: from bullseye.apana.org.au (uucp@localhost) by posgate.acis.com.au (8.9.2/8.9.2/Debian/GNU) with UUCP id OAA23841; Tue, 6 Jul 1999 14:54:48 +1000 (EST) Received: from bullseye.apana.org.au (central.apana.org.au [203.9.107.245]) by bullseye.apana.org.au (8.8.8/8.8.8) with SMTP id JAA09267; Tue, 6 Jul 1999 09:11:41 +1000 (EST) (envelope-from andymac@bullseye.apana.org.au) Date: Tue, 6 Jul 1999 09:03:42 +1000 (EST) From: Andrew MacIntyre To: Dmitry Flitmann Cc: freebsd-smp@FreeBSD.ORG Subject: Re: Intel SC450NX hangs under high disk/memory load (2) In-Reply-To: Message-ID: X-X-Sender: andymac@bullseye.apana.org.au 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, 5 Jul 1999, Dmitry Flitmann wrote: > I've read kern/11330 bug report from the GNATS database, > and tried to compile kernel which uses only 512M RAM. > > Everything seems to work fine. > > Any ideas - are there any problems with memory over 512M - > either kernel, or maybe some drivers/controllers? {...} > >MAXUSERS is 512 (or 256) I haven't seen any responses to your query via the list, so... Given that I remember your described usage patterns, I seem to recall seeing recommendations to use a smaller MAXUSERS value (say 128) and directly modify the specific values which may need to be increased, such as NMBCLUSTERS (hope I got that right...). I think it had to do with the MAXUSERS calculation causing kernel memory usage to expand too much. I also remember seeing a reference to Linux having a max of 1GB-64MB RAM, but was reasonably sure FreeBSD's limit was 4GB-64MB (but to use this much still required some recent bits from current). You may want to try searching the lists for more info on MAXUSERS and NMBCLUSTERS. -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andrew.macintyre@aba.gov.au (work) | Snail: PO Box 370 andymac@bullseye.apana.org.au (play) | Belconnen ACT 2616 Fido: Andrew MacIntyre, 3:620/243.18 | Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jul 6 9: 5:20 1999 Delivered-To: freebsd-smp@freebsd.org Received: from par28.ma.ikos.com (par28.ma.ikos.com [137.103.105.228]) by hub.freebsd.org (Postfix) with ESMTP id 0611F1545C for ; Tue, 6 Jul 1999 09:05:16 -0700 (PDT) (envelope-from tich@par28.ma.ikos.com) Received: from [[UNIX: localhost]] ([[UNIX: localhost]]) by par28.ma.ikos.com (8.8.7/8.8.7) id MAA30453; Tue, 6 Jul 1999 12:03:21 -0400 From: Richard Cownie To: Andrew MacIntyre , Dmitry Flitmann Subject: Re: Intel SC450NX hangs under high disk/memory load (2) Date: Tue, 6 Jul 1999 11:49:18 -0400 X-Mailer: KMail [version 1.1.0] Content-Type: text/plain Cc: freebsd-smp@FreeBSD.ORG References: MIME-Version: 1.0 Message-Id: <99070612032100.30449@par28.ma.ikos.com> Content-Transfer-Encoding: 8bit X-KMail-Mark: Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 05 Jul 1999, Andrew MacIntyre wrote: > On Mon, 5 Jul 1999, Dmitry Flitmann wrote: > > > Any ideas - are there any problems with memory over 512M - > > either kernel, or maybe some drivers/controllers? > > {...} > > > >MAXUSERS is 512 (or 256) > > I haven't seen any responses to your query via the list, so... > > Given that I remember your described usage patterns, I seem to recall > seeing recommendations to use a smaller MAXUSERS value (say 128) and > directly modify the specific values which may need to be increased, such > as NMBCLUSTERS (hope I got that right...). I think it had to do with the > MAXUSERS calculation causing kernel memory usage to expand too much. I'm running 4.0-CURRENT from about 6 June on an SC450NX with 4 x Xeon-500 and 4GB DRAM. The kernel is built with these sizing options: maxusers 256 options VM_KMEM_SIZE_MAX=0x20000000UL options NMBCLUSTERS=8192 If you don't set VM_KMEM_SIZE_MAX, I believe the default is 80MB, which is not much for a machine with >1GB of DRAM. However, this would probably cause a panic rather than the behaviour you're seeing. I believe Linux is good for approx 1GB of DRAM, and latest kernels can be tuned to support 2GB DRAM. As far as I know FreeBSD 3.x supports 2GB DRAM (not sure about 3GB ?) - you need a recent 4.0-CURRENT to support the full 4GB. It turns out to be 4GB - 97MB, because the SC450NX chipset/bios put some of the DRAM above the 4GB address boundary. Richard Cownie (tich@ma.ikos.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 6 16: 2: 9 1999 Delivered-To: freebsd-smp@freebsd.org Received: from gatekeeper.imall.com (gatekeeper.imall.com [209.63.195.8]) by hub.freebsd.org (Postfix) with ESMTP id C52CD15071 for ; Tue, 6 Jul 1999 16:02:03 -0700 (PDT) (envelope-from rfleming@cc.weber.edu) Received: (from mail@localhost) by gatekeeper.imall.com (8.9.1a/8.9.1) id RAA03475 for ; Tue, 6 Jul 1999 17:02:02 -0600 (MDT) Received: from mail.imall.com(10.0.6.84) by gatekeeper.imall.com via smap (V2.1) id xma003470; Tue, 6 Jul 99 17:02:01 -0600 Received: from cc.weber.edu (spottedcow.imall.com.6.0.10.in-addr.arpa [10.0.6.139] (may be forged)) by mail.imall.com (8.9.1a/8.9.1) with ESMTP id RAA28021 for ; Tue, 6 Jul 1999 17:02:00 -0600 (MDT) Message-ID: <37823AF4.7EA3BDA@cc.weber.edu> Date: Tue, 06 Jul 1999 17:20:53 +0000 From: rob X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 Cc: freebsd-smp@FreeBSD.ORG Subject: Re: Intel SC450NX hangs under high disk/memory load (2) References: <99070612032100.30449@par28.ma.ikos.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just a thought. Richard Cownie wrote: > On Mon, 05 Jul 1999, Andrew MacIntyre wrote: > > On Mon, 5 Jul 1999, Dmitry Flitmann wrote: > > > > > Any ideas - are there any problems with memory over 512M - > > > either kernel, or maybe some drivers/controllers? > > > > {...} > > > > > >MAXUSERS is 512 (or 256) I was playing with the setting a while ago trying to get better performance on a dual pII 400 with 512meg ram. I had hang problems similar to this. I read some notes that stated that this has actually very little to do with the number of users that can access a machine? Anyway I would try pushing this number back down. It uses a very large amount of memory. > > > > > I haven't seen any responses to your query via the list, so... > > > > Given that I remember your described usage patterns, I seem to recall > > seeing recommendations to use a smaller MAXUSERS value (say 128) and > > directly modify the specific values which may need to be increased, such > > as NMBCLUSTERS (hope I got that right...). I think it had to do with the > > MAXUSERS calculation causing kernel memory usage to expand too much. > > I'm running 4.0-CURRENT from about 6 June on an SC450NX with > 4 x Xeon-500 and 4GB DRAM. The kernel is built with these sizing > options: > > maxusers 256 > options VM_KMEM_SIZE_MAX=0x20000000UL > options NMBCLUSTERS=8192 > > If you don't set VM_KMEM_SIZE_MAX, I believe the default is 80MB, > which is not much for a machine with >1GB of DRAM. However, this > would probably cause a panic rather than the behaviour you're > seeing. > > I believe Linux is good for approx 1GB of DRAM, and latest kernels > can be tuned to support 2GB DRAM. As far as I know FreeBSD 3.x > supports 2GB DRAM (not sure about 3GB ?) - you need a recent 4.0-CURRENT > to support the full 4GB. It turns out to be 4GB - 97MB, because > the SC450NX chipset/bios put some of the DRAM above the 4GB address > boundary. > > Richard Cownie (tich@ma.ikos.com) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-smp" in the body of the message Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jul 6 22:32:59 1999 Delivered-To: freebsd-smp@freebsd.org Received: from hotmail.com (f227.hotmail.com [207.82.251.118]) by hub.freebsd.org (Postfix) with SMTP id 347711511C for ; Tue, 6 Jul 1999 22:32:54 -0700 (PDT) (envelope-from the_hermit665@hotmail.com) Received: (qmail 76441 invoked by uid 0); 7 Jul 1999 05:32:53 -0000 Message-ID: <19990707053253.76440.qmail@hotmail.com> Received: from 216.160.92.141 by www.hotmail.com with HTTP; Tue, 06 Jul 1999 22:32:52 PDT X-Originating-IP: [216.160.92.141] From: Cosmic 665 To: freebsd-smp@FreeBSD.ORG Subject: "Kernel" SYSTEM HANGS and halts Date: Tue, 06 Jul 1999 22:32:52 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Fellow FreeBSD Users; I'm somewhat new to FreeBSD. I've been having trouble setting up "SMP" under FreeBSD. I compile my kernel with all the Default settings for SMP, and when I do so, my machine freezes at "switching to wd0s1 or wd0s2" everytime I load the kernel. when I use a generic kernel i'm fine, but when I use the kernel with SMP and APIC it freezes. Once a "blue moon" it will load and when it does, if I switch to a VC in Xfree86, my computer freezes every time. Could someone please tell me what to do to stop this.?? Here are my system specs; FreeBSD 3.2 (this also happens to me on 3.0) MotherBoard: PCCHIPS dual PII Motherboard 233-333MHZ CPU's: INtel 333Mhz x2 Video Cards: #9 Revolution 3D 8MB & 2 Creative labs Voodoo II's 8MB SoundCard: AWE 32 2MB RAM HD: Western Digital Caviar 6.4 Gig 40x CDROM Drive using a NEtgear PCI network card the "de0" driver a Digital chipset here's my Kernel source note: whenever I set my CPU_type for only "I586_cpu" I get a kernel panic. could someone plz tell my why?? Also, if I do get a kernel panic, how do I "switch Back" to the GENERIC kernel without a bootdisk?? In 3.2 I'm clueless?? # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: HERMITAGE,v 1.143.2.12 1999/05/14 15:12:26 jkh Exp $ machine "i386" cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident HERMITAGE maxusers 32 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on wd0 # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 controller pnp0 controller eisa0 controller pci0 controller snd0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device acd0 #IDE CD-ROM device wfd0 #IDE Floppy (e.g. LS-120) ########## Sound Stuff ########### device sb0 at isa? port 0x220 irq 7 conflicts drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x38a device awe0 at isa? port 0x620 #device mpu0 at isa? port 0x330 irq 6 drq 0 # 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 psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at isa? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device sio2 at isa? disable port "IO_COM3" tty irq 5 device sio3 at isa? disable port "IO_COM4" tty irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 net irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? #controller vpo0 at ppbus? # # The following Ethernet NICs are all PCI devices. # device ax0 # ASIX AX88140A device de0 # DEC/Intel DC21x4x (``Tulip'') device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) device mx0 # Macronix 98713/98715/98725 (``PMAC'') device pn0 # Lite-On 82c168/82c169 (``PNIC'') device rl0 # RealTek 8129/8139 device tl0 # Texas Instruments ThunderLAN device tx0 # SMC 9432TX (83c170 ``EPIC'') device vr0 # VIA Rhine, Rhine II device vx0 # 3Com 3c590, 3c595 (``Vortex'') device wb0 # Winbond W89C840F device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 device ep0 at isa? port 0x300 net irq 10 device ex0 at isa? port? net irq? device fe0 at isa? port 0x300 net irq ? device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 device lnc0 at isa? port 0x280 net irq 10 drq 0 device ze0 at isa? port 0x300 net irq 10 iomem 0xd8000 device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 device cs0 at isa? port 0x300 net irq ? pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG options SYSVSEM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 8 #Berkeley packet filter thanks :) -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 6 22:41: 3 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 C115314BD2 for ; Tue, 6 Jul 1999 22:41:01 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA88039; Tue, 6 Jul 1999 22:41:00 -0700 (PDT) (envelope-from dillon) Date: Tue, 6 Jul 1999 22:41:00 -0700 (PDT) From: Matthew Dillon Message-Id: <199907070541.WAA88039@apollo.backplane.com> To: Cosmic 665 Cc: freebsd-smp@FreeBSD.ORG Subject: Re: "Kernel" SYSTEM HANGS and halts References: <19990707053253.76440.qmail@hotmail.com> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :Hello Fellow FreeBSD Users; : : I'm somewhat new to FreeBSD. I've been having trouble setting up "SMP" :under FreeBSD. I compile my kernel with all the Default settings for SMP, :and when I do so, my machine freezes at "switching to wd0s1 or wd0s2" :everytime I load the kernel. when I use a generic kernel i'm fine, but when :I use the kernel with SMP and APIC it freezes. Once a "blue moon" it will :load and when it does, if I switch to a VC in Xfree86, my computer freezes :every time. : Could someone please tell me what to do to stop this.?? : :Here are my system specs; : :FreeBSD 3.2 (this also happens to me on 3.0) :MotherBoard: PCCHIPS dual PII Motherboard 233-333MHZ :CPU's: INtel 333Mhz x2 :.. :note: whenever I set my CPU_type for only "I586_cpu" I get a kernel panic. :could someone plz tell my why?? Also, if I do get a kernel panic, how do I :"switch Back" to the GENERIC kernel without a bootdisk?? In 3.2 I'm :clueless?? A pentium-II cpu uses a Pentium-PRO core, not a pentium core. In otherwords, those are I686_cpu's you have, not 586's, so you should specify both the I586_cpu and the I686_cpu options. :# To make an SMP kernel, the next two are needed :options SMP # Symmetric MultiProcessor Kernel :options APIC_IO # Symmetric (APIC) I/O :# Optionally these may need tweaked, (defaults shown): :#options NCPU=2 # number of CPUs :#options NBUS=4 # number of busses :#options NAPIC=1 # number of IO APICs :#options NINTR=24 # number of INTs Try specifying the NCPU option specifically. That's all I can think of right offhand. options SMP options APIC_IO options NCP=2 : :thanks :) : : -Cosmic-665 -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jul 6 22:51:16 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 75FB11524D for ; Tue, 6 Jul 1999 22:51:12 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 43923 invoked from network); 7 Jul 1999 05:51:11 -0000 Received: from shell-2.enteract.com (dscheidt@207.229.143.41) by pop3-3.enteract.com with SMTP; 7 Jul 1999 05:51:11 -0000 Date: Wed, 7 Jul 1999 00:51:11 -0500 (CDT) From: David Scheidt To: Matthew Dillon Cc: Cosmic 665 , freebsd-smp@FreeBSD.ORG Subject: Re: "Kernel" SYSTEM HANGS and halts In-Reply-To: <199907070541.WAA88039@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 6 Jul 1999, Matthew Dillon wrote: > :CPU's: INtel 333Mhz x2 > :.. > :note: whenever I set my CPU_type for only "I586_cpu" I get a kernel panic. > :could someone plz tell my why?? Also, if I do get a kernel panic, how do I > :"switch Back" to the GENERIC kernel without a bootdisk?? In 3.2 I'm > :clueless?? At the third stage loader prompt (where it says something like autobooting in 9 seconds. Press Enter to boot immediately, any other key to interupt.) press any other key. You can then type "boot /kernel.GENERIC" to boot the kernel called /kernel.GENERIC. > > A pentium-II cpu uses a Pentium-PRO core, not a pentium core. In > otherwords, those are I686_cpu's you have, not 586's, so you should > specify both the I586_cpu and the I686_cpu options. Is there some reason that you can't just use I686_cpu? I do on my dual PII box, and it works... > > :# To make an SMP kernel, the next two are needed > :options SMP # Symmetric MultiProcessor Kernel > :options APIC_IO # Symmetric (APIC) I/O > :# Optionally these may need tweaked, (defaults shown): > :#options NCPU=2 # number of CPUs > :#options NBUS=4 # number of busses > :#options NAPIC=1 # number of IO APICs > :#options NINTR=24 # number of INTs > > Try specifying the NCPU option specifically. That's all I can think of > right offhand. Run mptable, and set your kernel to explicitly use what it returns. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue Jul 6 23: 5:50 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 ACF3215386 for ; Tue, 6 Jul 1999 23:05:48 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA88336; Tue, 6 Jul 1999 23:05:46 -0700 (PDT) (envelope-from dillon) Date: Tue, 6 Jul 1999 23:05:46 -0700 (PDT) From: Matthew Dillon Message-Id: <199907070605.XAA88336@apollo.backplane.com> To: David Scheidt Cc: Cosmic 665 , freebsd-smp@FreeBSD.ORG Subject: Re: "Kernel" SYSTEM HANGS and halts References: Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :> A pentium-II cpu uses a Pentium-PRO core, not a pentium core. In :> otherwords, those are I686_cpu's you have, not 586's, so you should :> specify both the I586_cpu and the I686_cpu options. : :Is there some reason that you can't just use I686_cpu? I do on my dual PII :box, and it works... Oh sure, that will work, but I haven't found that removing the I586_cpu improves performance any and I've shot myself in the foot in the past by not having it - I have a mix of machines and sometimes I shift boot disks around. The K6-II's are recognized as 586 cpu's. -Matt Matthew Dillon :Run mptable, and set your kernel to explicitly use what it returns. : : :David Scheidt : : : :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 Thu Jul 8 5: 0: 8 1999 Delivered-To: freebsd-smp@freebsd.org Received: from mta1.mail.telepac.pt (mail1.telepac.pt [194.65.3.53]) by hub.freebsd.org (Postfix) with ESMTP id 69B63150A9 for ; Thu, 8 Jul 1999 04:59:50 -0700 (PDT) (envelope-from jpedras@mail.telepac.pt) Received: from manecao.tafkap.priv ([194.65.204.223]) by mta1.mail.telepac.pt (InterMail v03.02.07 118-124-101) with ESMTP id <19990708120003.HKL2105@manecao.tafkap.priv> for ; Thu, 8 Jul 1999 13:00:03 +0100 Content-Length: 457 Message-ID: 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: Thu, 08 Jul 1999 12:59:33 +0100 (BST) From: Joao Pedras To: freebsd-smp@freebsd.org Subject: assign cpu Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, is it possible to assign a task to a particular cpu ? Thanks Joao ------------------------------------------------------------------------ Sent on 08-Jul-99 at 12:58:40 Powered by FreeBSD -> http://www.freebsd.org <- "The Power to Serve" PGP key available upon request or may be cut at http://members.tripod.com/fbsd/pgpkey.html ------------------------------------------------------------------------ There is no time like the pleasant. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jul 8 5:55:39 1999 Delivered-To: freebsd-smp@freebsd.org Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by hub.freebsd.org (Postfix) with ESMTP id 656DA150B3 for ; Thu, 8 Jul 1999 05:55:19 -0700 (PDT) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id OAA13973 for ; Thu, 8 Jul 1999 14:55:14 +0200 (MET DST) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.2/8.6.9) id OAA66113 for smp@freebsd.org; Thu, 8 Jul 1999 14:55:14 +0200 (CEST) Date: Thu, 8 Jul 1999 14:55:14 +0200 (CEST) From: Christoph Kukulies Message-Id: <199907081255.OAA66113@gil.physik.rwth-aachen.de> To: smp@freebsd.org Subject: SMP comparisons Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Have there been recent comparisons between quality of SMP between FreeBSD and the other free unices and non-free OSs? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jul 8 7:59:45 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 33F4215507 for ; Thu, 8 Jul 1999 07:59:41 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id HAA40150; Thu, 8 Jul 1999 07:59:29 -0700 (PDT) (envelope-from dillon) Date: Thu, 8 Jul 1999 07:59:29 -0700 (PDT) From: Matthew Dillon Message-Id: <199907081459.HAA40150@apollo.backplane.com> To: Christoph Kukulies Cc: smp@FreeBSD.ORG Subject: Re: SMP comparisons References: <199907081255.OAA66113@gil.physik.rwth-aachen.de> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :Have there been recent comparisons between quality of SMP :between FreeBSD and the other free unices and non-free OSs? : :-- :Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD is behind. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jul 8 9:27:27 1999 Delivered-To: freebsd-smp@freebsd.org Received: from hotmail.com (f195.hotmail.com [207.82.251.84]) by hub.freebsd.org (Postfix) with SMTP id 702A614CF0 for ; Thu, 8 Jul 1999 09:27:24 -0700 (PDT) (envelope-from the_hermit665@hotmail.com) Received: (qmail 16605 invoked by uid 0); 8 Jul 1999 16:27:24 -0000 Message-ID: <19990708162724.16604.qmail@hotmail.com> Received: from 216.160.92.141 by www.hotmail.com with HTTP; Thu, 08 Jul 1999 09:27:23 PDT X-Originating-IP: [216.160.92.141] From: Cosmic 665 To: freebsd-smp@FreeBSD.ORG Subject: Re: SMP comparisons Date: Thu, 08 Jul 1999 09:27:23 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org NO!!!!! FreeBSD is ahead... maybe behind a little... either way, we kick linux's A$$ p.s. I gave a copy of 3.0 to a friend of mine to compare between linux & FreeBSD on SMP and maybe even NT. I'll be hearing back from him on thouse results. -cosmic-665 >From: Matthew Dillon >To: Christoph Kukulies >CC: smp@FreeBSD.ORG >Subject: Re: SMP comparisons >Date: Thu, 8 Jul 1999 07:59:29 -0700 (PDT) >From owner-freebsd-smp@FreeBSD.ORG Thu Jul 08 08:03:34 1999 >Received: from [204.216.27.18] by hotmail.com (1.5) with SMTP id >MHotMailB94E08C401F7D82197B1CCD81B1271AD0; Thu Jul 08 08:03:34 1999 >Received: by hub.freebsd.org (Postfix, from userid 538)id 6FCF71550C; Thu, >8 Jul 1999 07:59:45 -0700 (PDT) >Received: from localhost (localhost [127.0.0.1])by hub.freebsd.org >(Postfix) with SMTPid 5E2051CD88D; Thu, 8 Jul 1999 07:59:45 -0700 >(PDT)(envelope-from owner-freebsd-smp) >Received: by hub.freebsd.org (bulk_mailer v1.12); Thu, 8 Jul 1999 07:59:45 >-0700 >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 33F4215507for ; >Thu, 8 Jul 1999 07:59:41 -0700 (PDT)(envelope-from >dillon@apollo.backplane.com) >Received: (from dillon@localhost)by apollo.backplane.com (8.9.3/8.9.1) id >HAA40150;Thu, 8 Jul 1999 07:59:29 -0700 (PDT)(envelope-from dillon) >Message-Id: <199907081459.HAA40150@apollo.backplane.com> >References: <199907081255.OAA66113@gil.physik.rwth-aachen.de> >Sender: owner-freebsd-smp@FreeBSD.ORG >X-Loop: FreeBSD.org >Precedence: bulk > >:Have there been recent comparisons between quality of SMP >:between FreeBSD and the other free unices and non-free OSs? >: >:-- >:Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > > FreeBSD is behind. > > -Matt > Matthew Dillon > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-smp" in the body of the message ______________________________________________________ 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 Thu Jul 8 9:34:27 1999 Delivered-To: freebsd-smp@freebsd.org Received: from alpha.netaccess.on.ca (alpha.netaccess.on.ca [199.243.225.10]) by hub.freebsd.org (Postfix) with ESMTP id 640EC14D41 for ; Thu, 8 Jul 1999 09:34:21 -0700 (PDT) (envelope-from rob@ControlQ.com) Received: from fatlady.controlq.com (dial197.nas.net [199.243.225.197]) by alpha.netaccess.on.ca (8.9.0/8.9.0) with SMTP id MAA21136; Thu, 8 Jul 1999 12:34:18 -0400 (EDT) Date: Thu, 8 Jul 1999 12:34:57 -0400 (EDT) From: "Robert S. Sciuk" To: Cosmic 665 Cc: freebsd-smp@FreeBSD.ORG Subject: Re: SMP comparisons In-Reply-To: <19990708162724.16604.qmail@hotmail.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 8 Jul 1999, Cosmic 665 wrote: > NO!!!!! FreeBSD is ahead... maybe behind a little... either way, we kick > linux's A$$ > > > p.s. I gave a copy of 3.0 to a friend of mine to compare between linux & > FreeBSD on SMP and maybe even NT. I'll be hearing back from him on thouse > results. > I think we're not where we should be ... what with the GreatBigLock in the Kernel ... however, I've seen some -smp traffic which leads me to believe some very talented individuals are working to rectify this situation ... then FreeBSD should kick some proverbial butt 8-). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jul 8 9:41:17 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 872BE14E1B for ; Thu, 8 Jul 1999 09:41:14 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA40947; Thu, 8 Jul 1999 09:41:14 -0700 (PDT) (envelope-from dillon) Date: Thu, 8 Jul 1999 09:41:14 -0700 (PDT) From: Matthew Dillon Message-Id: <199907081641.JAA40947@apollo.backplane.com> To: Cosmic 665 Cc: freebsd-smp@FreeBSD.ORG Subject: Re: SMP comparisons References: <19990708162724.16604.qmail@hotmail.com> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :NO!!!!! FreeBSD is ahead... maybe behind a little... either way, we kick :linux's A$$ : :p.s. I gave a copy of 3.0 to a friend of mine to compare between linux & :FreeBSD on SMP and maybe even NT. I'll be hearing back from him on thouse :results. : :-cosmic-665 Linux beats our arses on SMP performance, I'm afraid. They've been able to move the tcp stack outside of the big giant lock and have also moved a significant portion of the data copying stuff outside of the big giant lock. And, on top of that, we need to make significant changes to the way our buffer cache works to even approach linux's I/O performance under SMP. I want to move us more towards a UVM model for I/O - i.e. going through the VM subsystem to read and write data rather then VFS subsystem and the notifying the VFS system after the fact for writes. Unfortunately, I doubt that much progress will be made in the current environment. FreeBSD still kicks ass in the reliability department, despite the recent problems with INN and mmap(), and FreeBSD still kicks ass if a system ever has to start paging. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jul 8 10:12:45 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 60EA514D64 for ; Thu, 8 Jul 1999 10:12:39 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA20677; Thu, 8 Jul 1999 13:12:29 -0400 (EDT) Message-Id: <199907081712.NAA20677@cs.rpi.edu> To: Matthew Dillon Cc: Cosmic 665 , freebsd-smp@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: SMP comparisons In-Reply-To: Message from Matthew Dillon of "Thu, 08 Jul 1999 09:41:14 PDT." <199907081641.JAA40947@apollo.backplane.com> Date: Thu, 08 Jul 1999 13:12:20 -0400 From: "David E. Cross" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Unfortunately, I doubt that much progress will be made in the current > environment. Could you elaborate on what you mean by that. Is the environment to which you refer a technical environment, or political issues that are restraining us from making the required and necissary changes? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jul 8 10:21:33 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 2EB3214C02 for ; Thu, 8 Jul 1999 10:21:30 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA41309; Thu, 8 Jul 1999 10:21:17 -0700 (PDT) (envelope-from dillon) Date: Thu, 8 Jul 1999 10:21:17 -0700 (PDT) From: Matthew Dillon Message-Id: <199907081721.KAA41309@apollo.backplane.com> To: "David E. Cross" Cc: Cosmic 665 , freebsd-smp@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: SMP comparisons References: <199907081712.NAA20677@cs.rpi.edu> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org : :> Unfortunately, I doubt that much progress will be made in the current :> environment. : :Could you elaborate on what you mean by that. Is the environment to which you :refer a technical environment, or political issues that are restraining us :from making the required and necissary changes? : :-- :David Cross | email: crossd@cs.rpi.edu :Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd I'm making nasty indirect punches at core. Just ignore me :-) Actually, I think the SMP work could use a little more support from core. It's been excellent work, but it has also been somewhat fragmented. The work on the VFS/BIO subsystem, even with Kirk helping, is going to go slowly no matter what, but it will running worst case without commit privs for me. I've already fallen way behind on tracking down the remaining NFS problems and the VM/mmap problems because of time constraints which are not made better by core's unenlightened stance. In order to make real progress on any of these things current is really going to have to become a development kernel again instead of an 'must always be working' kernel. Like the VM adjustments I made earlier in the year, there are certain pieces of the VFS/BIO subsystem that are going to have to be ripped to shreads later this year before it can be put back together. I think some of the upcoming SMP issues are going to the same: -Matt Matthew Dillon :Rensselaer Polytechnic Institute, | Ph: 518.276.2860 :Department of Computer Science | Fax: 518.276.4033 :I speak only for myself. | WinNT:Linux::Linux:FreeBSD : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jul 8 10:36: 6 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 1B54A14E5F for ; Thu, 8 Jul 1999 10:35:50 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: (from alc@localhost) by cs.rice.edu (8.9.0/8.9.0) id MAA11200; Thu, 8 Jul 1999 12:35:47 -0500 (CDT) Date: Thu, 8 Jul 1999 12:35:46 -0500 From: Alan Cox To: "Robert S. Sciuk" Cc: Cosmic 665 , freebsd-smp@freebsd.org Subject: Re: SMP comparisons Message-ID: <19990708123546.H10611@cs.rice.edu> References: <19990708162724.16604.qmail@hotmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5us In-Reply-To: ; from Robert S. Sciuk on Thu, Jul 08, 1999 at 12:34:57PM -0400 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 08, 1999 at 12:34:57PM -0400, Robert S. Sciuk wrote: > I think we're not where we should be ... what with the GreatBigLock in the > Kernel ... however, I've seen some -smp traffic which leads me to believe > some very talented individuals are working to rectify this situation ... > then FreeBSD should kick some proverbial butt 8-). > Here's what you'll see shortly: 1. Bruce Evans is about to commit some changes to the interrupt management code that removes one impediment to moving (or removing) the giant lock. 2. Luoqi Chen is working on the next step. He's moving some of the interrupt management variables from shared memory to per processor memory. Once these pieces are in place, the *body* of many simple system calls can be executed without the giant lock. Returning from the system call to user level will still, however, require the giant lock. Tackling that problem and making some further changes to the interrupt management code will probably be the next steps, but in the meantime people will be able to experiment with multithreading various system calls. 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 8 11:28:30 1999 Delivered-To: freebsd-smp@freebsd.org Received: from titanic.uninet.kiev.ua (titanic.uninet.kiev.ua [193.125.79.178]) by hub.freebsd.org (Postfix) with ESMTP id 5F13F14D7C; Thu, 8 Jul 1999 11:28:13 -0700 (PDT) (envelope-from roman@uninet.kiev.ua) Received: (from roman@localhost) by titanic.uninet.kiev.ua (8.9.3/8.9.3) id VAA88529; Thu, 8 Jul 1999 21:28:08 +0300 (EEST) From: "Roman D. Sinyuk" Message-Id: <199907081828.VAA88529@titanic.uninet.kiev.ua> Subject: SMP hardware question To: freebsd-questions@freebsd.org Date: Thu, 8 Jul 1999 21:28:08 +0300 (EEST) Cc: freebsd-smp@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All! What motherboard is the better for SMP ? I can choose between: ASUS P2BD Supermicro P6DBU (with AIC 7890 onboard) Supermicro P6DGE Regards. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jul 8 11:37:35 1999 Delivered-To: freebsd-smp@freebsd.org Received: from ns.mt.sri.com (unknown [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 5046C14F67 for ; Thu, 8 Jul 1999 11:37:27 -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 MAA26140; Thu, 8 Jul 1999 12:37:15 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA01531; Thu, 8 Jul 1999 12:37:15 -0600 Date: Thu, 8 Jul 1999 12:37:15 -0600 Message-Id: <199907081837.MAA01531@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Alan Cox Cc: "Robert S. Sciuk" , Cosmic 665 , freebsd-smp@FreeBSD.ORG Subject: Re: SMP comparisons In-Reply-To: <19990708123546.H10611@cs.rice.edu> References: <19990708162724.16604.qmail@hotmail.com> <19990708123546.H10611@cs.rice.edu> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I think we're not where we should be ... what with the GreatBigLock in the > > Kernel ... however, I've seen some -smp traffic which leads me to believe > > some very talented individuals are working to rectify this situation ... > > then FreeBSD should kick some proverbial butt 8-). > > > > Here's what you'll see shortly: > > 1. Bruce Evans is about to commit some changes to the interrupt management > code that removes one impediment to moving (or removing) the giant lock. > > 2. Luoqi Chen is working on the next step. He's moving some > of the interrupt management variables from shared memory to > per processor memory. > > Once these pieces are in place, the *body* of many simple system calls can > be executed without the giant lock. Returning from the system call > to user level will still, however, require the giant lock. Tackling > that problem and making some further changes to the interrupt management > code will probably be the next steps, but in the meantime people will be > able to experiment with multithreading various system calls. Whoo hoo..... Go guys go!!! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jul 8 12: 6:34 1999 Delivered-To: freebsd-smp@freebsd.org Received: from elmls02.ce.mediaone.net (elmls02.ce.mediaone.net [24.131.128.27]) by hub.freebsd.org (Postfix) with ESMTP id A6FE315091; Thu, 8 Jul 1999 12:06:19 -0700 (PDT) (envelope-from burke@mcs.net) Received: from fatman2 (el01-24-131-147-32.ce.mediaone.net [24.131.147.32]) by elmls02.ce.mediaone.net (8.8.7/8.8.7) with ESMTP id OAA28384; Thu, 8 Jul 1999 14:05:38 -0500 (CDT) Message-Id: <4.2.0.58.19990708140056.00aa1920@pop.ce.mediaone.net> X-Sender: johnburke@pop.ce.mediaone.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 08 Jul 1999 14:05:38 -0500 To: "Roman D. Sinyuk" , freebsd-questions@FreeBSD.ORG From: Burke Gallagher Subject: Re: SMP hardware question Cc: freebsd-smp@FreeBSD.ORG In-Reply-To: <199907081828.VAA88529@titanic.uninet.kiev.ua> Mime-Version: 1.0 Content-Type: text/html; charset="us-ascii" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 09:28 PM 7/8/99 +0300, Roman D. Sinyuk wrote:
Hi All!

What motherboard is the better for SMP ? I can choose between:

  ASUS P2BD
  Supermicro P6DBU (with AIC 7890 onboard)
  Supermicro P6DGE

I have 3 of the P6DGEs and have had next to no troubles with them (they are picky about the memory they use, be sure it is of first rate quality, see the approved Supermicro recommended memory page http://www.supermicro.com/TECHSUPPORT/FAQs/Memory_vendors.htm )


Regards.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" 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 Fri Jul 9 2:46:55 1999 Delivered-To: freebsd-smp@freebsd.org Received: from 001101.zer0.org (001101.zer0.org [206.24.105.163]) by hub.freebsd.org (Postfix) with ESMTP id 2A3C61558E for ; Fri, 9 Jul 1999 02:46:52 -0700 (PDT) (envelope-from gsutter@001101.zer0.org) Received: (from gsutter@localhost) by 001101.zer0.org (8.9.2/8.9.2) id CAA71127; Fri, 9 Jul 1999 02:46:36 -0700 (PDT) (envelope-from gsutter) Date: Fri, 9 Jul 1999 02:46:36 -0700 From: Gregory Sutter To: Matthew Dillon Cc: freebsd-smp@FreeBSD.ORG Subject: Re: SMP comparisons Message-ID: <19990709024636.R13537@001101.zer0.org> References: <199907081712.NAA20677@cs.rpi.edu> <199907081721.KAA41309@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907081721.KAA41309@apollo.backplane.com>; from Matthew Dillon on Thu, Jul 08, 1999 at 10:21:17AM -0700 Organization: Zer0 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 08, 1999 at 10:21:17AM -0700, Matthew Dillon wrote: > > The work on the VFS/BIO subsystem, even with Kirk helping, is going > to go slowly no matter what, but it will running worst case without > commit privs for me. I've already fallen way behind on tracking down > the remaining NFS problems and the VM/mmap problems because of time > constraints which are not made better by core's unenlightened stance. > > In order to make real progress on any of these things current is > really going to have to become a development kernel again instead > of an 'must always be working' kernel. Like the VM adjustments > I made earlier in the year, there are certain pieces of the VFS/BIO > subsystem that are going to have to be ripped to shreads later this > year before it can be put back together. I think some of the upcoming > SMP issues are going to the same: Matt, I, as well as several others I've spoken to, am also eager to see you regain your commit privileges. In fact, since USENIX, where I fully expected things to be hashed out so that you _would_ regain them, I've really become discouraged with the opacity and apparent sluggishness of the core team on this issue. I've recently seen you do some excellent design work on subsystems that few have cared to or possessed the ability to work on. I hardly think that you should still be forced to deal with the aftereffects of a situation that should have been over and dealt with long ago. WRT the -CURRENT issue, I also am in agreement with you on that. -CURRENT is a development environment and those who run it must understand that it sometimes may break -- that's the nature of development environments. I would not, at this time, like to see a third branch become necessary (in the form of an -ALPHA or -DEVEL), as I don't think that there is the manpower to care for the release structure of a -DEVEL as well as -CURRENT and -STABLE. There are a lot of big issues that FreeBSD has to confront within the next year, and without some of this major design work, and accompanying breakage, we're going to lose to operating systems that can do SMP and have kernel thread support, among other things. Greg -- Gregory S. Sutter "Software is like sex; it's better mailto:gsutter@pobox.com when it's free." -- Linus Torvalds http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jul 9 3:40:20 1999 Delivered-To: freebsd-smp@freebsd.org Received: from news.IAEhv.nl (news.IAE.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id DDE3015234 for ; Fri, 9 Jul 1999 03:40:16 -0700 (PDT) (envelope-from marc@bowtie.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id MAA11695; Fri, 9 Jul 1999 12:40:09 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by bowtie.nl (8.8.8/8.8.8) with ESMTP id MAA03701; Fri, 9 Jul 1999 12:36:47 +0200 (CEST) (envelope-from marc@bowtie.nl) Message-Id: <199907091036.MAA03701@bowtie.nl> X-Mailer: exmh version 2.0.2 2/24/98 To: Gregory Sutter Cc: Matthew Dillon , freebsd-smp@FreeBSD.ORG Subject: Re: SMP comparisons In-reply-to: gsutter's message of Fri, 09 Jul 1999 02:46:36 -0700. <19990709024636.R13537@001101.zer0.org> Date: Fri, 09 Jul 1999 12:36:47 +0200 From: Marc van Kempen Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Thu, Jul 08, 1999 at 10:21:17AM -0700, Matthew Dillon wrote: > > > > The work on the VFS/BIO subsystem, even with Kirk helping, is going > > to go slowly no matter what, but it will running worst case without > > commit privs for me. I've already fallen way behind on tracking down > > the remaining NFS problems and the VM/mmap problems because of time > > constraints which are not made better by core's unenlightened stance. > > > > In order to make real progress on any of these things current is > > really going to have to become a development kernel again instead > > of an 'must always be working' kernel. Like the VM adjustments > > I made earlier in the year, there are certain pieces of the VFS/BIO > > subsystem that are going to have to be ripped to shreads later this > > year before it can be put back together. I think some of the upcoming > > SMP issues are going to the same: > > Matt, > > I, as well as several others I've spoken to, am also eager to see you > regain your commit privileges. In fact, since USENIX, where I fully > expected things to be hashed out so that you _would_ regain them, I've > really become discouraged with the opacity and apparent sluggishness of > the core team on this issue. I've recently seen you do some excellent > design work on subsystems that few have cared to or possessed the > ability to work on. I hardly think that you should still be forced to > deal with the aftereffects of a situation that should have been over > and dealt with long ago. > > WRT the -CURRENT issue, I also am in agreement with you on that. > -CURRENT is a development environment and those who run it must > understand that it sometimes may break -- that's the nature of > development environments. I would not, at this time, like to see a > third branch become necessary (in the form of an -ALPHA or -DEVEL), as > I don't think that there is the manpower to care for the release > structure of a -DEVEL as well as -CURRENT and -STABLE. There are a > lot of big issues that FreeBSD has to confront within the next year, > and without some of this major design work, and accompanying breakage, > we're going to lose to operating systems that can do SMP and have > kernel thread support, among other things. > I wholeheartedly agree, I must say I don't understand -core in this respect either. Sure I can understand that people feel threatened (or feel the stability of the system is threatened) by someone going through the code with the energy that Matt has displayed, especially when the code is so complicated and fragile, and a good review process should be in place. On the other hand doing nothing about it will only result in FreeBSD falling behind with respect to new developments and drive away talented *and* willing developers, and surely that is somehting worth the time and attention of -core, or so one would hope! Regards, Marc. ---------------------------------------------------- Marc van Kempen BowTie Technology Email: marc@bowtie.nl WWW & Databases tel. +31 40 2 43 20 65 fax. +31 40 2 44 21 86 http://www.bowtie.nl ---------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jul 9 12:44:27 1999 Delivered-To: freebsd-smp@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 5CB9B14EA2 for ; Fri, 9 Jul 1999 12:44:26 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id MAA27325; Fri, 9 Jul 1999 12:43:26 -0700 (PDT) Date: Fri, 9 Jul 1999 12:43:25 -0700 (PDT) From: Julian Elischer To: Marc van Kempen Cc: Gregory Sutter , Matthew Dillon , freebsd-smp@FreeBSD.ORG Subject: Re: SMP comparisons In-Reply-To: <199907091036.MAA03701@bowtie.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 9 Jul 1999, Marc van Kempen wrote: > > On Thu, Jul 08, 1999 at 10:21:17AM -0700, Matthew Dillon wrote: > I wholeheartedly agree, I must say I don't understand -core in this > respect either. > > Sure I can understand that people feel threatened (or feel the stability of > the system is threatened) by > someone going through the code with the energy that Matt has displayed, > especially when the code is so complicated and fragile, and a good > review process should be in place. On the other hand doing nothing about > it will only result in FreeBSD falling behind with respect to new > developments and drive away talented *and* willing developers, and surely > that is somehting worth the time and attention of -core, or so one > would hope! Basically there are two major groups of people in core as far as I can see on this issue.. those who rabidly don't want Matt to get commit privs. They give many excuses but in my opinion the real reason is that they don't feel qualified to clean up after him if something goes wrong and are afraid that it might come to that, and those who have less strong feelings but don't want to go against those with strong feelings. This is the impression I get from talking to many of them. In my opinion almost everything else you hear is an excuse. The main motivating factor for those who have strong feeling in the matter is fear. Either fear that -current will be destabilised (Well DUH, Helloooo, It's -current...) or fear that Matt will be a divisive influence. (go figure) julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jul 9 13:15: 6 1999 Delivered-To: freebsd-smp@freebsd.org Received: from gemini.bnc.net (gemini.bnc.net [195.247.233.33]) by hub.freebsd.org (Postfix) with ESMTP id 17F7914D92 for ; Fri, 9 Jul 1999 13:14:44 -0700 (PDT) (envelope-from ap@bnc.net) Received: (from ap@localhost) by gemini.bnc.net (8.9.3/8.9.3) id WAA77794; Fri, 9 Jul 1999 22:15:27 +0200 (CEST) (envelope-from ap) Date: Fri, 9 Jul 1999 22:15:27 +0200 From: Achim Patzner To: Julian Elischer Cc: Marc van Kempen , Gregory Sutter , Matthew Dillon , freebsd-smp@FreeBSD.ORG Subject: Re: SMP comparisons Message-ID: <19990709221527.D17869@bnc.net> References: <199907091036.MAA03701@bowtie.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Julian Elischer on Fri, Jul 09, 1999 at 12:43:25PM -0700 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 09, 1999 at 12:43:25PM -0700, Julian Elischer wrote: > Basically there are two major groups of people in core as far as I can see > on this issue.. those who rabidly don't want Matt to get commit privs. Sometimes I'm wondering who "the core" is anyway. But I just finished rereading Dan Simmon's four Hyperion books. I guess Matt should stop working for some weeks and read them too, just for the fun of it and watching the holy core getting kicked around. > They give many excuses but in my opinion the real reason is that they > don't feel qualified to clean up after him if something goes wrong and are > afraid that it might come to that, and those who have less strong feelings > but don't want to go against those with strong feelings. Applying all I learnt in a number of psychology classes I'd say they are scared that he might be better. > In my opinion almost everything else you hear is an excuse. Excuses? I'm more and more getting the impression of little local tyrants jealously guarding their territory. The last time this happened we suddenly had FreeBSD. Sorry - the last time this happened we gained yet another *BSD called OpenBSD. Great. I like this Balkanization. Instead of tackling the problems with enough manpower every wheel has to be invented at least thrice. And if the core is going on like this we'l probavly get yab. > The main motivating factor for those who have strong feeling in the matter > is fear. Either fear that -current will be destabilised (Well DUH, > Helloooo, It's -current...) or fear that Matt will be a divisive > influence. (go figure) I'd second the second. And I guess the should ask themselves why people are running -current on production machines... Achim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Jul 9 15:56: 9 1999 Delivered-To: freebsd-smp@freebsd.org Received: from oldnews.quick.net (unknown [207.212.170.1]) by hub.freebsd.org (Postfix) with ESMTP id 7113A14E10 for ; Fri, 9 Jul 1999 15:56:03 -0700 (PDT) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id PAA08867; Fri, 9 Jul 1999 15:56:01 -0700 (PDT) Date: Fri, 9 Jul 1999 15:56:01 -0700 (PDT) From: "Steven P. Donegan" To: freebsd-smp@freebsd.org Subject: Motherboard options Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What options are there for quad processor motherboards that are known to successfully run FreeBSD SMP? Thanks in advance for any pointers. Steven P. Donegan Sr. Engineer WANG Global To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message