From owner-freebsd-current Tue Aug 1 5:39: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 4238837BBEB for ; Tue, 1 Aug 2000 05:39:03 -0700 (PDT) (envelope-from pherman@frenchfries.net) Received: from bagabeedaboo.security.at12.de (dial-194-8-205-25.netcologne.de [194.8.205.25]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id OAA05417; Tue, 1 Aug 2000 14:39:01 +0200 (MET DST) Received: from localhost (localhost.security.at12.de [127.0.0.1]) by bagabeedaboo.security.at12.de (8.10.2/8.10.2) with ESMTP id e71Ccs003549; Tue, 1 Aug 2000 14:38:54 +0200 (CEST) Date: Tue, 1 Aug 2000 14:38:53 +0200 (CEST) From: Paul Herman To: Donn Miller Cc: freebsd-current@FreeBSD.ORG Subject: Re: Moused and Yarrow (Re: Moused behaving funny in 4.1-STABLE) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Aug 2000, Donn Miller wrote: > On Tue, 1 Aug 2000, Paul Herman wrote: > > > When both the prompt and the mouse are at the bottom of the screen, > > then moused starts eating up interrupt CPU. > > It has something to do with this whole Yarrow thing. I suppose Yarrow > (and dev/urandom) are eating up tty interrupts that otherwise would have > gone to moused and syscons. Yeah, I caught that thread, but the problems I'm seeing are in 4.1-STABLE and AFAIK Yarrow hasn't made it to my tree yet (yes, I deserve it, that's what I get for posting to -current). I just thought I'd give -current a holler, because people were noticing a similar thing on this list... I guess I'll try -stable if nobody has any ideas here. -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message