From owner-freebsd-bugs Sun May 3 09:33:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17962 for freebsd-bugs-outgoing; Sun, 3 May 1998 09:33:54 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [207.33.240.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17956 for ; Sun, 3 May 1998 09:33:49 -0700 (PDT) (envelope-from dillon@backplane.com) Received: (dillon@localhost) by apollo.backplane.com (8.8.8/8.6.5) id JAA04427; Sun, 3 May 1998 09:33:47 -0700 (PDT) Date: Sun, 3 May 1998 09:33:47 -0700 (PDT) From: Matthew Dillon Message-Id: <199805031633.JAA04427@apollo.backplane.com> To: Nate Williams Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: i386/5398 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :In short, it's only partially FreeBSD's problem. It's FreeBSD problems :because ultimately it makes FreeBSD look bad, but in reality this :problem is one in XFree86. Note, I've heard that newer versions of :XFree86 do things better/differently? Are you using the most recent :version of XFree86? Are you using a video card that tends to hog the :PCI bus because it's cranked way up? : :These are the *most* likely scenaries that will cause overflows on your :hardware based on my own personal experience. : :This is not an affront to your intelligence or your time, just :observations based on direct experience with FreeBSD and X with similar :behavior. : : :Nate How is XFree86, a userland program, able to disable interrupts ? The Hardware blitter/PCI latency also seems impossible, 115200 = 11.5 KBytes/sec = 86uS per character x the FIFO depth (after the hack) of 4 or 8 character times is over 500uS. It just doesn't make any sense. -Matt Matthew Dillon Engineering, BEST Internet Communications, Inc. [always include a portion of the original email in any response!] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message