Date: Fri, 23 Jul 1999 09:43:07 +0200 From: Marc van Kempen <marc@bowtie.nl> To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> Cc: Richard Scheper <scheper@beast.toad.net>, freebsd-smp@FreeBSD.ORG Subject: Re: SMP + XDM = keyboard lockup Message-ID: <199907230743.JAA11980@bowtie.nl> In-Reply-To: yokota's message of Fri, 23 Jul 1999 12:11:15 %2B0900. <199907230311.MAA00450@zodiac.mech.utsunomiya-u.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
> > >Actually, I don't have another way in, just the console. If I cause the > >lockup I have no recourse but to turn the computer off. It makes it tough > >to get info, I know. I never see any error messages in /var/log/messages > > Ok. Even if you don't have network connection to your system, it is > possible to find clues as to what is happening. > > After you experience keyboard lockup, reboot your system, give the > `-s' option at the boot loader prompt. You will then be in the single > user mode. > > Examine the file /usr/X11R6/lib/X11/xdm/xdm-errors which records > output from the X server and clients in the previous xdm invocation. > Locate the lines: > > Using syscons driver with X support (version 2.0) > (using VT number 4) > ~~~~~~~~~~~ > > As you are trying to run xdm in /dev/ttyv3 by /etc/ttys, you should > see "VT number 4" (notice the offset by 1; this is because the X > server gives the first vty (/dev/ttyv0) the number 1), when the X server > is running without the keyboard lockup. > > If the nubmer is 1 though 3, both the X server and getty are > fighting for keyboard input in the same vty. > > When you run xdm from rc.local (or /usr/local/etc/rc/something) in one > way or another, and have the keyboard lockup, you can veryfy xdm-getty > conflicts in the same way by looking at this log file. > > As I stated before, I believe this is a timing problem. It may not > always be reproducable by every SMP system; my SMP box has no trouble > when I start xdm from /etc/ttys. > I have had this happen to me on several systems (UNI processor), and the problem would not occur all the time which suggested to me too that it was some kind of timing problem between init and X trying to grab the keyboard. I could always solve it by starting xdm from a script which would sleep for several seconds (5-10) (giving init time to complete) and then start xdm. So it seems it isn't even SMP related. Regards, Marc. ---------------------------------------------------- Marc van Kempen BowTie Technology Email: marc@bowtie.nl WWW & Databases tel. +31 40 2 43 20 65 fax. +31 40 2 44 21 86 http://www.bowtie.nl ---------------------------------------------------- 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?199907230743.JAA11980>