Date: Fri, 23 Jul 1999 13:45:22 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: "Chris D. Faulhaber" <jedgar@fxp.org> Cc: freebsd-smp@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: SMP + XDM = keyboard lockup Message-ID: <199907230445.NAA03665@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Fri, 23 Jul 1999 00:17:44 -0400." <Pine.BSF.4.10.9907230012350.13821-100000@pawn.primelocation.net> References: <Pine.BSF.4.10.9907230012350.13821-100000@pawn.primelocation.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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.
>>
>
>vty's are assigned in /etc/ttys, though:
>
>ttyv4 "/usr/X11R6/bin/xdm -nodaemon" xterm off secure
>
>^^^^^
>so it the starting order shouldn't matter, unless you have a getty and xdm
>assigned the same vty, and then it _should_ lock up whether using SMP or
>not.
This does not necessarily mean the X server will run in the same
ttyv4 as xdm is. It will still look for an empty vty.
I just experimented with the following /etc/ttys:
ttyv1 "/usr/libexec/getty Pc" cons25 on secure
ttyv2 "/usr/libexec/getty Pc" cons25 on secure
ttyv3 "/usr/libexec/getty Pc" cons25 on secure
ttyv4 "/usr/libexec/getty Pc" cons25 on secure
ttyv5 "/usr/libexec/getty Pc" cons25 on secure
ttyv6 "/usr/libexec/getty Pc" cons25 on secure
ttyv7 "/usr/libexec/getty Pc" cons25 off secure
ttyv8 "/usr/libexec/getty Pc" cons25 off secure
ttyv9 "/usr/X11R6/bin/xdm -nodaemon" xterm on secure
Notice two empty vtys: ttyv7 and ttyv8.
Did `kill -HUP 1' and I got the X server in ttyv7 rather than ttyv9.
Here is lines from /usr/X11R6/lib/X11/xdm/xdm-errors:
XFree86 Version 3.3.3.1 / X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: December 29 1998
If the server is older than 6-12 months, or if your card is newer
than the above date, look for a newer version before reportiing
problems. (see http://www.XFree86.Org/FAQ)
Operating System: FreeBSD 3.0-CURRENT i386 [ELF]
Configured drivers:
SVGA: server for SVGA graphics adaptors (Patchlevel 0):
NV1, STG2000, RIVA128, RIVATNT, ET4000, ET4000W32, ET4000W32i,
[...]
ct64300, mediagx, V1000, V2x00, p9100, spc8110, generic
Using syscons driver with X support (version 2.0)
(using VT number 8)
~~~~~~~~~~~~
XF86Config: /etc/XF86Config
[...]
"VT number 8" means /dev/ttyv7.
This means that if xdm if run before any getty when the system is
staring up, it may grab a vty which will be subsequently used by a
getty process.
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?199907230445.NAA03665>