From owner-freebsd-hackers Sat Dec 4 9:58:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 0168314C28 for ; Sat, 4 Dec 1999 09:58:51 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id JAA10272; Sat, 4 Dec 1999 09:59:35 -0800 Date: Sat, 4 Dec 1999 09:59:35 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Warner Losh Cc: hackers@FreeBSD.ORG Subject: Re: tty level buffer overflows In-Reply-To: <199912041752.KAA21366@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message Matthew Jacob writes: > : Normally I might agree with this, but I use a tty line on a 150Mhz i386 to > : be a serial console for another freebsd box. This is a NS16550A with a 16 > : byte fifo. This systems is effectively idle except for this task. So, I'm > : running tip and I get constant tty-level buffer overflows at 9600 baud. > > In the past, something like TTYHOG has been used to arbitrate this, > but I can't seem to find the right magic bits here. Pointers? Err, umm, *cough*... it's been over ten years since I did any tty line discipline work, so I don't remember... :-(. > I am seeing this at 115200 on my 486DX2-66 for my ISDN line. NS16550A > uarts. Everything else seems cool. I am suspecting a subtle bug > because it only happens now and again, not all the time, or only when > large xfers are happening. I'd like to know more about this resource > shortage so I might do something about it. That's one I'd like to know as well. Sigh- I think somebody (I'm booked) will have to go looksee. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message