From owner-freebsd-bugs Sat May 20 2:20: 8 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0224A37B646 for ; Sat, 20 May 2000 02:20:06 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id CAA50029; Sat, 20 May 2000 02:20:05 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Sat, 20 May 2000 02:20:05 -0700 (PDT) Message-Id: <200005200920.CAA50029@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Tim Vanderhoek Subject: Re: i386/9341: tty-level buffer overflows Reply-To: Tim Vanderhoek Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR i386/9341; it has been noted by GNATS. From: Tim Vanderhoek To: freebsd-gnats-submit@FreeBSD.org, kowkn@asia1.com.sg Cc: vanderh@ecf.toronto.edu Subject: Re: i386/9341: tty-level buffer overflows Date: Sat, 20 May 2000 04:24:29 -0400 (EDT) >Jan 5 16:22:16 lewis /kernel: sio0: 966 more tty-level buffer overflows (total 5286) >Jan 5 16:22:17 lewis /kernel: sio0: 616 more tty-level buffer overflows (total 5902) > >What system parameters should we tune to increate the tty-level >buffer? I once adjusted sys/isa/sio.c, the siosetwater() function to try and make this go away. I adjusted ibufsize to something ridiculously high. Try say 4096 or so. I can't remember if that made the problem go away. I found in practice that I lost little bandwidth to the overflows so I decided not to fight cvsup over my changes. If it did work, my knowledge of sio.c is low enough that it was probably coincidence. :) I just went browsing through the mail archives to see what they say. In turns-out that there are many references to this in the archives. You should have searched them before filing a PR. However, it seems that some of the suggestions in the mail archives are less than useful. Again, see caveat about my little knowledge or interest in sio.c, but I don't believe that increasing your port speed will solve this problem. Neither do I believe that one of the rather elaborate (and, to me, sub-comprehensible) suggestions will work, either. Credible mail archive Bruce Evans: 199705080354.NAA02619@godzilla.zeta.org.au Doug White: Pine.BSF.4.03.9810220936040.12898-100000@resnet.uoregon.edu Try also the command `man 4 sio`. Note the explanation of error messages at the end of the manpage. In the event that you choose to ignore the error messages, you are mortally harming yourself. Nor are they due to an unknown bug in FreeBSD. Good luck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message