From owner-freebsd-smp Sun May 5 19:12: 1 2002 Delivered-To: freebsd-smp@freebsd.org Received: from sharmas.dhs.org (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by hub.freebsd.org (Postfix) with ESMTP id 24FE537B400 for ; Sun, 5 May 2002 19:11:58 -0700 (PDT) Received: by sharmas.dhs.org (Postfix, from userid 500) id 2E82A5E6FA; Sun, 5 May 2002 19:11:57 -0700 (PDT) Date: Sun, 5 May 2002 19:11:57 -0700 From: Arun Sharma To: Terry Lambert Cc: freebsd-smp@freebsd.org Subject: Re: hlt when idle? Message-ID: <20020506021157.GA30659@sharma-home.net> References: <15567.62317.677224.3470@grasshopper.cs.duke.edu> <3CD022A2.FACD21E9@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3CD022A2.FACD21E9@mindspring.com> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, May 01, 2002 at 10:15:14AM -0700, Terry Lambert wrote: Terry, > In theory, you want to run in "virtual wire mode", which means > that the CPUs get the interrupt, and then contend in order to > see who services it. I think you're confused between "virtual wire mode" and the "Symmetric I/O mode" for quite some time (going by your previous messages on the topic). Virtual wire mode is for DOS compatibility. Symmetric I/O mode is what most MP operating systems use. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon May 6 1:10:53 2002 Delivered-To: freebsd-smp@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 0B97837B401 for ; Mon, 6 May 2002 01:10:49 -0700 (PDT) Received: from pool0126.cvx22-bradley.dialup.earthlink.net ([209.179.198.126] helo=mindspring.com) by pintail.mail.pas.earthlink.net with esmtp (Exim 3.33 #2) id 174dZq-0000mM-00; Mon, 06 May 2002 01:10:35 -0700 Message-ID: <3CD63A3A.DF96520A@mindspring.com> Date: Mon, 06 May 2002 01:09:30 -0700 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Arun Sharma Cc: freebsd-smp@freebsd.org Subject: Re: hlt when idle? References: <15567.62317.677224.3470@grasshopper.cs.duke.edu> <3CD022A2.FACD21E9@mindspring.com> <20020506021157.GA30659@sharma-home.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Arun Sharma wrote: > On Wed, May 01, 2002 at 10:15:14AM -0700, Terry Lambert wrote: > > Terry, > > > In theory, you want to run in "virtual wire mode", which means > > that the CPUs get the interrupt, and then contend in order to > > see who services it. > > I think you're confused between "virtual wire mode" and the > "Symmetric I/O mode" for quite some time (going by your previous > messages on the topic). > > Virtual wire mode is for DOS compatibility. Symmetric I/O mode is what > most MP operating systems use. Yes, I already made this (embarrassing!) determination on my own; see my other posting. By way of further elaboration... I read about both back in October of 1994, when I got my first FreeBSD SMP system running, and the Intel MP Spec was actually 1.1, not 1.4 (running using Jack Vogel's original FreeBSD SMP patches, which I redistributed, and which were the basis for the original current SMP work). It wasn't entirely relevent, since there was a single kernel entry lock, and I didn't have any SMP hardware of my own until June of 1995, so I didn't bother treating the document as being of high importance (i.e. deserving of rote memorization). The mistake really came about when, rather than referring back to a memorized copy of the document, I derived the meaning from the memorized digested combinations of the words from the document themselves ("virtual wire" implies bussed delivery to a single virtual interrupt wire, which is not what it really means in the context of the Intel MP specification), which in turn led to my long standing mistake (but doesn't excuse it). Since noting this, I've committed the full outline of the 1.4 MP specification to rote memory ("RFC memory" 8-) 8-)). I won't make the same mistake in the future. Hopefully, anyone looking at the archives will read more recent information first, and see the corrections, and read the concepts, not the literal words, in my historical postings. Unfortunately, I have a learning disability that makes symbolic substitutions highly probable: it's called "aphasic dyslexia", which means I switch around not only letters in words, but also symbolic representations, as well ...which I learned to my regret, the first time I took math 452 without having real world examples available from which to derive the math as a cross-check. After that, I took my math one quarter behind the physics that required it. I actually spell as well as I do only because I get tactile feedback on typing misspellings, and correct them (it's one of my coping mechanisms) -- mostly... if I'm not typing in a hurry and/or sleep deprived. People might notice that they match the preferred spellings in the OED from my 4th grade Elementary school. You can even figure out which words I learned from reading it ("color" vs. "develope" vs. "behaviour", etc.). Clifford D. Simak (English author) is also responsible for some of my spelling. 8-). You can actually find a number of examples of symbolic language processing mistakes on my part similar to this one -- with the associated corrections, if the mistakes are eggregious enough; English is actually conceptually very forgiving, unless you are using technical jargon with explicit meanings -- in the FreeBSD archives. It usually leads to some really quite off-the-wall misunderstandings when it happens; they are fortuantely rather rare, and people generally cut me the necessary slack to make the corrections, when they happen to the point of noticibility. Heh. More "useless information about Terry than you wanted", I'm sure... Again: mea culpa. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon May 6 14:22: 9 2002 Delivered-To: freebsd-smp@freebsd.org Received: from fw.wemm.org (12-232-135-171.client.attbi.com [12.232.135.171]) by hub.freebsd.org (Postfix) with ESMTP id 995E237B401 for ; Mon, 6 May 2002 14:22:03 -0700 (PDT) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (8.11.6/8.11.6) with ESMTP id g46LM3425306 for ; Mon, 6 May 2002 14:22:03 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (Postfix) with ESMTP id 42EA538CC; Mon, 6 May 2002 14:22:03 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Terry Lambert Cc: Arun Sharma , freebsd-smp@FreeBSD.ORG Subject: Re: hlt when idle? In-Reply-To: <3CD63A3A.DF96520A@mindspring.com> Date: Mon, 06 May 2002 14:22:03 -0700 From: Peter Wemm Message-Id: <20020506212203.42EA538CC@overcee.wemm.org> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Terry Lambert wrote: > Arun Sharma wrote: > > On Wed, May 01, 2002 at 10:15:14AM -0700, Terry Lambert wrote: > > > > Terry, > > > > > In theory, you want to run in "virtual wire mode", which means > > > that the CPUs get the interrupt, and then contend in order to > > > see who services it. > > > > I think you're confused between "virtual wire mode" and the > > "Symmetric I/O mode" for quite some time (going by your previous > > messages on the topic). > > > > Virtual wire mode is for DOS compatibility. Symmetric I/O mode is what > > most MP operating systems use. > > Yes, I already made this (embarrassing!) determination on my own; > see my other posting. > > By way of further elaboration... [what seems like 20 pages of crap] Terry, we have enough email from you already. I realize that you dont seem to have anything else to do but post to the lists, but please try to keep it remotely relevant. "aphasic dyslexia" and your school history are not SMP relevant by any stretch of imagination. A simple "yes, I already realized the error" would have been more than enough. Any more than that and you are wasting our time and contributing to email overload. Cheers, -Peter -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue May 7 6:16:41 2002 Delivered-To: freebsd-smp@freebsd.org Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by hub.freebsd.org (Postfix) with ESMTP id 8633237B409 for ; Tue, 7 May 2002 06:15:43 -0700 (PDT) Received: (qmail 20593 invoked from network); 7 May 2002 13:15:40 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail16.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 7 May 2002 13:15:40 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g47DFQF28663 for ; Tue, 7 May 2002 09:15:27 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 07 May 2002 09:15:18 -0400 (EDT) From: John Baldwin To: smp@FreeBSD.org Subject: Possible status report Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Here's what I've come up with for a status report so far. If you have more to add please let me know: SMPng Status Report John Baldwin jhb@FreeBSD.org smp@FreeBSD.org

The SMPng project has been picking up steam in the last few months thankfully. In February, Seigo Tanimura-san committed the first round of process group and session locking. Alfred Perlstein also added locking to most of the pipe implementation. In March, Alfred fixed several problems with the locking for select() and pushed down Giant some in several system calls. Andrew Reiter added locking for kernel module metadata, and Jeff Roberson wrote a new SMP-friendly slab allocator to replace both the zone allocator and the in-kernel malloc(). Several other subsystems were also locked in April as well. See the SMPng website and todo list for more details.

Some of the current works in progress include locking for the kernel linker by Andrew Reiter and light-weight interrupt threads for the i386 by Bosko Milekic. Seigo Tanimura-san, Alfred Perlstein, and Jeffrey Hsu are also working on locking down various pieces of the networking stack. John Baldwin has written an implementation of turnstiles as well as adaptive mutexes in the jhb_lock Perforce branch. The adaptive mutexes appear to be stable on i386, alpha, and sparc64, but the turnstile code still contains several tricky lock order reversals. John also plans to commit the p_canfoo() API change to use td_ucred in the very near future and then finish the task of making ktrace(4) use a worker thread.

 -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Tue May 7 14: 1:20 2002 Delivered-To: freebsd-smp@freebsd.org Received: from wopr.ife.no (wopr.ife.no [128.39.4.3]) by hub.freebsd.org (Postfix) with ESMTP id 1752037B407 for ; Tue, 7 May 2002 14:01:02 -0700 (PDT) Received: from wopr.ife.no (vortex.sms.ife.no [128.39.4.71]) by wopr.ife.no (8.9.3/8.9.3) with ESMTP id XAA14122 for ; Tue, 7 May 2002 23:00:49 +0200 (CEST) Message-ID: <3CD84080.4090801@wopr.ife.no> Date: Tue, 07 May 2002 23:00:48 +0200 From: "Stein M. Sandbech" User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.3) Gecko/20010914 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-smp@FreeBSD.ORG Subject: Loosing IRQs on a FreeBSD4.4 based server. Content-Type: multipart/mixed; boundary="------------030807060704050209080506" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------030807060704050209080506 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, Sorry about the size of this post. I've seached the FreeBSD archives for info related to our problem, and found nil. I post this to SMP, as it is SMP HW. We run a uniprocessor config, however. The problem: On an Intel SRMK2 1U PentiumIII server (ServerWorks LE chipset), we start loosing IRQs after a while, probably while running X11 and KDE on the system. After a while the machine ginds to a halt. Yes,I know, one does *not* run X and KDE on servers :-). However, as we are still in the test phase, and we are still doing some tinkering with the accounts, quotas, samba etc., we felt it was more convenient that way. Please see below for "/var/log/messages", and find mptable and pciconf output attached. So, my question is, am I correct in assuming that it is KDE and/or X11 that's the culprit? Or can it be faulty HW or OS misconfiguration / error (shudder)? I would be very gratefull if somebody can give me some info on this. Or at least can indicate that this isn't a HW or OS problem. On beforehand, thank you... --Stein Morten /* Stein M Sandbech Email: stein@ife.no ** ** Owner & technical manager ** ** Ing. Stein M. Sandbech Phone: +47 6387 2300 ** ** Phone: +47 6380 6219 ** ** Asaktoppen 39, N-2015 Leirsund, NORWAY Fax: +47 6387 2300 */ ================================================================= Mar 20 17:45:26 dali /kernel: ahc1: Timedout SCB already complete. Interrupts may not be functioning. Mar 20 17:47:26 dali last message repeated 4 times Mar 20 17:48:33 dali /kernel: ahc1: Timedout SCB already complete. Interrupts may not be functioning. Mar 20 17:48:33 dali /kernel: fxp0: device timeout Mar 20 17:50:33 dali /kernel: ahc1: Timedout SCB already complete. Interrupts may not be functioning. Mar 20 17:52:34 dali /kernel: fxp0: device timeout Mar 20 17:54:34 dali /kernel: ahc1: Timedout SCB already complete. Interrupts may not be functioning. Mar 20 17:56:34 dali /kernel: ahc1: Timedout SCB already complete. Interrupts may not be functioning. Mar 20 17:58:34 dali /kernel: fxp0: device timeout : : ---> Within this timeinterval the system is stable. We're NOT running XFree86 and KDE. : May 2 19:01:23 dali login: ROOT LOGIN (root) ON ttyv0 : : ---> Started X and KDE again. : --------------> Is this significant?-| : | : V May 2 19:19:00 dali /kernel: pid 13323 (kdeinit), uid 0: exited on signal 11 (core dumped) May 2 21:40:49 dali /kernel: fxp0: device timeout May 2 21:42:41 dali /kernel: fxp0: device timeout May 2 21:44:41 dali /kernel: fxp0: device timeout May 2 21:44:41 dali /kernel: ahc1: Timedout SCB already complete. Interrupts may not be functioning. May 2 21:54:24 dali /kernel: Copyright (c) 1992-2001 The FreeBSD Project. May 2 21:54:24 dali /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 May 2 21:54:24 dali /kernel: The Regents of the University of California. All rights reserved. May 2 21:54:24 dali /kernel: FreeBSD 4.4-RELEASE #0: Mon Jan 21 22:01:16 CET 2002 May 2 21:54:24 dali /kernel: root@dali.asak.gs.ah.no:/usr/src/sys/compile/DALIQUOTA May 2 21:54:24 dali /kernel: Timecounter "i8254" frequency 1193182 Hz May 2 21:54:24 dali /kernel: Timecounter "TSC" frequency 797970373 Hz May 2 21:54:24 dali /kernel: CPU: Pentium III/Pentium III Xeon/Celeron (797.97-MHz 686-class CPU) May 2 21:54:24 dali /kernel: Origin = "GenuineIntel" Id = 0x686 Stepping = 6 May 2 21:54:24 dali /kernel: Features=0x383fbff May 2 21:54:24 dali /kernel: real memory = 536674304 (524096K bytes) May 2 21:54:24 dali /kernel: avail memory = 519000064 (506836K bytes) May 2 21:54:24 dali /kernel: Preloaded elf kernel "kernel" at 0xc035d000. May 2 21:54:24 dali /kernel: Pentium Pro MTRR support enabled May 2 21:54:24 dali /kernel: md0: Malloc disk May 2 21:54:24 dali /kernel: Using $PIR table, 10 entries at 0xc00f3080 May 2 21:54:24 dali /kernel: npx0: on motherboard May 2 21:54:24 dali /kernel: npx0: INT 16 interface May 2 21:54:24 dali /kernel: pcib0: on motherboard May 2 21:54:24 dali /kernel: pci0: on pcib0 May 2 21:54:24 dali /kernel: pci0: at 4.0 irq 11 May 2 21:54:24 dali /kernel: fxp0: port 0xd400-0xd43f mem 0xfe900000-0xfe9fffff,0xfeafd000-0xfeafdfff irq 10 at device 7.0 on pci0 May 2 21:54:24 dali /kernel: fxp0: Ethernet address 00:03:47:68:a7:59 May 2 21:54:24 dali /kernel: inphy0: on miibus0 May 2 21:54:24 dali /kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto May 2 21:54:24 dali /kernel: fxp1: port 0xd000-0xd03f mem 0xfe700000-0xfe7fffff,0xfeafc000-0xfea fcfff irq 5 at device 8.0 on pci0 May 2 21:54:24 dali /kernel: fxp1: Ethernet address 00:03:47:68:a7:5a May 2 21:54:24 dali /kernel: inphy1: on miibus1 May 2 21:54:24 dali /kernel: inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto May 2 21:54:24 dali /kernel: isab0: at device 15.0 on pci0 May 2 21:54:24 dali /kernel: isa0: on isab0 May 2 21:54:24 dali /kernel: pci0: at 15.1 May 2 21:54:24 dali /kernel: ohci0: mem 0xfeafb000-0xfeafbfff irq 10 at device 15.2 on pci0 May 2 21:54:24 dali /kernel: usb0: OHCI version 1.0, legacy support May 2 21:54:24 dali /kernel: usb0: SMM does not respond, resetting May 2 21:54:24 dali /kernel: usb0: on ohci0 May 2 21:54:24 dali /kernel: usb0: USB revision 1.0 May 2 21:54:24 dali /kernel: uhub0: (unknown) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 May 2 21:54:24 dali /kernel: uhub0: 2 ports with 2 removable, self powered May 2 21:54:24 dali /kernel: pcib1: on motherboard May 2 21:54:24 dali /kernel: pci1: on pcib1 May 2 21:54:24 dali /kernel: ahc0: port 0xe400-0xe4ff mem 0xfebfd000-0xfebfdfff irq 3 at device 4.0 on pci1 May 2 21:54:24 dali /kernel: aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs May 2 21:54:24 dali /kernel: ahc1: port 0xe800-0xe8ff mem 0xfebfe000-0xfebfefff irq 9 at device 4.1 on pci1 May 2 21:54:24 dali /kernel: aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/255 SCBs May 2 21:54:24 dali /kernel: orm0:
Hi just wanna know if newest FreeBSD=20 supports
Dual Athlon XP
Dual P4-Xeon?
Dual P3-Tualatin?
Thanks!
------=_NextPart_000_0035_01C1F84E.575E2610-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri May 10 18:27:50 2002 Delivered-To: freebsd-smp@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 526FF37B404 for ; Fri, 10 May 2002 18:27:47 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 34AE6AE27E; Fri, 10 May 2002 18:27:47 -0700 (PDT) Date: Fri, 10 May 2002 18:27:47 -0700 From: Alfred Perlstein To: David Cc: freebsd-smp@FreeBSD.org Subject: Re: question Message-ID: <20020511012747.GC90188@elvis.mu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org * David [020510 18:08] wrote: > > Hi just wanna know if newest FreeBSD supports > > Dual Athlon XP I have dual AMD MP, it works fine. > Dual P4-Xeon? Yes, even "hyperthreading" is supported. > Dual P3-Tualatin? I have a dual pIII working, but i'm unsure if it's "Tualatin". -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message