From owner-freebsd-net@freebsd.org Thu May 10 14:56:41 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 76110FCC3CD for ; Thu, 10 May 2018 14:56:41 +0000 (UTC) (envelope-from driesm.michiels@gmail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E803469202; Thu, 10 May 2018 14:56:40 +0000 (UTC) (envelope-from driesm.michiels@gmail.com) Received: by mail-wm0-x22a.google.com with SMTP id t11-v6so4415284wmt.0; Thu, 10 May 2018 07:56:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-transfer-encoding:thread-index:content-language; bh=OWrp9By8YqGtrI2QyA1u7mlXKb+ETaHOdObRZp3bXCI=; b=XIvGZbfaJvizDnTdzfnrLpvJqjnThg/DtnxKQ7jIo3NwlBi3DuECbrXIQEr4L5GiVF xn9KHatz5fxtOCC2Mi1MIhQU55z7YDdkSF5D1IYD5PqQUfjNR9MzGffle4EphhpszZH4 Mo1Alw60Ai1PYVA29Xr7iZ12+cCoxgMlqJKTwJlKXR9rcVSgRs888/RF1zEMuTbEGAoB 1lQUENwovjV88u9QehFmzhSTLzFs43Lf4psPp7C4UkoDY1qZHawHmkjatTBkswSDX1BN 4IrFAtmSp7SQO+k20OqEsoG6VBQ/1IOik2oU1+7EVAJyokrbIdr8N6UcMBMhpr8I3Fhq N3Lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=OWrp9By8YqGtrI2QyA1u7mlXKb+ETaHOdObRZp3bXCI=; b=rIkk1x0O6uHaxbwLmZEd3dxeS8cRUkOpOv89AJiYdXLxRffdzTJno9TldtvZzKF/7T d9/Eg1PBFaM8qByVSGPTvgoIX/kLA+m0q9AsPnf77LfmA7lBv6VQjwomv4NYXdyAVu/e hA8pJLzJfnU5/iiQgcjrP79bkOmo/m3qxuVXBPwqaqaZB2rV0EgUaTVOQUDhlVUw/SfQ oxEJ3wAmnjBsxOcMTL6/fpHsRTz4BHhj6uL3YLPwG+7d6WWYBxmSvWTz+BwcbTkaFwvb eV3HDQWLpsBSIcZOaA7rpWXq2jZAYFP0TNQlIyG/Ob8rhBkgHyiSejEe2EHZoNeg+Yk9 fxbg== X-Gm-Message-State: ALKqPweeTABHuO99YG8G6IsNM50XCRtebaByfslUa/N7Yr/jy9Iot5g0 dPPr37HwQ7whev2vaPJcu0obsf4v X-Google-Smtp-Source: AB8JxZqkjs29qYebjHuAKg1TB9X5kltBDW08sG7tbmeNgKgd3xfjB1IG5DXp+Vt6CBM26hcQ/I+HAA== X-Received: by 2002:a50:ed92:: with SMTP id h18-v6mr2790105edr.102.1525964199556; Thu, 10 May 2018 07:56:39 -0700 (PDT) Received: from DriesPC (ptr-8sl34rf6ki9c3i8vpvf.18120a2.ip6.access.telenet.be. [2a02:1811:2515:e000:2d76:eb53:3cfc:54bb]) by smtp.gmail.com with ESMTPSA id z11-v6sm662651edh.60.2018.05.10.07.56.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 May 2018 07:56:38 -0700 (PDT) From: "Dries Michiels" To: "'Tom Jones'" , References: <5ae60f44.1c69fb81.ee4a5.1043@mx.google.com> <20180429190450.GA97911@tom-desk.erg.abdn.ac.uk> <5ae6cbc7.1c69fb81.ed649.655e@mx.google.com> <20180510134746.GD37534@tom-desk.erg.abdn.ac.uk> In-Reply-To: <20180510134746.GD37534@tom-desk.erg.abdn.ac.uk> Subject: RE: kernel: in6_delayed_cksum: delayed m_pullup Date: Thu, 10 May 2018 16:56:38 +0200 Message-ID: <007101d3e86f$196e4fb0$4c4aef10$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQH3wx2RQj7VP9hMd2oXN/9H7zga9gGHJ0kyAlXXZaICcqC33aOu2PbA Content-Language: nl-be X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2018 14:56:41 -0000 > -----Original Message----- > From: Tom Jones > Sent: donderdag 10 mei 2018 15:48 > To: Dries Michiels > Cc: freebsd-net@freebsd.org > Subject: Re: kernel: in6_delayed_cksum: delayed m_pullup >=20 > On Mon, Apr 30, 2018 at 09:54:48AM +0200, Dries Michiels wrote: > > > > Tom, > > > > I=E2=80=99m using the igb (intel I210) driver for my LAN interface = and the em > > (intel I219-V) driver for the WAN interface. I use this FreeBSD box > > as my home server so I wouldn=E2=80=99t say that it has a heavy ipv6 = workload. > > >=20 > Hi Dries, >=20 > Does this bug persist on later snapshots? Or have you stayed with the = same > one from the original question? I had updated the day after to see if it was just a regression but the = error message was not gone: May 1 22:19:51 vados kernel: in6_delayed_cksum: delayed m_pullup, = m->len: 48 plen 68 off 56 csum_flags=3D400 May 1 22:27:57 vados last message repeated 29 times May 1 22:36:53 vados last message repeated 17 times May 1 22:49:41 vados last message repeated 6 times May 1 23:00:09 vados last message repeated 8 times May 1 23:01:06 vados last message repeated 7 times May 1 23:18:05 vados last message repeated 12 times For this reason I had disabled IPV6 for my LAN clients (disabled = rtadvd). My server was still ipv6 reachable and error messages where gone. > Could you send me the ifconfig flags lines for igb0 and em0? >=20 > like this >=20 > $ ifconfig em0 > em0: > flags=3D8943 > metric 0 mtu 1500 > options=3D40098 AN_HWTSO> >=20 > $ ifconfig igb0 > igb0: flags=3D8843 metric 0 > mtu 1500 >=20 > options=3D6403bb O_MTU,VLAN_HWCSUM,TSO4,TSO6,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM > _IPV6> ifconfig flags of my interfaces shown below. em0: flags=3D8843 metric 0 mtu = 1500 description: WAN = options=3D209b igb0: flags=3D8843 metric 0 mtu = 1500 description: LAN = options=3D6403bb > My em interfaces don't have flags for ipv6 checksum offload, I suspect = the > issue is from the em side of your network. >=20 > I have tried moving 100GB of v6 tcp through each interface with iperf3 = to see > if I could stimulate the bug, but no luck so far. I will leave the = test box sitting > exposed to my network for a while. >=20 > - [tj]