From owner-freebsd-hackers Mon Dec 6 15:21: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1F24915049; Mon, 6 Dec 1999 15:21:04 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA38894; Mon, 6 Dec 1999 16:21:03 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA37653; Mon, 6 Dec 1999 16:21:03 -0700 (MST) Message-Id: <199912062321.QAA37653@harmony.village.org> To: Mike Smith Subject: Re: tty level buffer overflows Cc: mjacob@feral.com, hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 05 Dec 1999 20:41:31 PST." <199912060441.UAA00805@mass.cdrom.com> References: <199912060441.UAA00805@mass.cdrom.com> Date: Mon, 06 Dec 1999 16:21:03 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912060441.UAA00805@mass.cdrom.com> Mike Smith writes: : Yup. Ignore the "problem in the application" part, as that predicates : that the kernel and driver are working properly, which doesn't seem to be : the case. The problem here is that the buffer between the top side of : the driver and the application isn't being drained fast enough. It would : be educational to know what the app is sleeping on when these messages : are emitted; just dropping to ddb and using 'ps' would probably be : enough. There has to be some reason that the process is either not being : woken when data arrives, or is being held up somewhere else for long : enough that the clist overflows. : : Does the problem still manifest with the recent scheduler changes? : Perhaps the comms processes are being unfairly scheduled against for some : reason? We're seeing it with our ppp link, which uses the kernel level ppp code. Since it doesn't happen for me often, it is hard to diagnose. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message