From owner-freebsd-smp Thu Jul 22 12:17:39 1999 Delivered-To: freebsd-smp@freebsd.org Received: from beast.toad.net (beast.toad.net [205.197.182.100]) by hub.freebsd.org (Postfix) with ESMTP id A512D14D82 for ; Thu, 22 Jul 1999 12:17:31 -0700 (PDT) (envelope-from scheper@beast.toad.net) Received: from localhost (scheper@localhost) by beast.toad.net (8.9.3/8.9.3) with ESMTP id PAA14623 for ; Thu, 22 Jul 1999 15:16:20 -0400 Date: Thu, 22 Jul 1999 15:16:20 -0400 (EDT) From: Richard Scheper To: freebsd-smp@FreeBSD.ORG Subject: Re: SMP + XDM = keyboard lockup In-Reply-To: <199907221839.LAA10550@usr05.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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 -Rich On Thu, 22 Jul 1999, Terry Lambert wrote: > > Since he appears to have a way in, other than the console, he > should: > > 1) Cause the lockup > > 2) Go in and do a 'ps' to see if conflicting processes are > running > > 3) Force a console switch via escape sequence to a console > vty not currently in use. This should result in the X > server disengaging, and the input devices being detached > and reattached to the new vty, if the problem is merely > a race. > > Also, if both terminals are reading input, as has been posited, > a ctrl-alt-F2 should still result in a console switch, regardless > of who takes the keypress event (ctrl and alt are modifiers, so > only the F2 keycode should be relevent). > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message