From owner-freebsd-net@FreeBSD.ORG Sun Feb 2 09:06:02 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A918551 for ; Sun, 2 Feb 2014 09:06:02 +0000 (UTC) Received: from mail-ee0-x234.google.com (mail-ee0-x234.google.com [IPv6:2a00:1450:4013:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C53771A30 for ; Sun, 2 Feb 2014 09:06:01 +0000 (UTC) Received: by mail-ee0-f52.google.com with SMTP id e53so3018752eek.25 for ; Sun, 02 Feb 2014 01:06:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=PiuNq322K/VwoY94hJFAgbp+CxVnfusTl5/38kkZYTA=; b=eZEAhdZmGSGLkHPKz4NfbMorNOK21RxSW6kCOjTvlECkcOSnlpWF3LlWaInAxPQktZ Cpx5ZIKIy25U3+7MnDFpvhPeLjZu8F5MPOLgVrIwPIF+A1AdYW7hL1pNlWsG2ew7UWM6 MxUzcp+aY+dZonVT9O5KcPepoq14SYlhERyQlbTH1Uc7j9hQmHY5EmSnI0YlxYvbust1 xX8cd+h8r/BfVR6aO0UtEnSf0Sd8cxLtKGsOrO/ZurBU4lQX4QxoCQbsYgWvaRV/NRTt Dx5DDtZ0z96jwsIN+RR3KBtAkZGGLKrsKp7yQVTZnEcXX8jjEDcwfHj1mH8nrPEgoRc6 5xcQ== MIME-Version: 1.0 X-Received: by 10.15.61.7 with SMTP id h7mr1226759eex.49.1391331960037; Sun, 02 Feb 2014 01:06:00 -0800 (PST) Received: by 10.14.65.4 with HTTP; Sun, 2 Feb 2014 01:05:59 -0800 (PST) In-Reply-To: References: Date: Sun, 2 Feb 2014 01:05:59 -0800 Message-ID: Subject: Re: Errors using span interface on if_bridge(4) From: hiren panchasara To: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Feb 2014 09:06:02 -0000 On Sat, Feb 1, 2014 at 6:29 PM, hiren panchasara wrote: > On Sat, Feb 1, 2014 at 5:16 PM, hiren panchasara > wrote: > Trying to find how to narrow down what is causing this checksum errors. >From ixgbe.c: ixgbe_rx_checksum() 4643 if (status & IXGBE_RXD_STAT_IPCS) { 4644 if (!(errors & IXGBE_RXD_ERR_IPE)) { xxx 4645 /* IP Checksum Good */ 4646 mp->m_pkthdr.csum_flags = CSUM_IP_CHECKED; 4647 mp->m_pkthdr.csum_flags |= CSUM_IP_VALID; 4648 4649 } else { yyy 4650 mp->m_pkthdr.csum_flags = 0; 4651 } 4652 4653 } If I put a device_printf() at xxx, everything slows down and I see very less packets making through with near-zero checksum errors. A device_printf() at yyy (and nothing at xxx) never gets called. I was expecting it to be called as I thought checksum errors would cause that code-path to be traversed. cheers, Hiren