From owner-freebsd-current Wed Dec 25 17:28:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA00395 for current-outgoing; Wed, 25 Dec 1996 17:28:05 -0800 (PST) Received: from fools.ecpnet.com (moke@fools.ecpnet.com [204.246.64.101]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA00371 for ; Wed, 25 Dec 1996 17:27:59 -0800 (PST) Received: from localhost (moke@localhost) by fools.ecpnet.com (8.8.4/8.8.4) with SMTP id TAA00418; Wed, 25 Dec 1996 19:24:24 -0600 (CST) Date: Wed, 25 Dec 1996 19:24:24 -0600 (CST) From: Jimbo Bahooli To: Kazutaka YOKOTA cc: Nate Williams , freebsd-current@freebsd.org Subject: Re: options ASYNCH In-Reply-To: <199612251201.VAA07663@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 25 Dec 1996, Kazutaka YOKOTA wrote: > > >On Tue, 24 Dec 1996, Nate Williams wrote: > > > >> > The ASYNCH define to fix the keyboard lockups when switching vty's appears > >> > to be gone in 2.2 and 3.0. So now when I switch vty's my keyboard locks > >> > and I need to reset it by unplugging it, then plugging it back in. Is > >> > there another work around? > >> > >> Try using 2.2-Beta and see if it helps. > >> > >> > >> Nate > >> > > > >I'm tracking the RELENG_2_2 branch, and I made world the day 2.2-BETA came > >out so I'm running its equal. Possibly even with a few more fixes, so that > >didn't help. :) > > I think we need more details to diagnose your problem. > > Does lockup happen when switching between the X server and vty's? > > Do you have a PS/2 mouse and `psm' enabled? If so, does the X server > access the mouse via `moused'? > > Is there any error message on the console or in `/var/log/messages'? > > Kazu > 1. It locks up when switching vty's. The X server is not involved in this equation. 2. Its a microsoft 2-button serial mouse, psm is not even compiled in the kernel. 3. And there are no messages in /var/log/messages, or any other logfiles. Hope that helps...