From owner-freebsd-smp Sun Jun 3 4: 7:35 2001 Delivered-To: freebsd-smp@freebsd.org Received: from ns2.staruni.com (ns2.staruni.com [209.85.86.196]) by hub.freebsd.org (Postfix) with ESMTP id 0D68C37B401 for ; Sun, 3 Jun 2001 04:07:26 -0700 (PDT) (envelope-from bbedros@cyberhotline.com) Received: from bbedros (209.85.86.82 [209.85.86.82]) by ns2.staruni.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id LSG1LS1N; Sat, 2 Jun 2001 22:12:18 -0700 Message-ID: <000801c0ebec$a86e8b40$525655d1@bbedros> From: "Bedros Bedros" To: Subject: Our color is a mess Date: Sat, 2 Jun 2001 22:18:41 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C0EBB1.FAE19380" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 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. ------=_NextPart_000_0005_01C0EBB1.FAE19380 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hi, We have STB Symmetric GLyder CD version 2.95 (P/N 270-0022-003). It is = Windows 95 compatible. We have Windows 98, now and this is the second = time we reloaded our Windows and our color got messed up. =20 How do we fix it? =20 Thanks. ------=_NextPart_000_0005_01C0EBB1.FAE19380 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

Hi,

We have STB Symmetric GLyder CD version 2.95 (P/N=20 270-0022-003). It is Windows 95 compatible. We have Windows = 98, now=20 and this is the second time we reloaded our Windows and our color = got=20 messed up.

How do we fix it?

Thanks.

