From owner-freebsd-current@FreeBSD.ORG Wed Jan 21 03:40:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D24C16A4CE for ; Wed, 21 Jan 2004 03:40:37 -0800 (PST) Received: from sarevok.idg.nl (ardvark.idg.nl [62.250.13.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6507B43D45 for ; Wed, 21 Jan 2004 03:40:34 -0800 (PST) (envelope-from mdev@sarevok.idg.nl) Received: by sarevok.idg.nl (Postfix, from userid 100) id 06889B828; Wed, 21 Jan 2004 12:40:33 +0100 (CET) From: Melvyn Sopacua Organization: WebTeckies.org To: current@FreeBSD.org Date: Wed, 21 Jan 2004 12:40:32 +0100 User-Agent: KMail/1.5.94 References: <200401202147.i0KLlXAw014093@mta7.pltn13.pbi.net> In-Reply-To: <200401202147.i0KLlXAw014093@mta7.pltn13.pbi.net> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_wUmDAxeCD6QQhA0"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200401211240.32843.freebsd-current@webteckies.org> Subject: Re: PANIC: sent too much X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jan 2004 11:40:37 -0000 --Boundary-02=_wUmDAxeCD6QQhA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 20 January 2004 22:48, Jeffrey Hsu wrote: > > sometimes i got this panic > > with high load on network interfaces > > I fixed this in DragonFlyBSD months ago. This is because you > have the experimental Limited Transmit option turned on by default, > something I do not recommend for FreeBSD because there is a subtle bug > with that code when the connection is not congestion window limited. This "Limited Transmit" option, is that configurable somewhere and does tha= t=20 work-around the bug (a quick grep tcp on sysctl -a doesn't yield something= =20 recognizable)? Seen this this morning while doing a `cvs -d/home/ncvs update src', logged = in=20 via ssh in a GENERIC kernel of 2004-01-10. This was via a chello Netherland= s=20 cable connection - an ISP famous for it's high bandwidth and equally high=20 packet loss, so it fits the profile. I'll try Andre's patch regardless, but if it doesn't work, it would be nice= if=20 there's an alternative (maybe mention that in UPDATING as well). =2D-=20 Melvyn =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D =46reeBSD sarevok.idg.nl 5.2-CURRENT FreeBSD 5.2-CURRENT #3: Tue Dec 30 14:= 31:47=20 CET 2003 root@sarevok.idg.nl:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG= =20 i386 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D --Boundary-02=_wUmDAxeCD6QQhA0 Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBADmUwOv9JNmfFN5URAreOAKC1fydKZt+BhvqGoJ6/YSR1D4Pm0QCcCwze biiDGlNCICEBWDXX7pWsCIs= =2O/O -----END PGP SIGNATURE----- --Boundary-02=_wUmDAxeCD6QQhA0--