From owner-freebsd-current Sat Nov 16 15:14:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA26714 for current-outgoing; Sat, 16 Nov 1996 15:14:41 -0800 (PST) Received: from ravenock.cybercity.dk (disn49.cybercity.dk [194.16.57.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA26706 for ; Sat, 16 Nov 1996 15:14:32 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.2/8.7.3) id AAA01173 for current@freebsd.org; Sun, 17 Nov 1996 00:15:30 +0100 (MET) Message-Id: <199611162315.AAA01173@ravenock.cybercity.dk> Subject: Problem with syscons mouse pointer... To: current@freebsd.org (FreeBSD current) Date: Sun, 17 Nov 1996 00:15:19 +0100 (MET) From: "Soren Schmidt" From: sos@freebsd.org Reply-to: sos@freebsd.org X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Guys... I've just come across a problem with the mousepointer in syscons. If I use it on my p5 machine in will lock the machine tight in a few seconds. This happens both in 2.2-ALPHA and -current, so it has nothing to do with the latest psm&syscons changes (why do I always feel at risk when stating such things :) ) I can also run X which uses the mouse pseudo-device through syscons so it must have something to do with the mousepointer update rutine, but I havn't found out why yet (need some sleep). The strange thing is it doesn't happen on a 486 machine running the exact same code... Anybody else seeing this ?? Or am I halucinating due to lack of sleep lately.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end ..