From owner-freebsd-smp Thu Jul 22 14: 1:22 1999 Delivered-To: freebsd-smp@freebsd.org Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id DB032155AF for ; Thu, 22 Jul 1999 14:01:11 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.8.8/8.8.8) with ESMTP id RAA24728; Thu, 22 Jul 1999 17:00:55 -0400 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: <199907221839.LAA10550@usr05.primenet.com> Date: Thu, 22 Jul 1999 17:00:55 -0400 To: Richard Scheper , freebsd-smp@FreeBSD.ORG From: Garance A Drosihn Subject: Re: SMP + XDM = keyboard lockup Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 3:16 PM -0400 7/22/99, Richard Scheper wrote: > 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 Early in the login process, start some dumb script which just loops around dumping the output of 'ps' into some file (with a 'sleep' in the loop, of course!). If you're a bit more daring, you could also have this other script kill off your xdm task after a few minutes, which should give you control back. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message