From owner-freebsd-current Wed Apr 1 03:03:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03684 for freebsd-current-outgoing; Wed, 1 Apr 1998 03:03:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03679 for ; Wed, 1 Apr 1998 03:03:07 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id FAA09798; Wed, 1 Apr 1998 05:59:50 -0500 (EST) From: Peter Dufault Message-Id: <199804011059.FAA09798@hda.hda.com> Subject: Re: -current X11 slowdown confirmation In-Reply-To: <19980401131532.15104@nagual.pp.ru> from "[______ ______]" at "Apr 1, 98 01:15:32 pm" To: ache@nagual.pp.ru (=?koi8-r?B?4c7E0sXKIP7F0s7P1w==?=) Date: Wed, 1 Apr 1998 05:59:48 -0500 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Maybe it is not syscons, I just guess. Best slowdown indicator is > Netscape, it update icons/screen very slowly now. One strange thing I > found that once update stops completely and continues only when I move > mouse, so it maybe syscons /sys/mouse section in question. I assume the blurber (the meteor shower or whatever) is synchronized to the clock via an event loop so it doesn't run too fast. Maybe it is only (or mostly) being updated via the event motion loop instead of a timing event loop. Has anyone with the problem looked closely at how setitimer / SIGARLM is working? -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message