From owner-freebsd-current Fri Aug 16 13:15:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA12865 for current-outgoing; Fri, 16 Aug 1996 13:15:27 -0700 (PDT) Received: from gwydion.hns.st-louis.mo.us (dialup-124.icon-stl.net [199.217.153.124]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA12860 for ; Fri, 16 Aug 1996 13:15:23 -0700 (PDT) Received: (from kenth@localhost) by gwydion.hns.st-louis.mo.us (8.7.5/8.7.3) id PAA23042 for dfr@render.com; Fri, 16 Aug 1996 15:11:48 -0500 (CDT) From: Kent Hamilton Message-Id: <199608162011.PAA23042@gwydion.hns.st-louis.mo.us> Subject: Re: locking up To: dfr@render.com (Doug Rabson) Cc: Current@FreeBSD.ORG Date: Fri, 16 Aug 1996 15:11:47 -0500 (CDT) In-Reply-To: from "Doug Rabson" at Aug 12, 96 02:58:43 pm X-Mailer: ELM [version 2.4 PL24 ME8a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Mon, 12 Aug 1996, Doug Rabson wrote: > > > This happens to me whenever I break into DDB. The ipending thing fixes > > it. I guess this motherboard manages to misplace the keyboard interrupt > > while I am in the debugger :-(. > > Potentially useless extra datapoint: This only happens under syscons; pcvt > works fine. I've been off-line for a few days so I missed part of this conversation. I've had keyboard lockup problems with FreeBSD from day one on my home system under syscons. The fix used to be to add 'options "ASYNCH"' but sos removed that when he added the mouse code. Now I just run the gdb kludge out of cron every few minutes. -- Kent Hamilton Play: KentH@HNS.St-Louis.MO.US NIC Handle: KH91 URL: http://www.icon-stl.net/~khamilto/ Blessed Be.... Work: KHamilton@Hunter.COM