From owner-freebsd-current@FreeBSD.ORG Thu Jun 30 17:01:34 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 9082F16A41C for ; Thu, 30 Jun 2005 17:01:34 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from pne-smtpout1-sn1.fre.skanova.net (pne-smtpout1-sn1.fre.skanova.net [81.228.11.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DE0C43D48 for ; Thu, 30 Jun 2005 17:01:34 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from royal64.emp.zapto.org (195.198.193.104) by pne-smtpout1-sn1.fre.skanova.net (7.2.060.1) id 42B813B0001CD802 for freebsd-current@freebsd.org; Thu, 30 Jun 2005 19:01:33 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 30 Jun 2005 19:00:38 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Message-ID: <4F9C9299A10AE74E89EA580D14AA10A6028584@royal64.emp.zapto.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: tcp_sack_output: Computed sack hole not the same as cached value Thread-Index: AcV9lT24oke33pkFR2S1YAlvMeN+Eg== From: "Daniel Eriksson" To: Subject: tcp_sack_output: Computed sack hole not the same as cached value X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Thu, 30 Jun 2005 17:01:34 -0000 With latest CURRENT (2005.06.30.12.00.00) I get a ton of these messages on the console. 50-100 per minute and that's when load is light. With the old kernel (2005.06.23.00.30.00) no such messages show up. tcp_sack_output: Computed sack hole not the same as cached value This is on an SMP machine. On my UP server I saw no messages, but I only had the two machines (one UP and one SMP) running the new kernel for a few minutes. /Daniel Eriksson