From owner-freebsd-current  Fri Jul 18 08:43:33 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id IAA28763
          for current-outgoing; Fri, 18 Jul 1997 08:43:33 -0700 (PDT)
Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA28754
          for <freebsd-current@FreeBSD.ORG>; Fri, 18 Jul 1997 08:43:28 -0700 (PDT)
Received: from pauling.salk.edu (pauling [198.202.70.108]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id IAA05640; Fri, 18 Jul 1997 08:43:15 -0700 (PDT)
Date: Fri, 18 Jul 1997 08:43:12 -0700 (PDT)
From: Tom Bartol <bartol@salk.edu>
To: Kyle Mestery <mestery@winternet.com>
cc: Steve Passe <smp@csn.net>, freebsd-current@FreeBSD.ORG
Subject: Re: Xterm question 
In-Reply-To: <Pine.GSO.3.96.970718061625.4734A-100000@tundra.winternet.com>
Message-ID: <Pine.BSF.3.95.970718084114.2459A-100000@pauling.salk.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


I saw similarly weird behaviour under X with w and -current (non-SMP) 
until I upgraded to XFree86-3.3.  All has been well ever since. 

Tom


On Fri, 18 Jul 1997, Kyle Mestery wrote:

> On Thu, 17 Jul 1997, Steve Passe wrote:
> 
> > Are you running the SMP kernel?   If so that *might* be the problem, proper
> > handling of the timer code is still lacking in many areas.
> > Or SMP might have nothing to do with it...
> > 
> Yes, I am running the SMP kernel.  It's strange, but the problem does not
> occurr right away upon starting X.  Things seem to be fine, and then after
> a while the problem starts.
> 
> Kyle Mestery
> StorageTek's Network Systems Group
> 7600 Boone Ave. N., Brooklyn Park, MN 55428
> mesteka@anubis.network.com, mestery@winternet.com
> 
> 
>