From owner-freebsd-smp Fri Jul 23 9:24:46 1999 Delivered-To: freebsd-smp@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 666D514BFF for ; Fri, 23 Jul 1999 09:24:40 -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 KAA09806; Fri, 23 Jul 1999 10:24:11 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA07741; Fri, 23 Jul 1999 10:24:10 -0600 Date: Fri, 23 Jul 1999 10:24:10 -0600 Message-Id: <199907231624.KAA07741@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Kazutaka YOKOTA Cc: freebsd-smp@FreeBSD.ORG Subject: Re: SMP + XDM = keyboard lockup In-Reply-To: <199907230402.NAA02136@zodiac.mech.utsunomiya-u.ac.jp> References: <199907221817.LAA09698@usr05.primenet.com> <199907230402.NAA02136@zodiac.mech.utsunomiya-u.ac.jp> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I guess it may not. After init forks and execs getty and xdm, we > don't know the exact order in which these processes will be scheduled > to run on which CPU, do we? /etc/ttys does not ensure the order of > execution. > > If xdm happens to run before other getty processes, it may grab a vty > which will be eventually opened by a getty later. Actually, I had forgotten about this. This is true because the line in /etc/ttys doesn't specify *which* tty for X to use. If we could easily force X to use that specific tty, it would avoid this problem. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message