From xemacs-m  Sun Apr 13 14:22:48 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id OAA04982
	for <xemacs-beta@xemacs.org>; Sun, 13 Apr 1997 14:22:44 -0500 (CDT)
Received: by crystal.WonderWorks.COM 
	id QQcldd12856; Sun, 13 Apr 1997 15:22:38 -0400 (EDT)
Date: Sun, 13 Apr 1997 15:22:38 -0400 (EDT)
Message-Id: <QQcldd12856.199704131922@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: Bug with itimers/display-time?
In-Reply-To: <m3encelu3b.fsf@jens.metrix.de>
References: <m3encelu3b.fsf@jens.metrix.de>
X-Mailer: VM 6.25 under 19.15 XEmacs Lucid
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Jens Lautenbacher writes:
 > As some of you already have noticed, the display-time timer sometimes
 > seems to "hang". I don't have a solution or explanation for this, but
 > I just saw some strange behaviour related to this.
 > [...]

All of it is consistent with the theory that the timer driver
stops running.

Naturally, I never see the problem.