------=_NextPart_000_0005_01C0EBB1.FAE19380-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Sun Jun 3 4:20:20 2001 Delivered-To: freebsd-smp@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-243.dsl.lsan03.pacbell.net [64.165.226.243]) by hub.freebsd.org (Postfix) with ESMTP id 6C8A237B403 for ; Sun, 3 Jun 2001 04:20:12 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E0302673A5; Sun, 3 Jun 2001 04:20:11 -0700 (PDT) Date: Sun, 3 Jun 2001 04:20:11 -0700 From: Kris Kennaway To: Bedros Bedros Cc: freebsd-smp@freebsd.org Subject: Re: Our color is a mess Message-ID: <20010603042011.A4589@xor.obsecurity.org> References: <000801c0ebec$a86e8b40$525655d1@bbedros> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <000801c0ebec$a86e8b40$525655d1@bbedros>; from bbedros@cyberhotline.com on Sat, Jun 02, 2001 at 10:18:41PM -0700 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 --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 02, 2001 at 10:18:41PM -0700, Bedros Bedros wrote: > Hi, >=20 > We have STB Symmetric GLyder CD version 2.95 (P/N 270-0022-003). It is W= indows 95 compatible. We have Windows 98, now and this is the second time = we reloaded our Windows and our color got messed up. =20 >=20 > How do we fix it? =20 Edit your /usr/X11R6/lib/X11/app-defaults/XSymmetricGlyder file and change the default colour values. If you don't have that directory, install XFree86. If you don't have XFree86, install FreeBSD to get it. Kris --n8g4imXOkfNTN/H1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7Gh1rWry0BWjoQKURApHNAJ9GoNriEVLLciGjpgZlAtDQxqT7hACglctT voosWF2umMLHioQtYQQzlHk= =4MVp -----END PGP SIGNATURE----- --n8g4imXOkfNTN/H1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Mon Jun 4 11:29:50 2001 Delivered-To: freebsd-smp@freebsd.org Received: from smtpg.casema.net (smtpg.casema.net [195.96.96.160]) by hub.freebsd.org (Postfix) with SMTP id 8744E37B405 for ; Mon, 4 Jun 2001 11:29:46 -0700 (PDT) (envelope-from walter@binity.com) Received: (qmail 25965 invoked by uid 0); 4 Jun 2001 18:29:44 -0000 Received: from unknown (HELO slash.b118.binity.net) (212.64.76.217) by smtpg.casema.net with SMTP; 4 Jun 2001 18:29:44 -0000 Received: from silver.b118.binity.net (silver.b118.binity.net [172.18.3.10]) by slash.b118.binity.net (Postfix) with ESMTP id A08A2123; Mon, 4 Jun 2001 20:28:12 +0200 (CEST) Date: Mon, 4 Jun 2001 20:31:51 +0200 From: Walter Hop X-Mailer: The Bat! (v1.52f) Educational Organization: Binity X-Priority: 3 (Normal) Message-ID: <29338755324.20010604203151@binity.com> To: freebsd-smp@freebsd.org Cc: Ali Niknam Subject: Unexpected lockups on SMP boxes MIME-Version: 1.0 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 Hi all, my SMP boxes (FreeBSD 4.2-RELEASE) seem to freeze in a while. There are no panics and no apparent symptoms other than lockups after which they have to be forcefully rebooted. I have never experienced this on any uniprocessor machine with similar configuration and tasks (Apache, BIND, ProFTPd, MySQL). Configurations: 1. ServerWorks chipset, dual 866MHz, 1GB ECC ram, fxp NIC 2. VIA chipset, dual 866MHz, 1GB ram, xl NIC (locks up) or fxp NIC (also) SMP was just enabled by uncommenting the SMP lines in the default kernel config file. Does anyone have any ideas, or maybe a hint on what I should check? Or is this something that can be expected from 4.x SMP support? Thanks! walter -- Walter Hop | +31 6 24290808 | Finger for public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 7 20:16:19 2001 Delivered-To: freebsd-smp@freebsd.org Received: from soda.csua.berkeley.edu (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (Postfix) with ESMTP id 02C4F37B405 for ; Thu, 7 Jun 2001 20:16:18 -0700 (PDT) (envelope-from jwm@CSUA.Berkeley.EDU) Received: from soda.csua.berkeley.edu (IDENT:jixQysXb0Kjo1yXWHvyfZB0GHGaeoJEg@localhost [127.0.0.1]) by soda.csua.berkeley.edu (8.11.1/8.11.1) with ESMTP id f583GHP35188 for ; Thu, 7 Jun 2001 20:16:17 -0700 (PDT) (envelope-from jwm@soda.csua.berkeley.edu) Message-Id: <200106080316.f583GHP35188@soda.csua.berkeley.edu> To: freebsd-smp@freebsd.org Subject: Information on context stealing Reply-To: jwm@CSUA.Berkeley.EDU Date: Thu, 07 Jun 2001 20:16:17 -0700 From: John Milford Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have some free time coming up soon, and I am interested in working on context stealing for FreeBSD. However in begining to look into it, I have run up against some questions I have not been able to answer from the web page or email archives. 1) It the purpose solely to reduce process overhead, are these threads also to be created on demand, or are there other objectives as well such as reduced memory overhead? 2) Since KVM is mapped into every process, would it meet the goals to preform a full context switch to one of these lightweight threads, except that cr3 is not touched? It would be really helpful if someone could point me in the direction of a document that could clarify these for me. Also if someone has already thought through some or all of this and has soe notes that would be helpful as well. I am assuming that no one has started becasue the project has a not started status on the web page. Thank you for any help/clarification you can offer. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Thu Jun 7 21:28:49 2001 Delivered-To: freebsd-smp@freebsd.org Received: from cr66388-a.rchrd1.on.wave.home.com (cr1047640-a.rchrd1.on.wave.home.com [24.157.126.22]) by hub.freebsd.org (Postfix) with ESMTP id 3109437B403 for ; Thu, 7 Jun 2001 21:28:45 -0700 (PDT) (envelope-from jburkholder0829@home.com) Received: from k7.rchrd1.on.wave.home.com (k7.rchrd1.on.wave.home.com [10.0.0.249]) by cr66388-a.rchrd1.on.wave.home.com (Postfix) with ESMTP id 9DB0B1F3; Fri, 8 Jun 2001 00:34:10 -0400 (EDT) Received: from k7.rchrd1.on.wave.home.com (localhost [127.0.0.1]) by k7.rchrd1.on.wave.home.com (Postfix) with ESMTP id 105CC22A5; Fri, 8 Jun 2001 00:33:37 -0400 (EDT) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: jwm@CSUA.Berkeley.EDU Cc: freebsd-smp@FreeBSD.ORG Subject: Re: Information on context stealing In-Reply-To: Message from John Milford of "Thu, 07 Jun 2001 20:16:17 PDT." <200106080316.f583GHP35188@soda.csua.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 08 Jun 2001 00:33:36 -0400 From: Jake Burkholder Message-Id: <20010608043337.105CC22A5@k7.rchrd1.on.wave.home.com> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > I have some free time coming up soon, and I am interested in > working on context stealing for FreeBSD. However in begining to look > into it, I have run up against some questions I have not been able to > answer from the web page or email archives. > > 1) It the purpose solely to reduce process overhead, are these > threads also to be created on demand, or are there other > objectives as well such as reduced memory overhead? The purpose is solely to reduce the overhead required to context switch from a process to an interrupt thread. > 2) Since KVM is mapped into every process, would it meet the > goals to preform a full context switch to one of these > lightweight threads, except that cr3 is not touched? More or less. This is one of the goals, another would be to not save the floating point state if the current process is using it, to generally stream line the whole code path. Its also conceivable to not switch the stack pointer, but I don't know why anyone in their right mind would do this. > > It would be really helpful if someone could point me in the direction > of a document that could clarify these for me. Also if someone has > already thought through some or all of this and has soe notes that > would be helpful as well. I am assuming that no one has started > becasue the project has a not started status on the web page. Thank > you for any help/clarification you can offer. The documentation that I know about is the BSD/OS source code which implements this to some extent, as well as a general SMPng goals and definitions document. Unfortunately this stuff is the property of BSDi and/or wind river, so its currently only available to committers and employees. I've studied the code in question extensively and I started implementing it for FreeBSD, but I never finished. I decided that there was more to be gained with less effort by working on adding data locking to the kernel to push down the giant mutex and working on other areas of the scheduler. Also, I feel that any implementation that is truly light weight will be very complex and have subtle implications, to the point that few people other than the implementer will understand it or be able to maintain it. I believe that the BSD/OS code suffers from this. In any case, what I've done is on my web page: http://people.freebsd.org/~jake/ithd.diff its rather old and stale. I wrote a kld that tested the blocking and non-blocking cases but I can't seem to find it. I never ran this code with real interrupts. I don't mean to scare you away, but a lot of people seem to want this and I don't think they have fully considered the ramifications beyond the buzzwords. Let me know if you have any questions. Jake > > 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