Date: Fri, 23 Jul 1999 13:02:02 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: freebsd-smp@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: SMP + XDM = keyboard lockup Message-ID: <199907230402.NAA02136@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Thu, 22 Jul 1999 18:17:19 GMT." <199907221817.LAA09698@usr05.primenet.com> References: <199907221817.LAA09698@usr05.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> > The XFree86 server tries to locate an empty vty to use for the X >> > sesssion. If xdm is started in rc.local, the X server will run BEFORE >> > init(8) starts invoking getty(8), and will find /dev/ttyv1 empty and >> > tries to occupy that vty. When rc.init is finished, init(8) will run >> > a copy of getty(8) in /dev/ttyv1, then, *Bomb* The X server and getty >> > both tries to read from the keyboard. > >I don't believe this is the case, because of the SMP factor. If >SMP is disabled, he does not see the problem. > >I believe that if what you are saying is correct, merely following >the xdm documentation and starting the X server in /etc/ttys should >resolve his problem. 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. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907230402.NAA02136>