From owner-freebsd-net@FreeBSD.ORG Sun Feb 24 08:22:20 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 69AF0172; Sun, 24 Feb 2013 08:22:20 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.208.146]) by mx1.freebsd.org (Postfix) with ESMTP id 2C6F018BF; Sun, 24 Feb 2013 08:22:20 +0000 (UTC) Received: from maia.hub.org (unknown [200.46.151.188]) by hub.org (Postfix) with ESMTP id A50E8221010; Sun, 24 Feb 2013 04:22:12 -0400 (AST) Received: from hub.org ([200.46.208.146]) by maia.hub.org (mx1.hub.org [200.46.151.188]) (amavisd-maia, port 10024) with ESMTP id 14503-06; Sun, 24 Feb 2013 08:22:12 +0000 (UTC) Received: from [192.168.0.52] (S01067cb21b2ff4ca.gv.shawcable.net [24.108.26.71]) by hub.org (Postfix) with ESMTPA id 9822422100E; Sun, 24 Feb 2013 04:22:11 -0400 (AST) From: Marc Fournier Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: 9-STABLE: bce pulse(): Warning: bootcode thinks driver is absent Date: Sun, 24 Feb 2013 00:22:10 -0800 Message-Id: To: "freebsd-stable@freebsd.org" Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 24 Feb 2013 08:22:20 -0000 I just started to try and get VirtualBox up and running on this server = .. same configuration as another server I already have a few of them = running, but after a period of time with the install, I get the above = error pop up on my remote console, and pinging to the server itself just = dies =85 I'm up to date for src / 9-STABLE as of today =85 have never seen this = one before, nor can I seem to find anything useful through google except = for points to the code itself =85 When it dies, it isn't just the network that is dead, but the whole = machine appears to be un-responsive =85 When I rebuilt the kernel, I did also rebuild VirtualBox/kmod, since = I've experienced odd things with it in the past =85=20 Anyone have any ideas on what is causing this? Something with = VirtualBox triggering =85 something? Thx From owner-freebsd-net@FreeBSD.ORG Sun Feb 24 08:26:48 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 365803FF; Sun, 24 Feb 2013 08:26:48 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.208.146]) by mx1.freebsd.org (Postfix) with ESMTP id C885418FE; Sun, 24 Feb 2013 08:26:47 +0000 (UTC) Received: from maia.hub.org (unknown [200.46.151.188]) by hub.org (Postfix) with ESMTP id EEA91191CEAE; Sun, 24 Feb 2013 04:26:46 -0400 (AST) Received: from hub.org ([200.46.208.146]) by maia.hub.org (mx1.hub.org [200.46.151.188]) (amavisd-maia, port 10024) with ESMTP id 16009-01; Sun, 24 Feb 2013 08:26:46 +0000 (UTC) Received: from [192.168.0.52] (S01067cb21b2ff4ca.gv.shawcable.net [24.108.26.71]) by hub.org (Postfix) with ESMTPA id DBBB1191CEAD; Sun, 24 Feb 2013 04:26:45 -0400 (AST) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: 9-STABLE: bce pulse(): Warning: bootcode thinks driver is absent From: Marc Fournier In-Reply-To: Date: Sun, 24 Feb 2013 00:26:43 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: "freebsd-stable@freebsd.org" X-Mailer: Apple Mail (2.1499) Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 24 Feb 2013 08:26:48 -0000 Further to this =85 I just did a 'ctl-alt-del' through my remote = console, which appears to have 'unstuck' whatever it was, in that I got = a bunch of Login: prompts scroll up the screen (hit return a few times = after it got stuck), after which it seems to do a full shutdown and = reboot, as if nothing was wrong =85 I had a ping process running against that machine, which halted =85 but = when I hit ctl-alt-del, a whack of responses came back with really high = times: =3D=3D=3D 64 bytes from 200.46.151.146: icmp_seq=3D3104 ttl=3D64 time=3D215390.333 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3105 ttl=3D64 time=3D214389.342 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3286 ttl=3D64 time=3D33295.200 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3287 ttl=3D64 time=3D32294.228 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3288 ttl=3D64 time=3D31296.220 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3289 ttl=3D64 time=3D30296.262 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3315 ttl=3D64 time=3D4299.235 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3316 ttl=3D64 time=3D3299.278 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3317 ttl=3D64 time=3D2298.324 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3318 ttl=3D64 time=3D1299.448 = ms 64 bytes from 200.46.151.146: icmp_seq=3D3319 ttl=3D64 time=3D298.485 ms 64 bytes from 200.46.151.146: icmp_seq=3D3320 ttl=3D64 time=3D0.168 ms 64 bytes from 200.46.151.146: icmp_seq=3D3321 ttl=3D64 time=3D0.158 ms 64 bytes from 200.46.151.146: icmp_seq=3D3322 ttl=3D64 time=3D0.167 ms 64 bytes from 200.46.151.146: icmp_seq=3D3323 ttl=3D64 time=3D0.157 ms 64 bytes from 200.46.151.146: icmp_seq=3D3330 ttl=3D64 time=3D0.137 ms 64 bytes from 200.46.151.146: icmp_seq=3D3331 ttl=3D64 time=3D0.159 ms 64 bytes from 200.46.151.146: icmp_seq=3D3332 ttl=3D64 time=3D0.154 ms 64 bytes from 200.46.151.146: icmp_seq=3D3333 ttl=3D64 time=3D0.204 ms On 2013-02-24, at 12:22 AM, Marc Fournier wrote: >=20 > I just started to try and get VirtualBox up and running on this server = .. same configuration as another server I already have a few of them = running, but after a period of time with the install, I get the above = error pop up on my remote console, and pinging to the server itself just = dies =85 >=20 > I'm up to date for src / 9-STABLE as of today =85 have never seen this = one before, nor can I seem to find anything useful through google except = for points to the code itself =85 >=20 > When it dies, it isn't just the network that is dead, but the whole = machine appears to be un-responsive =85 >=20 > When I rebuilt the kernel, I did also rebuild VirtualBox/kmod, since = I've experienced odd things with it in the past =85=20 >=20 > Anyone have any ideas on what is causing this? Something with = VirtualBox triggering =85 something? >=20 > Thx >=20 >=20 >=20 >=20 From owner-freebsd-net@FreeBSD.ORG Sun Feb 24 10:06:52 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C898DCBD for ; Sun, 24 Feb 2013 10:06:52 +0000 (UTC) (envelope-from vegeta@tuxpowered.net) Received: from mail-ee0-f51.google.com (mail-ee0-f51.google.com [74.125.83.51]) by mx1.freebsd.org (Postfix) with ESMTP id 2DEB11B02 for ; Sun, 24 Feb 2013 10:06:51 +0000 (UTC) Received: by mail-ee0-f51.google.com with SMTP id d17so917216eek.24 for ; Sun, 24 Feb 2013 02:06:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:from:organization:to:subject:date:user-agent:references :in-reply-to:mime-version:content-type:content-transfer-encoding :message-id:x-gm-message-state; bh=2jSs1oHrW18YwQNRaoxZvFUYyADhYRworWxCHaDB1Kw=; b=JZSGwJloWwqCKaFFWYVJ5E/8EStahnE6rv0o0WKCc6Ncapq//1k14dM9tpClCpAr9I 9qM1M3Mi1g1GvoWuNRfrgFIUHDC23fByrRUu7AEbgizdlJVsOexU7Fh1yJmt0T4w2fBi SANbGJabC0BO0B5JDoO5Dy4lpIc17oB0rneG0f9tXmCbPmZYe6VG0D6jiBIesYd4pscZ dzpxurDE5XN4Q7MhFiKNp6m+1k0LZbsGJ/AfaFPPJtgncu28w/64uUOeI7ksloMn6kEf PsDx328cPP0r9g+lTG53MHUdYCteovFEE8rCZXyAp0Kh13OEouWawqvKg1XjUWvl9XsQ 4brA== X-Received: by 10.14.211.132 with SMTP id w4mr26354661eeo.36.1361700404757; Sun, 24 Feb 2013 02:06:44 -0800 (PST) Received: from zvezda.localnet (port-6198.pppoe.wtnet.de. [84.46.24.78]) by mx.google.com with ESMTPS id s3sm13015847eem.4.2013.02.24.02.06.43 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 24 Feb 2013 02:06:43 -0800 (PST) From: Kajetan Staszkiewicz Organization: TuxPowered To: freebsd-net@freebsd.org Subject: Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout Date: Sun, 24 Feb 2013 11:06:42 +0100 User-Agent: KMail/1.13.5 (Linux/3.6.6-vegeta.1; KDE/4.4.5; x86_64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201302241106.42477.vegeta@tuxpowered.net> X-Gm-Message-State: ALoCoQl3GwSsn7aqCwmN1MfwLLCbEpwi2VwSkCP9mRR47QBinT4PqTbV6k2epq026w1AyQT3tQA6 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 24 Feb 2013 10:06:52 -0000 Dnia sobota, 23 lutego 2013 o 04:54:07 Marc Fournier napisa=C5=82(a): > We just picked up 5 new HP DL 360p Gen8 E5-2630 2P servers =E2=80=A6 just= installed > 9.1-RELEASE, and it looks like all of the hardware is detected properly, > and being configured =E2=80=A6 >=20 > After reboot, I start getting the 'watchdog timeout - resetting' message = on > bge0 =E2=80=A6 I've searched the web, and found the references to setting: Have a look at the following patch: http://svnweb.freebsd.org/base?view=3Drevision&revision=3D243546 When I encountered the same error on Dell machines, using bge driver from H= EAD=20 helped me, although it seems that the aforementioned patch should be enough. =2D-=20 | pozdrawiam / greetings | powered by Debian, CentOS and FreeBSD | | Kajetan Staszkiewicz | jabber,email: vegeta()tuxpowered net | | Vegeta | www: http://vegeta.tuxpowered.net | `------------------------^---------------------------------------' From owner-freebsd-net@FreeBSD.ORG Sun Feb 24 23:29:02 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7CD8472D; Sun, 24 Feb 2013 23:29:02 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 3CBF9D8A; Sun, 24 Feb 2013 23:29:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1ONT2Yk013062; Sun, 24 Feb 2013 23:29:02 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1ONT2pK013058; Sun, 24 Feb 2013 23:29:02 GMT (envelope-from linimon) Date: Sun, 24 Feb 2013 23:29:02 GMT Message-Id: <201302242329.r1ONT2pK013058@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/176401: [netgraph] page fault in netgraph X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 24 Feb 2013 23:29:02 -0000 Old Synopsis: page fault in netgraph New Synopsis: [netgraph] page fault in netgraph Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Feb 24 23:28:37 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=176401 From owner-freebsd-net@FreeBSD.ORG Sun Feb 24 23:30:32 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8798D855; Sun, 24 Feb 2013 23:30:32 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 61EF8DB2; Sun, 24 Feb 2013 23:30:32 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1ONUWlA014674; Sun, 24 Feb 2013 23:30:32 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1ONUWMJ014670; Sun, 24 Feb 2013 23:30:32 GMT (envelope-from linimon) Date: Sun, 24 Feb 2013 23:30:32 GMT Message-Id: <201302242330.r1ONUWMJ014670@freefall.freebsd.org> To: gallatin@FreeBSD.org, linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/176369: [mxge] [patch] Correct some problem and do some cleanups X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 24 Feb 2013 23:30:32 -0000 Old Synopsis: [PATCH] mxge: Correct some problem and do some cleanups New Synopsis: [mxge] [patch] Correct some problem and do some cleanups Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sun Feb 24 23:29:46 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=176369 From owner-freebsd-net@FreeBSD.ORG Mon Feb 25 08:16:54 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 28D9226E for ; Mon, 25 Feb 2013 08:16:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) by mx1.freebsd.org (Postfix) with ESMTP id 04FFF3C6 for ; Mon, 25 Feb 2013 08:16:53 +0000 (UTC) Received: by mail-pa0-f47.google.com with SMTP id bj3so1610166pad.34 for ; Mon, 25 Feb 2013 00:16:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:date:to:cc:subject:message-id:reply-to:references :mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=fYgzi6Qjp4kKZ80yWQ8r2mJMP8BBTnh2MBJW0Ky0Jq0=; b=NyQn68mqzZM4zHOhHrHgQGrIT3nJXuNiX9EzR9ZAFUcOCpkew/iQQJ1gOm/kMW7ozF d8CcUSawhKXOljdK5Az+MlYX2lu2uPOefPSORadz6x/FPgc7WeN5SD9Ka7bk089wSx+t gu54lrNiBf54p8OpaHaAJ11k1+9f9f/mk3l8UAt71USYuYmvb5cfa0jpMF7KjOYPbfdA f4SHmWsFK8RfzgpwTk6+sfHRuTOG1hPC5JurDXOambsxGHp7TxQG08OTK4n9K2R4ddYM Kbq/jRKpDzIQSgRGYXWOgjg42Ypl4GKl1VSfgmSWJQTwK3Zk493OUWJinM8lLc2Qp6uT hH/Q== X-Received: by 10.66.162.196 with SMTP id yc4mr17881100pab.137.1361780213397; Mon, 25 Feb 2013 00:16:53 -0800 (PST) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id t4sm12942732pax.0.2013.02.25.00.16.49 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 25 Feb 2013 00:16:52 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Mon, 25 Feb 2013 17:16:46 +0900 From: YongHyeon PYUN Date: Mon, 25 Feb 2013 17:16:46 +0900 To: Marc Fournier Subject: Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout Message-ID: <20130225081646.GA1426@michelle.cdnetworks.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 08:16:54 -0000 On Fri, Feb 22, 2013 at 07:54:07PM -0800, Marc Fournier wrote: > > > > We just picked up 5 new HP DL 360p Gen8 E5-2630 2P servers … just installed 9.1-RELEASE, and it looks like all of the hardware is detected properly, and being configured … > > After reboot, I start getting the 'watchdog timeout - resetting' message on bge0 … I've searched the web, and found the references to setting: > > hw.bge.allow_asf="0" > hw.pci.enable_msi="0" > > but after reboot with those set in /boot/loader.conf (and confirmed via sysctl -a after login), its still doing it … > > Looking at sysctl -a, even though: > > hw.pci.enable_msi="0" > > is set, I do see: > > dev.bge.0.msi=1 > dev.bge.1.msi=1 > dev.bge.2.msi=1 > dev.bge.3.msi=1 > > still all set to 1 … is that right? > > Don't know if this is useful, but, again, according to sysctl -a: > > dev.bge.0.%desc: Broadcom unknown BCM5719, ASIC rev. 0x5719001 > > === > > If I do an 'ifconfig bge0', it does show the interface as being active, but I can't ping out on it … > > I even found someone's reference to doing a 'ifconfig bge0 -tso -vlanhwtso' and tried that … no go … > > Something else I can look at? You have to use latest stable/9 or stable/8. From owner-freebsd-net@FreeBSD.ORG Mon Feb 25 08:28:59 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B971F73B for ; Mon, 25 Feb 2013 08:28:59 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-da0-f50.google.com (mail-da0-f50.google.com [209.85.210.50]) by mx1.freebsd.org (Postfix) with ESMTP id 685D5661 for ; Mon, 25 Feb 2013 08:28:59 +0000 (UTC) Received: by mail-da0-f50.google.com with SMTP id h15so1144962dan.23 for ; Mon, 25 Feb 2013 00:28:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:date:to:cc:subject:message-id:reply-to:references :mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=ZBQRrG7RQ5lLYXbI1olFSfsYkpYE9xTywxnn9HD1XJU=; b=GlP/ykxtq+DfMq/Lqa9TReiT1fmUMGHckaG3AYpqPYCNy1x5Bnfyvr8KzTOM+1F3Cu VCOBXww67z3AH3LEuAGeCLPV97hN854USZNetH4Bc4S0jeWmN10vPf75a349Jl2Nn+zE Dg+Q/C5r8qnYqED2xnfIcmjhVgBIsNfxCw+9FIxfeoh3QskV7w1oT5YH8it2Jt90ulWp cNo1r+MHqUI5QuaKvDSIheIcQRtkhhY8mEJXCDajK9ZQ+81MECFZvxg3CD4eh5JoFbdt 3uVQ2r5x78sBbZV79n8+2b9M4hRMf9/NhBVen13gC7DlgBy2Z5F95EIxaBesCPWuy1xQ uvWQ== X-Received: by 10.68.191.229 with SMTP id hb5mr16851252pbc.201.1361780448651; Mon, 25 Feb 2013 00:20:48 -0800 (PST) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id zw3sm11972409pbc.23.2013.02.25.00.20.45 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 25 Feb 2013 00:20:47 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Mon, 25 Feb 2013 17:20:42 +0900 From: YongHyeon PYUN Date: Mon, 25 Feb 2013 17:20:42 +0900 To: Kajetan Staszkiewicz Subject: Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout Message-ID: <20130225082042.GB1426@michelle.cdnetworks.com> References: <201302241106.42477.vegeta@tuxpowered.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201302241106.42477.vegeta@tuxpowered.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 08:28:59 -0000 On Sun, Feb 24, 2013 at 11:06:42AM +0100, Kajetan Staszkiewicz wrote: > Dnia sobota, 23 lutego 2013 o 04:54:07 Marc Fournier napisaÅ‚(a): > > We just picked up 5 new HP DL 360p Gen8 E5-2630 2P servers … just installed > > 9.1-RELEASE, and it looks like all of the hardware is detected properly, > > and being configured … > > > > After reboot, I start getting the 'watchdog timeout - resetting' message on > > bge0 … I've searched the web, and found the references to setting: > > Have a look at the following patch: > > http://svnweb.freebsd.org/base?view=revision&revision=243546 > > When I encountered the same error on Dell machines, using bge driver from HEAD > helped me, although it seems that the aforementioned patch should be enough. That change is just one of changes required to make BCM5718/5718/5719/5720 work. You need entire bge(4)/brgphy(4) changes to get working bge(4) driver on your machines. From owner-freebsd-net@FreeBSD.ORG Mon Feb 25 11:06:51 2013 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C71BB162 for ; Mon, 25 Feb 2013 11:06:51 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id B9B57E7D for ; Mon, 25 Feb 2013 11:06:51 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1PB6pdv066673 for ; Mon, 25 Feb 2013 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1PB6pxe066671 for freebsd-net@FreeBSD.org; Mon, 25 Feb 2013 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 25 Feb 2013 11:06:51 GMT Message-Id: <201302251106.r1PB6pxe066671@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Subject: Current problem reports assigned to freebsd-net@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 11:06:51 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/176401 net [netgraph] page fault in netgraph o kern/176369 net [mxge] [patch] Correct some problem and do some cleanu o kern/176167 net [ipsec][lagg] using lagg and ipsec causes immediate pa o kern/176097 net [lagg] [patch] lagg/lacp broken when aggregated interf o kern/176027 net [em] [patch] flow control systcl consistency for em dr o kern/176026 net [tcp] [patch] TCP wrappers caused quite a lot of warni o bin/175974 net ppp(8): logic issue o kern/175864 net [re] Intel MB D510MO, onboard ethernet not working aft o kern/175852 net [amd64] [patch] in_cksum_hdr() behaves differently on o kern/175734 net no ethernet detected on system with EG20T PCH chipset o kern/175267 net [pf] [tap] pf + tap keep state problem o kern/175236 net [epair] [gif] epair and gif Devices On Bridge o kern/175182 net [panic] kernel panic on RADIX_MPATH when deleting rout o kern/175153 net [tcp] will there miss a FIN when do TSO? o kern/174959 net [net] [patch] rnh_walktree_from visits spurious nodes o kern/174958 net [net] [patch] rnh_walktree_from makes unreasonable ass o kern/174897 net [route] Interface routes are broken o kern/174851 net [bxe] [patch] UDP checksum offload is wrong in bxe dri o kern/174850 net [bxe] [patch] bxe driver does not receive multicasts o kern/174849 net [bxe] [patch] bxe driver can hang kernel when reset o kern/174822 net [tcp] Page fault in tcp_discardcb under high traffic o kern/174602 net [gif] [ipsec] traceroute issue on gif tunnel with ipse o kern/174535 net [tcp] TCP fast retransmit feature works strange o kern/173475 net [tun] tun(4) stays opened by PID after process is term o kern/173201 net [ixgbe] [patch] Missing / broken ixgbe sysctl's and tu o kern/173137 net [em] em(4) unable to run at gigabit with 9.1-RC2 o kern/173002 net [patch] data type size problem in if_spppsubr.c o kern/172985 net [patch] [ip6] lltable leak when adding and removing IP o kern/172895 net [ixgb] [ixgbe] do not properly determine link-state o kern/172683 net [ip6] Duplicate IPv6 Link Local Addresses o kern/172675 net [netinet] [patch] sysctl_tcp_hc_list (net.inet.tcp.hos o kern/172113 net [panic] [e1000] [patch] 9.1-RC1/amd64 panices in igb(4 o kern/171840 net [ip6] IPv6 packets transmitting only on queue 0 o kern/171739 net [bce] [panic] bce related kernel panic o kern/171711 net [dummynet] [panic] Kernel panic in dummynet o kern/171532 net [ndis] ndis(4) driver includes 'pccard'-specific code, o kern/171531 net [ndis] undocumented dependency for ndis(4) o kern/171524 net [ipmi] ipmi driver crashes kernel by reboot or shutdow s kern/171508 net [epair] [request] Add the ability to name epair device o kern/171228 net [re] [patch] if_re - eeprom write issues o kern/170701 net [ppp] killl ppp or reboot with active ppp connection c o kern/170267 net [ixgbe] IXGBE_LE32_TO_CPUS is probably an unintentiona o kern/170081 net [fxp] pf/nat/jails not working if checksum offloading o kern/169898 net ifconfig(8) fails to set MTU on multiple interfaces. o kern/169676 net [bge] [hang] system hangs, fully or partially after re o kern/169664 net [bgp] Wrongful replacement of interface connected net o kern/169620 net [ng] [pf] ng_l2tp incoming packet bypass pf firewall o kern/169459 net [ppp] umodem/ppp/3g stopped working after update from o kern/169438 net [ipsec] ipv4-in-ipv6 tunnel mode IPsec does not work p kern/168294 net [ixgbe] [patch] ixgbe driver compiled in kernel has no o kern/168246 net [em] Multiple em(4) not working with qemu o kern/168245 net [arp] [regression] Permanent ARP entry not deleted on o kern/168244 net [arp] [regression] Unable to manually remove permanent o kern/168183 net [bce] bce driver hang system o kern/167947 net [setfib] [patch] arpresolve checks only the default FI o kern/167603 net [ip] IP fragment reassembly's broken: file transfer ov o kern/167500 net [em] [panic] Kernel panics in em driver o kern/167325 net [netinet] [patch] sosend sometimes return EINVAL with o kern/167202 net [igmp]: Sending multiple IGMP packets crashes kernel o kern/167059 net [tcp] [panic] System does panic in in_pcbbind() and ha o kern/166940 net [ipfilter] [panic] Double fault in kern 8.2 o kern/166462 net [gre] gre(4) when using a tunnel source address from c o kern/166372 net [patch] ipfilter drops UDP packets with zero checksum o kern/166285 net [arp] FreeBSD v8.1 REL p8 arp: unknown hardware addres o kern/166255 net [net] [patch] It should be possible to disable "promis o kern/165963 net [panic] [ipf] ipfilter/nat NULL pointer deference o kern/165903 net mbuf leak o kern/165643 net [net] [patch] Missing vnet restores in net/if_ethersub o kern/165622 net [ndis][panic][patch] Unregistered use of FPU in kernel s kern/165562 net [request] add support for Intel i350 in FreeBSD 7.4 o kern/165526 net [bxe] UDP packets checksum calculation whithin if_bxe o kern/165488 net [ppp] [panic] Fatal trap 12 jails and ppp , kernel wit o kern/165305 net [ip6] [request] Feature parity between IP_TOS and IPV6 o kern/165296 net [vlan] [patch] Fix EVL_APPLY_VLID, update EVL_APPLY_PR o kern/165181 net [igb] igb freezes after about 2 weeks of uptime o kern/165174 net [patch] [tap] allow tap(4) to keep its address on clos o kern/165152 net [ip6] Does not work through the issue of ipv6 addresse o kern/164495 net [igb] connect double head igb to switch cause system t o kern/164490 net [pfil] Incorrect IP checksum on pfil pass from ip_outp o kern/164475 net [gre] gre misses RUNNING flag after a reboot o kern/164265 net [netinet] [patch] tcp_lro_rx computes wrong checksum i o kern/163903 net [igb] "igb0:tx(0)","bpf interface lock" v2.2.5 9-STABL o kern/163481 net freebsd do not add itself to ping route packet o kern/162927 net [tun] Modem-PPP error ppp[1538]: tun0: Phase: Clearing o kern/162926 net [ipfilter] Infinite loop in ipfilter with fragmented I o kern/162558 net [dummynet] [panic] seldom dummynet panics o kern/162153 net [em] intel em driver 7.2.4 don't compile o kern/162110 net [igb] [panic] RELENG_9 panics on boot in IGB driver - o kern/162028 net [ixgbe] [patch] misplaced #endif in ixgbe.c o kern/161277 net [em] [patch] BMC cannot receive IPMI traffic after loa o kern/160873 net [igb] igb(4) from HEAD fails to build on 7-STABLE o kern/160750 net Intel PRO/1000 connection breaks under load until rebo o kern/160693 net [gif] [em] Multicast packet are not passed from GIF0 t o kern/160293 net [ieee80211] ppanic] kernel panic during network setup o kern/160206 net [gif] gifX stops working after a while (IPv6 tunnel) o kern/159817 net [udp] write UDPv4: No buffer space available (code=55) o kern/159629 net [ipsec] [panic] kernel panic with IPsec in transport m o kern/159621 net [tcp] [panic] panic: soabort: so_count o kern/159603 net [netinet] [patch] in_ifscrubprefix() - network route c o kern/159601 net [netinet] [patch] in_scrubprefix() - loopback route re o kern/159294 net [em] em watchdog timeouts o kern/159203 net [wpi] Intel 3945ABG Wireless LAN not support IBSS o kern/158930 net [bpf] BPF element leak in ifp->bpf_if->bif_dlist o kern/158726 net [ip6] [patch] ICMPv6 Router Announcement flooding limi o kern/158694 net [ix] [lagg] ix0 is not working within lagg(4) o kern/158665 net [ip6] [panic] kernel pagefault in in6_setscope() o kern/158635 net [em] TSO breaks BPF packet captures with em driver f kern/157802 net [dummynet] [panic] kernel panic in dummynet o kern/157785 net amd64 + jail + ipfw + natd = very slow outbound traffi o kern/157418 net [em] em driver lockup during boot on Supermicro X9SCM- o kern/157410 net [ip6] IPv6 Router Advertisements Cause Excessive CPU U o kern/157287 net [re] [panic] INVARIANTS panic (Memory modified after f o kern/157209 net [ip6] [patch] locking error in rip6_input() (sys/netin o kern/157200 net [network.subr] [patch] stf(4) can not communicate betw o kern/157182 net [lagg] lagg interface not working together with epair o kern/156877 net [dummynet] [panic] dummynet move_pkt() null ptr derefe o kern/156667 net [em] em0 fails to init on CURRENT after March 17 o kern/156408 net [vlan] Routing failure when using VLANs vs. Physical e o kern/156328 net [icmp]: host can ping other subnet but no have IP from o kern/156317 net [ip6] Wrong order of IPv6 NS DAD/MLD Report o kern/156283 net [ip6] [patch] nd6_ns_input - rtalloc_mpath does not re o kern/156279 net [if_bridge][divert][ipfw] unable to correctly re-injec o kern/156226 net [lagg]: failover does not announce the failover to swi o kern/156030 net [ip6] [panic] Crash in nd6_dad_start() due to null ptr o kern/155772 net ifconfig(8): ioctl (SIOCAIFADDR): File exists on direc o kern/155680 net [multicast] problems with multicast s kern/155642 net [new driver] [request] Add driver for Realtek RTL8191S o kern/155597 net [panic] Kernel panics with "sbdrop" message o kern/155420 net [vlan] adding vlan break existent vlan o kern/155177 net [route] [panic] Panic when inject routes in kernel p kern/155030 net [igb] igb(4) DEVICE_POLLING does not work with carp(4) o kern/155010 net [msk] ntfs-3g via iscsi using msk driver cause kernel o kern/154943 net [gif] ifconfig gifX create on existing gifX clears IP s kern/154851 net [new driver] [request]: Port brcm80211 driver from Lin o kern/154850 net [netgraph] [patch] ng_ether fails to name nodes when t o kern/154679 net [em] Fatal trap 12: "em1 taskq" only at startup (8.1-R o kern/154600 net [tcp] [panic] Random kernel panics on tcp_output o kern/154557 net [tcp] Freeze tcp-session of the clients, if in the gat o kern/154443 net [if_bridge] Kernel module bridgestp.ko missing after u o kern/154286 net [netgraph] [panic] 8.2-PRERELEASE panic in netgraph o kern/154255 net [nfs] NFS not responding o kern/154214 net [stf] [panic] Panic when creating stf interface o kern/154185 net race condition in mb_dupcl o kern/154169 net [multicast] [ip6] Node Information Query multicast add o kern/154134 net [ip6] stuck kernel state in LISTEN on ipv6 daemon whic o kern/154091 net [netgraph] [panic] netgraph, unaligned mbuf? o conf/154062 net [vlan] [patch] change to way of auto-generatation of v o kern/153937 net [ral] ralink panics the system (amd64 freeBSDD 8.X) wh o kern/153936 net [ixgbe] [patch] MPRC workaround incorrectly applied to o kern/153816 net [ixgbe] ixgbe doesn't work properly with the Intel 10g o kern/153772 net [ixgbe] [patch] sysctls reference wrong XON/XOFF varia o kern/153497 net [netgraph] netgraph panic due to race conditions o kern/153454 net [patch] [wlan] [urtw] Support ad-hoc and hostap modes o kern/153308 net [em] em interface use 100% cpu o kern/153244 net [em] em(4) fails to send UDP to port 0xffff o kern/152893 net [netgraph] [panic] 8.2-PRERELEASE panic in netgraph o kern/152853 net [em] tftpd (and likely other udp traffic) fails over e o kern/152828 net [em] poor performance on 8.1, 8.2-PRE o kern/152569 net [net]: Multiple ppp connections and routing table prob o kern/152235 net [arp] Permanent local ARP entries are not properly upd o kern/152141 net [vlan] [patch] encapsulate vlan in ng_ether before out o kern/152036 net [libc] getifaddrs(3) returns truncated sockaddrs for n o kern/151690 net [ep] network connectivity won't work until dhclient is o kern/151681 net [nfs] NFS mount via IPv6 leads to hang on client with o kern/151593 net [igb] [panic] Kernel panic when bringing up igb networ o kern/150920 net [ixgbe][igb] Panic when packets are dropped with heade o kern/150557 net [igb] igb0: Watchdog timeout -- resetting o kern/150251 net [patch] [ixgbe] Late cable insertion broken o kern/150249 net [ixgbe] Media type detection broken o bin/150224 net ppp(8) does not reassign static IP after kill -KILL co f kern/149969 net [wlan] [ral] ralink rt2661 fails to maintain connectio o kern/149937 net [ipfilter] [patch] kernel panic in ipfilter IP fragmen o kern/149643 net [rum] device not sending proper beacon frames in ap mo o kern/149609 net [panic] reboot after adding second default route o kern/149117 net [inet] [patch] in_pcbbind: redundant test o kern/149086 net [multicast] Generic multicast join failure in 8.1 o kern/148018 net [flowtable] flowtable crashes on ia64 o kern/147912 net [boot] FreeBSD 8 Beta won't boot on Thinkpad i1300 11 o kern/147894 net [ipsec] IPv6-in-IPv4 does not work inside an ESP-only o kern/147155 net [ip6] setfb not work with ipv6 o kern/146845 net [libc] close(2) returns error 54 (connection reset by f kern/146792 net [flowtable] flowcleaner 100% cpu's core load o kern/146719 net [pf] [panic] PF or dumynet kernel panic o kern/146534 net [icmp6] wrong source address in echo reply o kern/146427 net [mwl] Additional virtual access points don't work on m f kern/146394 net [vlan] IP source address for outgoing connections o bin/146377 net [ppp] [tun] Interface doesn't clear addresses when PPP o kern/146358 net [vlan] wrong destination MAC address o kern/146165 net [wlan] [panic] Setting bssid in adhoc mode causes pani o kern/146082 net [ng_l2tp] a false invaliant check was performed in ng_ o kern/146037 net [panic] mpd + CoA = kernel panic o kern/145825 net [panic] panic: soabort: so_count o kern/145728 net [lagg] Stops working lagg between two servers. p kern/145600 net TCP/ECN behaves different to CE/CWR than ns2 reference f kern/144917 net [flowtable] [panic] flowtable crashes system [regressi o kern/144882 net MacBookPro =>4.1 does not connect to BSD in hostap wit o kern/144874 net [if_bridge] [patch] if_bridge frees mbuf after pfil ho o conf/144700 net [rc.d] async dhclient breaks stuff for too many people o kern/144616 net [nat] [panic] ip_nat panic FreeBSD 7.2 f kern/144315 net [ipfw] [panic] freebsd 8-stable reboot after add ipfw o kern/144231 net bind/connect/sendto too strict about sockaddr length o kern/143846 net [gif] bringing gif3 tunnel down causes gif0 tunnel to s kern/143673 net [stf] [request] there should be a way to support multi s kern/143666 net [ip6] [request] PMTU black hole detection not implemen o kern/143622 net [pfil] [patch] unlock pfil lock while calling firewall o kern/143593 net [ipsec] When using IPSec, tcpdump doesn't show outgoin o kern/143591 net [ral] RT2561C-based DLink card (DWL-510) fails to work o kern/143208 net [ipsec] [gif] IPSec over gif interface not working o kern/143034 net [panic] system reboots itself in tcp code [regression] o kern/142877 net [hang] network-related repeatable 8.0-STABLE hard hang o kern/142774 net Problem with outgoing connections on interface with mu o kern/142772 net [libc] lla_lookup: new lle malloc failed f kern/142518 net [em] [lagg] Problem on 8.0-STABLE with em and lagg o kern/142018 net [iwi] [patch] Possibly wrong interpretation of beacon- o kern/141861 net [wi] data garbled with WEP and wi(4) with Prism 2.5 f kern/141741 net Etherlink III NIC won't work after upgrade to FBSD 8, o kern/140742 net rum(4) Two asus-WL167G adapters cannot talk to each ot o kern/140682 net [netgraph] [panic] random panic in netgraph f kern/140634 net [vlan] destroying if_lagg interface with if_vlan membe o kern/140619 net [ifnet] [patch] refine obsolete if_var.h comments desc o kern/140346 net [wlan] High bandwidth use causes loss of wlan connecti o kern/140142 net [ip6] [panic] FreeBSD 7.2-amd64 panic w/IPv6 o kern/140066 net [bwi] install report for 8.0 RC 2 (multiple problems) o kern/139565 net [ipfilter] ipfilter ioctl SIOCDELST broken o kern/139387 net [ipsec] Wrong lenth of PF_KEY messages in promiscuous o bin/139346 net [patch] arp(8) add option to remove static entries lis o kern/139268 net [if_bridge] [patch] allow if_bridge to forward just VL p kern/139204 net [arp] DHCP server replies rejected, ARP entry lost bef o kern/139117 net [lagg] + wlan boot timing (EBUSY) o kern/139058 net [ipfilter] mbuf cluster leak on FreeBSD 7.2 o kern/138850 net [dummynet] dummynet doesn't work correctly on a bridge o kern/138782 net [panic] sbflush_internal: cc 0 || mb 0xffffff004127b00 o kern/138688 net [rum] possibly broken on 8 Beta 4 amd64: able to wpa a o kern/138678 net [lo] FreeBSD does not assign linklocal address to loop o kern/138407 net [gre] gre(4) interface does not come up after reboot o kern/138332 net [tun] [lor] ifconfig tun0 destroy causes LOR if_adata/ o kern/138266 net [panic] kernel panic when udp benchmark test used as r o kern/138177 net [ipfilter] FreeBSD crashing repeatedly in ip_nat.c:257 f kern/138029 net [bpf] [panic] periodically kernel panic and reboot o kern/137881 net [netgraph] [panic] ng_pppoe fatal trap 12 p bin/137841 net [patch] wpa_supplicant(8) cannot verify SHA256 signed p kern/137776 net [rum] panic in rum(4) driver on 8.0-BETA2 o bin/137641 net ifconfig(8): various problems with "vlan_device.vlan_i o kern/137392 net [ip] [panic] crash in ip_nat.c line 2577 o kern/137372 net [ral] FreeBSD doesn't support wireless interface from o kern/137089 net [lagg] lagg falsely triggers IPv6 duplicate address de o bin/136994 net [patch] ifconfig(8) print carp mac address o kern/136911 net [netgraph] [panic] system panic on kldload ng_bpf.ko t o kern/136618 net [pf][stf] panic on cloning interface without unit numb o kern/135502 net [periodic] Warning message raised by rtfree function i o kern/134583 net [hang] Machine with jail freezes after random amount o o kern/134531 net [route] [panic] kernel crash related to routes/zebra o kern/134157 net [dummynet] dummynet loads cpu for 100% and make a syst o kern/133969 net [dummynet] [panic] Fatal trap 12: page fault while in o kern/133968 net [dummynet] [panic] dummynet kernel panic o kern/133736 net [udp] ip_id not protected ... o kern/133595 net [panic] Kernel Panic at pcpu.h:195 o kern/133572 net [ppp] [hang] incoming PPTP connection hangs the system o kern/133490 net [bpf] [panic] 'kmem_map too small' panic on Dell r900 o kern/133235 net [netinet] [patch] Process SIOCDLIFADDR command incorre f kern/133213 net arp and sshd errors on 7.1-PRERELEASE o kern/133060 net [ipsec] [pfsync] [panic] Kernel panic with ipsec + pfs o kern/132889 net [ndis] [panic] NDIS kernel crash on load BCM4321 AGN d o conf/132851 net [patch] rc.conf(5): allow to setfib(1) for service run o kern/132734 net [ifmib] [panic] panic in net/if_mib.c o kern/132705 net [libwrap] [patch] libwrap - infinite loop if hosts.all o kern/132672 net [ndis] [panic] ndis with rt2860.sys causes kernel pani o kern/132554 net [ipl] There is no ippool start script/ipfilter magic t o kern/132354 net [nat] Getting some packages to ipnat(8) causes crash o kern/132277 net [crypto] [ipsec] poor performance using cryptodevice f o kern/131781 net [ndis] ndis keeps dropping the link o kern/131776 net [wi] driver fails to init o kern/131753 net [altq] [panic] kernel panic in hfsc_dequeue o kern/131601 net [ipfilter] [panic] 7-STABLE panic in nat_finalise (tcp o bin/131365 net route(8): route add changes interpretation of network f kern/130820 net [ndis] wpa_supplicant(8) returns 'no space on device' o kern/130628 net [nfs] NFS / rpc.lockd deadlock on 7.1-R o conf/130555 net [rc.d] [patch] No good way to set ipfilter variables a o kern/130525 net [ndis] [panic] 64 bit ar5008 ndisgen-erated driver cau o kern/130311 net [wlan_xauth] [panic] hostapd restart causing kernel pa o kern/130109 net [ipfw] Can not set fib for packets originated from loc f kern/130059 net [panic] Leaking 50k mbufs/hour f kern/129719 net [nfs] [panic] Panic during shutdown, tcp_ctloutput: in o kern/129517 net [ipsec] [panic] double fault / stack overflow f kern/129508 net [carp] [panic] Kernel panic with EtherIP (may be relat o kern/129219 net [ppp] Kernel panic when using kernel mode ppp o kern/129197 net [panic] 7.0 IP stack related panic o bin/128954 net ifconfig(8) deletes valid routes o bin/128602 net [an] wpa_supplicant(8) crashes with an(4) o kern/128448 net [nfs] 6.4-RC1 Boot Fails if NFS Hostname cannot be res o bin/128295 net [patch] ifconfig(8) does not print TOE4 or TOE6 capabi o bin/128001 net wpa_supplicant(8), wlan(4), and wi(4) issues o kern/127826 net [iwi] iwi0 driver has reduced performance and connecti o kern/127815 net [gif] [patch] if_gif does not set vlan attributes from o kern/127724 net [rtalloc] rtfree: 0xc5a8f870 has 1 refs f bin/127719 net [arp] arp: Segmentation fault (core dumped) f kern/127528 net [icmp]: icmp socket receives icmp replies not owned by p kern/127360 net [socket] TOE socket options missing from sosetopt() o bin/127192 net routed(8) removes the secondary alias IP of interface f kern/127145 net [wi]: prism (wi) driver crash at bigger traffic o kern/126895 net [patch] [ral] Add antenna selection (marked as TBD) o kern/126874 net [vlan]: Zebra problem if ifconfig vlanX destroy o kern/126695 net rtfree messages and network disruption upon use of if_ o kern/126339 net [ipw] ipw driver drops the connection o kern/126075 net [inet] [patch] internet control accesses beyond end of o bin/125922 net [patch] Deadlock in arp(8) o kern/125920 net [arp] Kernel Routing Table loses Ethernet Link status o kern/125845 net [netinet] [patch] tcp_lro_rx() should make use of hard o kern/125258 net [socket] socket's SO_REUSEADDR option does not work o kern/125239 net [gre] kernel crash when using gre o kern/124341 net [ral] promiscuous mode for wireless device ral0 looses o kern/124225 net [ndis] [patch] ndis network driver sometimes loses net o kern/124160 net [libc] connect(2) function loops indefinitely o kern/124021 net [ip6] [panic] page fault in nd6_output() o kern/123968 net [rum] [panic] rum driver causes kernel panic with WPA. o kern/123892 net [tap] [patch] No buffer space available o kern/123890 net [ppp] [panic] crash & reboot on work with PPP low-spee o kern/123858 net [stf] [patch] stf not usable behind a NAT o kern/123796 net [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not o kern/123758 net [panic] panic while restarting net/freenet6 o bin/123633 net ifconfig(8) doesn't set inet and ether address in one o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o bin/123465 net [ip6] route(8): route add -inet6 -interfac o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices f kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge o kern/122685 net It is not visible passing packets in tcpdump(1) o kern/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal o kern/122252 net [ipmi] [bge] IPMI problem with BCM5704 (does not work o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup ieee o bin/121895 net [patch] rtsol(8)/rtsold(8) doesn't handle managed netw s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/121555 net [panic] Fatal trap 12: current process = 12 (swi1: net o kern/121443 net [gif] [lor] icmp6_input/nd6_lookup o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA o bin/121359 net [patch] [security] ppp(8): fix local stack overflow in o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/120966 net [rum] kernel panic with if_rum and WPA encryption o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time o kern/120266 net [udp] [panic] gnugk causes kernel panic when closing U o bin/120060 net routed(8) deletes link-level routes in the presence of o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119432 net [arp] route add -host -iface causes arp e o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr o kern/118727 net [netgraph] [patch] [request] add new ng_pf module o kern/117423 net [vlan] Duplicate IP on different interfaces o bin/117339 net [patch] route(8): loading routing management commands o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/115019 net [netgraph] ng_ether upper hook packet flow stops on ad o kern/115002 net [wi] if_wi timeout. failed allocation (busy bit). ifco o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o kern/113432 net [ucom] WARNING: attempt to net_add_domain(netgraph) af o kern/112722 net [ipsec] [udp] IP v4 udp fragmented packet reject o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/111537 net [inet6] [patch] ip6_input() treats mbuf cluster wrong o kern/111457 net [ral] ral(4) freeze o kern/110284 net [if_ethersubr] Invalid Assumption in SIOCSIFADDR in et o kern/110249 net [kernel] [regression] [patch] setsockopt() error regre o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/107944 net [wi] [patch] Forget to unlock mutex-locks o conf/107035 net [patch] bridge(8): bridge interface given in rc.conf n o kern/106444 net [netgraph] [panic] Kernel Panic on Binding to an ip to o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets o kern/105945 net Address can disappear from network interface s kern/105943 net Network stack may modify read-only mbuf chain copies o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] o kern/104851 net [inet6] [patch] On link routes not configured when usi o kern/104751 net [netgraph] kernel panic, when getting info about my tr o kern/103191 net Unpredictable reboot o kern/103135 net [ipsec] ipsec with ipfw divert (not NAT) encodes a pac o kern/102540 net [netgraph] [patch] supporting vlan(4) by ng_fec(4) o conf/102502 net [netgraph] [patch] ifconfig name does't rename netgrap o kern/102035 net [plip] plip networking disables parallel port printing o kern/101948 net [ipf] [panic] Kernel Panic Trap No 12 Page Fault - cau o kern/100709 net [libc] getaddrinfo(3) should return TTL info o kern/100519 net [netisr] suggestion to fix suboptimal network polling o kern/98978 net [ipf] [patch] ipfilter drops OOW packets under 6.1-Rel o kern/98597 net [inet6] Bug in FreeBSD 6.1 IPv6 link-local DAD procedu o bin/98218 net wpa_supplicant(8) blacklist not working o kern/97306 net [netgraph] NG_L2TP locks after connection with failed o conf/97014 net [gif] gifconfig_gif? in rc.conf does not recognize IPv f kern/96268 net [socket] TCP socket performance drops by 3000% if pack o kern/95519 net [ral] ral0 could not map mbuf o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/95267 net packet drops periodically appear f kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo o kern/93019 net [ppp] ppp and tunX problems: no traffic after restarti o kern/92880 net [libc] [patch] almost rewritten inet_network(3) functi s kern/92279 net [dc] Core faults everytime I reboot, possible NIC issu o kern/91859 net [ndis] if_ndis does not work with Asus WL-138 s kern/91777 net [ipf] [patch] wrong behaviour with skip rule inside an o kern/91364 net [ral] [wep] WF-511 RT2500 Card PCI and WEP o kern/91311 net [aue] aue interface hanging o kern/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k o kern/87421 net [netgraph] [panic]: ng_ether + ng_eiface + if_bridge o kern/86871 net [tcp] [patch] allocation logic for PCBs in TIME_WAIT s o kern/86427 net [lor] Deadlock with FASTIPSEC and nat o kern/86103 net [ipf] Illegal NAT Traversal in IPFilter o kern/85780 net 'panic: bogus refcnt 0' in routing/ipv6 o bin/85445 net ifconfig(8): deprecated keyword to ifconfig inoperativ p kern/85320 net [gre] [patch] possible depletion of kernel stack in ip o bin/82975 net route change does not parse classfull network as given o kern/82881 net [netgraph] [panic] ng_fec(4) causes kernel panic after o kern/82468 net Using 64MB tcp send/recv buffers, trafficflow stops, i o bin/82185 net [patch] ndp(8) can delete the incorrect entry o kern/81095 net IPsec connection stops working if associated network i o kern/78968 net FreeBSD freezes on mbufs exhaustion (network interface o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if o kern/77341 net [ip6] problems with IPV6 implementation s kern/77195 net [ipf] [patch] ipfilter ioctl SIOCGNATL does not match o kern/75873 net Usability problem with non-RFC-compliant IP spoof prot s kern/75407 net [an] an(4): no carrier after short time a kern/71474 net [route] route lookup does not skip interfaces marked d o kern/71469 net default route to internet magically disappears with mu o kern/70904 net [ipf] ipfilter ipnat problem with h323 proxy support o kern/68889 net [panic] m_copym, length > size of mbuf chain o kern/66225 net [netgraph] [patch] extend ng_eiface(4) control message o kern/65616 net IPSEC can't detunnel GRE packets after real ESP encryp s kern/60293 net [patch] FreeBSD arp poison patch a kern/56233 net IPsec tunnel (ESP) over IPv6: MTU computation is wrong s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr o kern/39937 net ipstealth issue a kern/38554 net [patch] changing interface ipaddress doesn't seem to w o kern/34665 net [ipf] [hang] ipfilter rcmd proxy "hangs". o kern/31940 net ip queue length too short for >500kpps o kern/31647 net [libc] socket calls can return undocumented EINVAL o kern/30186 net [libc] getaddrinfo(3) does not handle incorrect servna o kern/27474 net [ipf] [ppp] Interactive use of user PPP and ipfilter c f kern/24959 net [patch] proper TCP_NOPUSH/TCP_CORK compatibility o conf/23063 net [arp] [patch] for static ARP tables in rc.network o kern/21998 net [socket] [patch] ident only for outgoing connections o kern/5877 net [socket] sb_cc counts control data as well as data dat 447 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Feb 25 13:36:02 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CE1DD5A1; Mon, 25 Feb 2013 13:36:02 +0000 (UTC) (envelope-from gallatin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 8DA52D2E; Mon, 25 Feb 2013 13:36:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1PDa2ni097501; Mon, 25 Feb 2013 13:36:02 GMT (envelope-from gallatin@freefall.freebsd.org) Received: (from gallatin@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1PDa2Rt097497; Mon, 25 Feb 2013 13:36:02 GMT (envelope-from gallatin) Date: Mon, 25 Feb 2013 13:36:02 GMT Message-Id: <201302251336.r1PDa2Rt097497@freefall.freebsd.org> To: gallatin@FreeBSD.org, gallatin@FreeBSD.org, freebsd-net@FreeBSD.org, gallatin@FreeBSD.org From: gallatin@FreeBSD.org Subject: Re: kern/176369: [mxge] [patch] Correct some problem and do some cleanups X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 13:36:02 -0000 Synopsis: [mxge] [patch] Correct some problem and do some cleanups Responsible-Changed-From-To: freebsd-net->gallatin Responsible-Changed-By: gallatin Responsible-Changed-When: Mon Feb 25 13:36:02 UTC 2013 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=176369 From owner-freebsd-net@FreeBSD.ORG Mon Feb 25 18:16:05 2013 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1DC0E220 for ; Mon, 25 Feb 2013 18:16:05 +0000 (UTC) (envelope-from harrison@biostat.wisc.edu) Received: from agogare.doit.wisc.edu (agogare.doit.wisc.edu [144.92.197.211]) by mx1.freebsd.org (Postfix) with ESMTP id EEF1BCFE for ; Mon, 25 Feb 2013 18:16:04 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0MIS00D00F8LTV00@smtpauth2.wiscmail.wisc.edu> for freebsd-net@FreeBSD.org; Mon, 25 Feb 2013 12:16:03 -0600 (CST) X-Spam-PmxInfo: Server=avs-2, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.2.25.175717, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from seal.biostat.wisc.edu (seal.biostat.wisc.edu [144.92.73.36]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0MIS000ADG2OQG50@smtpauth2.wiscmail.wisc.edu> for freebsd-net@FreeBSD.org; Mon, 25 Feb 2013 12:16:01 -0600 (CST) X-Wisc-Sender: harrison@biostat.wisc.edu Message-id: <512BAA60.3060703@biostat.wisc.edu> Date: Mon, 25 Feb 2013 12:16:00 -0600 From: "Christopher D. Harrison" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121116 Thunderbird/10.0.11 To: freebsd-net@FreeBSD.org Subject: igb network lockups X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 18:16:05 -0000 I recently have been experiencing network "freezes" and network "lockups" on our Freebsd 9.1 systems which are running zfs and nfs file servers. I upgraded from 9.0 to 9.1 about 2 months ago and we have been having issues with almost bi-monthly. The issue manifests in the system becomes unresponsive to any/all nfs clients. The system is not resource bound as our I/O is low to disk and our network is usually in the 20mbit/40mbit range. We do notice a correlation between temporary i/o spikes and network freezes but not enough to send our system in to "lockup" mode for the next 5min. Currently we have 4 igb nics in 2 aggr's with 8 queue's per nic and our dev.igb reports: dev.igb.3.%desc: Intel(R) PRO/1000 Network Connection version - 2.3.4 I am almost certain the problem is with the ibg driver as a friend is also experiencing the same problem with the same intel igb nic. He has addressed the issue by restarting the network using netif on his systems. According to my friend, once the network interfaces get cleared, everything comes back and starts working as expected. I have noticed an issue with the igb driver and I was looking for thoughts on how to help address this problem. http://freebsd.1045724.n5.nabble.com/em-igb-if-transmit-drbr-and-ALTQ-td5760338.html Thoughts/Ideas are greatly appreciated!!! -C From owner-freebsd-net@FreeBSD.ORG Mon Feb 25 18:29:33 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DD01E5BB for ; Mon, 25 Feb 2013 18:29:33 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ve0-f182.google.com (mail-ve0-f182.google.com [209.85.128.182]) by mx1.freebsd.org (Postfix) with ESMTP id A2972DC3 for ; Mon, 25 Feb 2013 18:29:33 +0000 (UTC) Received: by mail-ve0-f182.google.com with SMTP id ox1so2454913veb.41 for ; Mon, 25 Feb 2013 10:29:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=CRUDoAAwPSftbUNpl9teVJDX+l/OVTMSmvcL8P0S8fo=; b=RIJOZENq6Nb339+KUqq+pId7HcmdCyLBLQIv/NI85+/dz9S9vbHMFPTbBovsvMz9pK pnNRpNl7vlG8wWmPOugFic3Wr4EPKzcAUZat10WPLxfeLh2xXnMMrqfV/ZyQAEKj09nv m4lFstv2CPH61BlsOZTQ+PvmSt2pNRyP3Ss+QJRnTW22ERHFcRqpOcUZTMpFmyM403c2 u97YIF5mFOEoaIVbtw5noJllrS+DYWhDsp+U0t0Bsk9ghBEpxQ8PFYl8X7M6wJUokWUD GrClIKUt64K9hN/031MJPkZNs5bdakn4n53jD0ysZfVo4yaZKVH2AEUas5j8vCOV5+HY bWNw== MIME-Version: 1.0 X-Received: by 10.52.66.41 with SMTP id c9mr8948730vdt.32.1361816967742; Mon, 25 Feb 2013 10:29:27 -0800 (PST) Received: by 10.220.191.132 with HTTP; Mon, 25 Feb 2013 10:29:27 -0800 (PST) In-Reply-To: <512BAA60.3060703@biostat.wisc.edu> References: <512BAA60.3060703@biostat.wisc.edu> Date: Mon, 25 Feb 2013 10:29:27 -0800 Message-ID: Subject: Re: igb network lockups From: Jack Vogel To: "Christopher D. Harrison" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 18:29:33 -0000 I've not heard of this problem, but I think most users do not use ALTQ, and we (Intel) do not test using it. Can it be eliminated from the equation? Jack On Mon, Feb 25, 2013 at 10:16 AM, Christopher D. Harrison < harrison@biostat.wisc.edu> wrote: > I recently have been experiencing network "freezes" and network "lockups" > on our Freebsd 9.1 systems which are running zfs and nfs file servers. > I upgraded from 9.0 to 9.1 about 2 months ago and we have been having > issues with almost bi-monthly. The issue manifests in the system becomes > unresponsive to any/all nfs clients. The system is not resource bound as > our I/O is low to disk and our network is usually in the 20mbit/40mbit > range. We do notice a correlation between temporary i/o spikes and > network freezes but not enough to send our system in to "lockup" mode for > the next 5min. Currently we have 4 igb nics in 2 aggr's with 8 queue's > per nic and our dev.igb reports: > > dev.igb.3.%desc: Intel(R) PRO/1000 Network Connection version - 2.3.4 > > I am almost certain the problem is with the ibg driver as a friend is also > experiencing the same problem with the same intel igb nic. He has > addressed the issue by restarting the network using netif on his systems. > According to my friend, once the network interfaces get cleared, everything > comes back and starts working as expected. > > I have noticed an issue with the igb driver and I was looking for thoughts > on how to help address this problem. > http://freebsd.1045724.n5.**nabble.com/em-igb-if-transmit-** > drbr-and-ALTQ-td5760338.html > > Thoughts/Ideas are greatly appreciated!!! > > -C > > ______________________________**_________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/**mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@**freebsd.org > " > From owner-freebsd-net@FreeBSD.ORG Mon Feb 25 18:38:10 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2F2B0807 for ; Mon, 25 Feb 2013 18:38:10 +0000 (UTC) (envelope-from harrison@biostat.wisc.edu) Received: from agogare.doit.wisc.edu (agogare.doit.wisc.edu [144.92.197.211]) by mx1.freebsd.org (Postfix) with ESMTP id 05AA0E24 for ; Mon, 25 Feb 2013 18:38:09 +0000 (UTC) MIME-version: 1.0 Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0MIS00H00GIDE400@smtpauth2.wiscmail.wisc.edu> for freebsd-net@freebsd.org; Mon, 25 Feb 2013 12:38:09 -0600 (CST) X-Spam-PmxInfo: Server=avs-2, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.2.25.182720, SenderIP=0.0.0.0 X-Spam-Report: AuthenticatedSender=yes, SenderIP=0.0.0.0 Received: from seal.biostat.wisc.edu (seal.biostat.wisc.edu [144.92.73.36]) by smtpauth2.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0MIS00CSMH3HUH10@smtpauth2.wiscmail.wisc.edu> for freebsd-net@freebsd.org; Mon, 25 Feb 2013 12:38:06 -0600 (CST) Date: Mon, 25 Feb 2013 12:38:05 -0600 From: "Christopher D. Harrison" Subject: Re: igb network lockups In-reply-to: To: Jack Vogel Message-id: <512BAF8D.7080308@biostat.wisc.edu> X-Wisc-Sender: harrison@biostat.wisc.edu References: <512BAA60.3060703@biostat.wisc.edu> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121116 Thunderbird/10.0.11 Content-Type: text/plain; CHARSET=US-ASCII; format=flowed Content-Transfer-Encoding: 7BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 18:38:10 -0000 Sure, The problem appears on both systems running with ALTQ and vanilla. -C On 02/25/13 12:29, Jack Vogel wrote: > I've not heard of this problem, but I think most users do not use > ALTQ, and we (Intel) do not > test using it. Can it be eliminated from the equation? > > Jack > > > On Mon, Feb 25, 2013 at 10:16 AM, Christopher D. Harrison > > wrote: > > I recently have been experiencing network "freezes" and network > "lockups" on our Freebsd 9.1 systems which are running zfs and nfs > file servers. > I upgraded from 9.0 to 9.1 about 2 months ago and we have been > having issues with almost bi-monthly. The issue manifests in the > system becomes unresponsive to any/all nfs clients. The system > is not resource bound as our I/O is low to disk and our network is > usually in the 20mbit/40mbit range. We do notice a correlation > between temporary i/o spikes and network freezes but not enough to > send our system in to "lockup" mode for the next 5min. Currently > we have 4 igb nics in 2 aggr's with 8 queue's per nic and our > dev.igb reports: > > dev.igb.3.%desc: Intel(R) PRO/1000 Network Connection version - 2.3.4 > > I am almost certain the problem is with the ibg driver as a friend > is also experiencing the same problem with the same intel igb nic. > He has addressed the issue by restarting the network using netif > on his systems. According to my friend, once the network > interfaces get cleared, everything comes back and starts working > as expected. > > I have noticed an issue with the igb driver and I was looking for > thoughts on how to help address this problem. > http://freebsd.1045724.n5.nabble.com/em-igb-if-transmit-drbr-and-ALTQ-td5760338.html > > Thoughts/Ideas are greatly appreciated!!! > > -C > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to > "freebsd-net-unsubscribe@freebsd.org > " > > From owner-freebsd-net@FreeBSD.ORG Mon Feb 25 18:45:09 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 41FBD951 for ; Mon, 25 Feb 2013 18:45:09 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-ve0-f180.google.com (mail-ve0-f180.google.com [209.85.128.180]) by mx1.freebsd.org (Postfix) with ESMTP id CFF6AE79 for ; Mon, 25 Feb 2013 18:45:08 +0000 (UTC) Received: by mail-ve0-f180.google.com with SMTP id jx10so2434650veb.25 for ; Mon, 25 Feb 2013 10:45:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=LaH8LFSmnBQ+30w1q1doUY7bhTnUs8VpLYXRx0IpxZo=; b=d0zfdNArlLouzBjASNeW5a8VzI9fc7UpYs5+WdkdW00nJevg9wX+emdMZF7C1tQAX3 cCVr1G9ORC3DnIUf06EbAmaPlwBU7qf21cKzJrSkPEI40hZD0R6l9HayIL3Xr2Xpx6za UwDx0QPwKWkcJbuxxE+5h94S5VwN0OkGuF42LRvazpN2lBr6SqNbc1UPnWf6HQMocV9X 0QNv/NjMdk3Tjypf0AsU6rcjMx+Q63En6GU67wmmWauJI1dTE6PibfAWU3nmAVtVy1zQ xJWT2m6H0/DcdENUHjYKnhDvYE8GK04l5rB4nzvOykO+4EX7M1DmRXbwb8J/vrhyleXj F6mQ== MIME-Version: 1.0 X-Received: by 10.220.205.195 with SMTP id fr3mr10240365vcb.6.1361817902598; Mon, 25 Feb 2013 10:45:02 -0800 (PST) Received: by 10.220.191.132 with HTTP; Mon, 25 Feb 2013 10:45:02 -0800 (PST) In-Reply-To: <512BAF8D.7080308@biostat.wisc.edu> References: <512BAA60.3060703@biostat.wisc.edu> <512BAF8D.7080308@biostat.wisc.edu> Date: Mon, 25 Feb 2013 10:45:02 -0800 Message-ID: Subject: Re: igb network lockups From: Jack Vogel To: "Christopher D. Harrison" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 18:45:09 -0000 Have you done any poking around, looking at stats to determine why the hangs? For instance, might your mbuf pool be depleted? Some other network resource perhaps? Jack On Mon, Feb 25, 2013 at 10:38 AM, Christopher D. Harrison < harrison@biostat.wisc.edu> wrote: > Sure, > The problem appears on both systems running with ALTQ and vanilla. > -C > > On 02/25/13 12:29, Jack Vogel wrote: > > I've not heard of this problem, but I think most users do not use ALTQ, > and we (Intel) do not > test using it. Can it be eliminated from the equation? > > Jack > > > On Mon, Feb 25, 2013 at 10:16 AM, Christopher D. Harrison < > harrison@biostat.wisc.edu> wrote: > >> I recently have been experiencing network "freezes" and network "lockups" >> on our Freebsd 9.1 systems which are running zfs and nfs file servers. >> I upgraded from 9.0 to 9.1 about 2 months ago and we have been having >> issues with almost bi-monthly. The issue manifests in the system becomes >> unresponsive to any/all nfs clients. The system is not resource bound as >> our I/O is low to disk and our network is usually in the 20mbit/40mbit >> range. We do notice a correlation between temporary i/o spikes and >> network freezes but not enough to send our system in to "lockup" mode for >> the next 5min. Currently we have 4 igb nics in 2 aggr's with 8 queue's >> per nic and our dev.igb reports: >> >> dev.igb.3.%desc: Intel(R) PRO/1000 Network Connection version - 2.3.4 >> >> I am almost certain the problem is with the ibg driver as a friend is >> also experiencing the same problem with the same intel igb nic. He has >> addressed the issue by restarting the network using netif on his systems. >> According to my friend, once the network interfaces get cleared, everything >> comes back and starts working as expected. >> >> I have noticed an issue with the igb driver and I was looking for >> thoughts on how to help address this problem. >> >> http://freebsd.1045724.n5.nabble.com/em-igb-if-transmit-drbr-and-ALTQ-td5760338.html >> >> Thoughts/Ideas are greatly appreciated!!! >> >> -C >> >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > > > From owner-freebsd-net@FreeBSD.ORG Tue Feb 26 13:38:43 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D0F93C1B; Tue, 26 Feb 2013 13:38:43 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 83C28324; Tue, 26 Feb 2013 13:38:43 +0000 (UTC) Received: from lstewart1.loshell.room52.net (ppp59-167-184-191.static.internode.on.net [59.167.184.191]) by lauren.room52.net (Postfix) with ESMTPSA id 151BC7E88D; Wed, 27 Feb 2013 00:38:36 +1100 (EST) Message-ID: <512CBADB.3050004@freebsd.org> Date: Wed, 27 Feb 2013 00:38:35 +1100 From: Lawrence Stewart User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120613 Thunderbird/13.0 MIME-Version: 1.0 To: Andre Oppermann Subject: Bug in sbsndptr() Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lauren.room52.net Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2013 13:38:43 -0000 Hi Andre, A colleague and I spent a very frustrating day tracing an accounting bug in the multipath TCP patch we're working on at CAIA to a bug in sbsndptr(). I haven't tested it with regular TCP yet, but I believe the following patch fixes the bug (proposed commit log message is at the top of the patch): http://people.freebsd.org/~lstewart/patches/misctcp/sbsndptr_mnext_10.x.r247314.diff The patch should have no tangible effect to operation other than to ensure the function delivers on the promise to return the closest mbuf in the chain for the given offset. I would appreciate a review and any thoughts. Cheers, Lawrence From owner-freebsd-net@FreeBSD.ORG Tue Feb 26 16:56:43 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C2E71E94 for ; Tue, 26 Feb 2013 16:56:43 +0000 (UTC) (envelope-from dkandula@gmail.com) Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49]) by mx1.freebsd.org (Postfix) with ESMTP id 4BEC0FB4 for ; Tue, 26 Feb 2013 16:56:42 +0000 (UTC) Received: by mail-wg0-f49.google.com with SMTP id 15so3508507wgd.4 for ; Tue, 26 Feb 2013 08:56:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=r2s96hN4XTxXqEV0nnh62fivMJnlO3r7XjP/kkgibq8=; b=pnSyNvLLMGiIP4gfYGBDt7i76xBU3+d0JvheRTJznqujDm7HuMRuabzUTChUiQdtbo apT+hI8DRW4aWKjXEQmByb3xrDgNLAh24OQJpxZuDnJBpUjTQ5EmBPU30HuxYSt9Ahl3 feOKA0uW8tsHUInqF86SlDUa00KNjtHf4hgbP8Wbwu2HYVVg5RfGHADC/M6oufkZURWA /0mn+j3vObXw+ZZvdRcYBeWs38YkX95C/chpEIe3dUFUggzBc3xjG39ct6OLq7gRYLaS SNi3miScEC/wm+mGN822spFcYRFsrD0fu3Lk1AVxMPgTyA2Ow6Dd0k+2wQ4A7BQNGc9i Eviw== MIME-Version: 1.0 X-Received: by 10.194.108.229 with SMTP id hn5mr28045882wjb.8.1361897801968; Tue, 26 Feb 2013 08:56:41 -0800 (PST) Received: by 10.194.108.104 with HTTP; Tue, 26 Feb 2013 08:56:41 -0800 (PST) Date: Tue, 26 Feb 2013 11:56:41 -0500 Message-ID: Subject: Clarifications required in rn_delete From: Dheeraj Kandula To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2013 16:56:43 -0000 Hey All, I have been reading through the routing path code in FreeBSD 9.1 and have a few questions while adding and deleting a route using rn_addroute() and rn_delete(). My questions are highlighted in bold. In the code fragment below - part of rn_delete() function: b = -1 - tt->rn_bit; t = saved_tt->rn_parent; if (b > t->rn_bit) goto on1; /* Wasn't lifted at all */ do { x = t; t = t->rn_parent; } while (b <= t->rn_bit && x != top); for (mp = &x->rn_mklist; (m = *mp); mp = &m->rm_mklist) if (m == saved_m) { *mp = m->rm_mklist; MKFree(m); break; } if (m == 0) { log(LOG_ERR, "rn_delete: couldn't find our annotation\n"); if (tt->rn_flags & RNF_NORMAL) return (0); /* Dangling ref to us */ } the node "m" inside the for loop is removed from x's rn_mklist and inserted into rn_mkfreelist. *Shouldn't a test for the rm_refs similar to code below - part of rn_delete() too - be performed.??* /* * Demote routes attached to us. */ if (t->rn_mklist) { if (x->rn_bit >= 0) { for (mp = &x->rn_mklist; (m = *mp);) mp = &m->rm_mklist; *mp = t->rn_mklist; } else { /* If there are any key,mask pairs in a sibling duped-key chain, some subset will appear sorted in the same order attached to our mklist */ for (m = t->rn_mklist; m && x; x = x->rn_dupedkey) if (m == x->rn_mklist) { struct radix_mask *mm = m->rm_mklist; x->rn_mklist = 0; * if (--(m->rm_refs) < 0) MKFree(m);* m = mm; } if (m) log(LOG_ERR, "rn_delete: Orphaned Mask %p at %p\n", m, x); } } My understanding is that for leaf nodes that represent a network route, there will be only one radix_mask node in the linked list. When a new route is being added i.e. rn_addroute(), the other child of the new route's parent i.e. the sibling of the new route's node, can be either a leaf or an internal node. The scenarios are described below: 1. Leaf Node. a. If it is a leaf that is a network route and no duplicate routes at x i.e. x->rn_dupedkey is NULL, a new radix_mask node is created when the rn_bit is >= the new route's rn_bit i.e. x->rn_bit >= b_leaf and x->rn_mklist == 0. /* Promote general routes from below */ if (x->rn_bit < 0) { for (mp = &t->rn_mklist; x; x = x->rn_dupedkey) if (x->rn_mask && (x->rn_bit >= b_leaf) && x->rn_mklist == 0) { *mp = m = rn_new_radix_mask(x, 0); if (m) mp = &m->rm_mklist; } } b. If it is a leaf that is a network node and there are duplicate routes at x i.e. x->rn_dupedkey is NON-NULL, a new radix_mask node is added for every node in the duplicate linked list if. x->rn_bit >= b_leaf. as per the code above in case a. 2. Internal Node: If it is an internal node and the x->rn_mklist is NON-NULL, the linked list headed by x->rn_mklist is traversed and the traversal is discontinued only if m->rm_bit >= b_leaf. else if (x->rn_mklist) { /* * Skip over masks whose index is > that of new node */ for (mp = &x->rn_mklist; (m = *mp); mp = &m->rm_mklist) if (m->rm_bit >= b_leaf) break; t->rn_mklist = m; *mp = 0; } Here x will always be an internal node and hence if (m->rm_bit >= b_leaf) will always fail as b_leaf is a signed short and rm_bit is a signed short too and b_leaf is negative as b_leaf is -1 -t->rn_bit. *Isn't it? Is this a bug in the code.* Dheeraj From owner-freebsd-net@FreeBSD.ORG Tue Feb 26 17:37:09 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0723DC61 for ; Tue, 26 Feb 2013 17:37:09 +0000 (UTC) (envelope-from if@xip.at) Received: from chile.gbit.at (ns1.xip.at [193.239.188.99]) by mx1.freebsd.org (Postfix) with ESMTP id CF38311E5 for ; Tue, 26 Feb 2013 17:37:06 +0000 (UTC) Received: (qmail 9353 invoked from network); 26 Feb 2013 18:30:23 +0100 Received: from fw.xip.at (HELO ?127.0.0.1?) (89.207.145.147) by chile.gbit.at with SMTP; 26 Feb 2013 18:30:23 +0100 Message-ID: <512CF131.7010001@xip.at> Date: Tue, 26 Feb 2013 18:30:25 +0100 From: Ingo Flaschberger User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: Clarifications required in rn_delete References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2013 17:37:09 -0000 Am 26.02.2013 17:56, schrieb Dheeraj Kandula: > Here x will always be an internal node and hence if (m->rm_bit >= b_leaf) > will always fail as b_leaf is a signed short and rm_bit is a signed short > too and b_leaf is negative as b_leaf is -1 -t->rn_bit. *Isn't it? Is this a > bug in the code.* at least there is a bug with radix_mpath; I had problems with no more existing leafs. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/173477 -- Mit freundlichen Grüßen, With best regards, Ingo Flaschberger Geschäftsleitung --- Beschreibung: Beschreibung: Beschreibung: logo_email2 *Besondere Ansprüche. Individuelle Lösungen. Particular demands. **Individual solutions.*** crossip communications gmbh A-1020 Wien, Wohlmutstrasse 27 Sitz der Gesellschaft: 1020 Wien, Österreich Firmenbuchgericht: Handelsgericht Wien, FN 269698 s, Umsatzsteueridentifikationsnummer (UID): ATU62080367 Haftungsausschluss / Disclaimer: _http://www.crossip.net/de/legal/haftungsausschluss-disclaimer_ From owner-freebsd-net@FreeBSD.ORG Tue Feb 26 18:05:54 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 62B5E8BC for ; Tue, 26 Feb 2013 18:05:54 +0000 (UTC) (envelope-from emz@norma.perm.ru) Received: from elf.hq.norma.perm.ru (unknown [IPv6:2001:470:1f09:14c0::2]) by mx1.freebsd.org (Postfix) with ESMTP id 11D9214DF for ; Tue, 26 Feb 2013 18:05:53 +0000 (UTC) Received: from [192.168.248.32] ([192.168.248.32]) by elf.hq.norma.perm.ru (8.14.5/8.14.5) with ESMTP id r1QI5mEu048028 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Wed, 27 Feb 2013 00:05:48 +0600 (YEKT) (envelope-from emz@norma.perm.ru) Message-ID: <512CF97B.8030805@norma.perm.ru> Date: Wed, 27 Feb 2013 00:05:47 +0600 From: "Eugene M. Zheganin" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout References: <201302241106.42477.vegeta@tuxpowered.net> <20130225082042.GB1426@michelle.cdnetworks.com> In-Reply-To: <20130225082042.GB1426@michelle.cdnetworks.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (elf.hq.norma.perm.ru [192.168.3.10]); Wed, 27 Feb 2013 00:05:48 +0600 (YEKT) X-Spam-Status: No hits=-101.0 bayes=0.5 testhits ALL_TRUSTED=-1, USER_IN_WHITELIST=-100 autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on elf.hq.norma.perm.ru X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Feb 2013 18:05:54 -0000 Hi. On 25.02.2013 14:20, YongHyeon PYUN wrote: > On Sun, Feb 24, 2013 at 11:06:42AM +0100, Kajetan Staszkiewicz wrote: >> Dnia sobota, 23 lutego 2013 o 04:54:07 Marc Fournier napisaÅ‚(a): >>> We just picked up 5 new HP DL 360p Gen8 E5-2630 2P servers … just installed >>> 9.1-RELEASE, and it looks like all of the hardware is detected properly, >>> and being configured … >>> >>> After reboot, I start getting the 'watchdog timeout - resetting' message on >>> bge0 … I've searched the web, and found the references to setting: >> Have a look at the following patch: >> >> http://svnweb.freebsd.org/base?view=revision&revision=243546 >> >> When I encountered the same error on Dell machines, using bge driver from HEAD >> helped me, although it seems that the aforementioned patch should be enough. > That change is just one of changes required to make > BCM5718/5718/5719/5720 work. You need entire bge(4)/brgphy(4) > changes to get working bge(4) driver on your machines. > Just to clear some things: this (or earlier changes) doesn't affect and doesn't enable IPMI sol and stuff on a BCM5722 ? Thanks. Eugene. From owner-freebsd-net@FreeBSD.ORG Wed Feb 27 00:09:55 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 74A5297B; Wed, 27 Feb 2013 00:09:55 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 4189BABC; Wed, 27 Feb 2013 00:09:55 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1R09tui012442; Wed, 27 Feb 2013 00:09:55 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1R09tEb012438; Wed, 27 Feb 2013 00:09:55 GMT (envelope-from linimon) Date: Wed, 27 Feb 2013 00:09:55 GMT Message-Id: <201302270009.r1R09tEb012438@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/176446: [netinet] [patch] Concurrency in ixgbe driving out-of-order packet process and spurious RST X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2013 00:09:55 -0000 Old Synopsis: Concurrency in ixgbe driving out-of-order packet process and spurious RST New Synopsis: [netinet] [patch] Concurrency in ixgbe driving out-of-order packet process and spurious RST Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Feb 27 00:09:22 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=176446 From owner-freebsd-net@FreeBSD.ORG Wed Feb 27 00:19:37 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 58EB2FEB; Wed, 27 Feb 2013 00:19:37 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 30808B6B; Wed, 27 Feb 2013 00:19:37 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1R0Jbg7015672; Wed, 27 Feb 2013 00:19:37 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1R0JbnT015668; Wed, 27 Feb 2013 00:19:37 GMT (envelope-from linimon) Date: Wed, 27 Feb 2013 00:19:37 GMT Message-Id: <201302270019.r1R0JbnT015668@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/176419: [kernel] [patch] socketpair support for LOCAL_PEERCRED X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2013 00:19:37 -0000 Old Synopsis: [patch] socketpair support for LOCAL_PEERCRED New Synopsis: [kernel] [patch] socketpair support for LOCAL_PEERCRED Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Feb 27 00:19:05 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=176419 From owner-freebsd-net@FreeBSD.ORG Wed Feb 27 00:19:53 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D7213151; Wed, 27 Feb 2013 00:19:53 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id B3081B8B; Wed, 27 Feb 2013 00:19:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1R0Jrxt015718; Wed, 27 Feb 2013 00:19:53 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1R0Jrcn015714; Wed, 27 Feb 2013 00:19:53 GMT (envelope-from linimon) Date: Wed, 27 Feb 2013 00:19:53 GMT Message-Id: <201302270019.r1R0Jrcn015714@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/176420: [kernel] [patch] incorrect errno for LOCAL_PEERCRED X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2013 00:19:53 -0000 Old Synopsis: [patch] incorrect errno for LOCAL_PEERCRED New Synopsis: [kernel] [patch] incorrect errno for LOCAL_PEERCRED Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Wed Feb 27 00:19:39 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=176420 From owner-freebsd-net@FreeBSD.ORG Wed Feb 27 02:01:37 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CF570589 for ; Wed, 27 Feb 2013 02:01:37 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) by mx1.freebsd.org (Postfix) with ESMTP id A9F3114D for ; Wed, 27 Feb 2013 02:01:37 +0000 (UTC) Received: by mail-pa0-f45.google.com with SMTP id kl14so101290pab.4 for ; Tue, 26 Feb 2013 18:01:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:date:to:cc:subject:message-id:reply-to:references :mime-version:content-type:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=4z/vbV7vwR6gfn2J3fzWqnSZ/pW9rhzVYGFzGKVQ+TM=; b=fGPu397UVJIPBggAWeqMiRQ+CQFNOkpd+CVKSd/Fk/nnLltfdlnUDwut6VccO17CPC b1D78bmCYCODrlyT16e0rvG+ngn6qRBw/Fji/tNKFKbzfkb100Qf/+7oEYxrSNI7SlPF +c+TFqf56dcMoBUDqmYRHf86AmqPEnip4xFYH4r4nk0S7vHAEhQQapcPHfz19gANDm/u R+fzWs8aCZFVtLhvHUGDja88AnF4kOkWm+5oL5tG4c44FuAGEaOO9i8sCXer77kv2ecy Qu+dsIAyxNyg3U7zYdVyMFLLgyKYn4vdUa19KVVSaYWf0ip22r/ydvsU+akbAV63AmOS K3bw== X-Received: by 10.68.210.164 with SMTP id mv4mr782772pbc.30.1361930490937; Tue, 26 Feb 2013 18:01:30 -0800 (PST) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id zw3sm2754096pbc.23.2013.02.26.18.01.27 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 26 Feb 2013 18:01:29 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 27 Feb 2013 11:01:23 +0900 From: YongHyeon PYUN Date: Wed, 27 Feb 2013 11:01:23 +0900 To: "Eugene M. Zheganin" Subject: Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout Message-ID: <20130227020123.GA3581@michelle.cdnetworks.com> References: <201302241106.42477.vegeta@tuxpowered.net> <20130225082042.GB1426@michelle.cdnetworks.com> <512CF97B.8030805@norma.perm.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <512CF97B.8030805@norma.perm.ru> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2013 02:01:37 -0000 On Wed, Feb 27, 2013 at 12:05:47AM +0600, Eugene M. Zheganin wrote: > Hi. > > On 25.02.2013 14:20, YongHyeon PYUN wrote: > >On Sun, Feb 24, 2013 at 11:06:42AM +0100, Kajetan Staszkiewicz wrote: > >>Dnia sobota, 23 lutego 2013 o 04:54:07 Marc Fournier napisaÅ‚(a): > >>>We just picked up 5 new HP DL 360p Gen8 E5-2630 2P servers … just > >>>installed > >>>9.1-RELEASE, and it looks like all of the hardware is detected properly, > >>>and being configured … > >>> > >>>After reboot, I start getting the 'watchdog timeout - resetting' message > >>>on > >>>bge0 … I've searched the web, and found the references to setting: > >>Have a look at the following patch: > >> > >>http://svnweb.freebsd.org/base?view=revision&revision=243546 > >> > >>When I encountered the same error on Dell machines, using bge driver from > >>HEAD > >>helped me, although it seems that the aforementioned patch should be > >>enough. > >That change is just one of changes required to make > >BCM5718/5718/5719/5720 work. You need entire bge(4)/brgphy(4) > >changes to get working bge(4) driver on your machines. > > > Just to clear some things: this (or earlier changes) doesn't affect and > doesn't enable IPMI sol and stuff on a BCM5722 ? bge(4)'s IPMI support for old controllers had many issues and didn't work well. Only some of users had luck to enjoy it. However IPMI support for 5717/5718/5719/5720 has no known issues and it should work. I also got a report that mentions IPMI does not work any more on 5715 after adding support for 5717/5718/5719/5720. The sanitized public data sheet does not mention IPMI interface so Linux tg3 would be the only source of information. Given that I don't have access to IPMI-capable controllers I have no idea when it could be fixed. Somebody with the IPMI-capable controllers have to sit down and verify all possible combinations. > > Thanks. > Eugene. From owner-freebsd-net@FreeBSD.ORG Wed Feb 27 06:33:57 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8BF63737; Wed, 27 Feb 2013 06:33:57 +0000 (UTC) (envelope-from sales@hub.org) Received: from hub.org (hub.org [200.46.208.146]) by mx1.freebsd.org (Postfix) with ESMTP id 5A4B8CD9; Wed, 27 Feb 2013 06:33:57 +0000 (UTC) Received: from maia.hub.org (unknown [200.46.151.189]) by hub.org (Postfix) with ESMTP id C1C081BCD87; Wed, 27 Feb 2013 02:33:49 -0400 (AST) Received: from hub.org ([200.46.208.146]) by maia.hub.org (mx1.hub.org [200.46.151.189]) (amavisd-maia, port 10024) with ESMTP id 83205-05; Wed, 27 Feb 2013 06:33:49 +0000 (UTC) Received: from [192.168.0.52] (S01067cb21b2ff4ca.gv.shawcable.net [24.108.26.71]) by hub.org (Postfix) with ESMTPA id CE9CC1BCD86; Wed, 27 Feb 2013 02:33:48 -0400 (AST) From: Sales Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Odd issue with VirtualBox+9-STABLE+bce ... Date: Tue, 26 Feb 2013 22:33:47 -0800 Message-Id: <2A0FD48D-6CEF-4A70-B915-724315C48674@hub.org> To: "freebsd-net@freebsd.org" Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) X-Mailer: Apple Mail (2.1499) Cc: "freebsd-emulation@freebsd.org" , "freebsd-stable@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2013 06:33:57 -0000 I'm experiencing some odd issues with Virtualbox running on 9-STABLE. = where my network periodically disappears =85 sometimes, it comes back = again after a few minutes, other times I have to reboot the server =85 This last time, the error on the screen states: bce1: bce_pulse(): Warning: boot code thinks driver is absent! (bc_state = =3D 0x00004006) I had 20 regular 'jail' VPSs running on it before I tried VirtualBox on = it,and never had this problem, so figure it has to be something with = VirtualBox / kmod =85 ? Anyone experiencing any odd issues with VirtualBox and 9-STABLE? = Pointers / ideas? Thx =85 From owner-freebsd-net@FreeBSD.ORG Wed Feb 27 11:16:40 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 79DE3A89 for ; Wed, 27 Feb 2013 11:16:40 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 240ED966 for ; Wed, 27 Feb 2013 11:16:40 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 7B68828435; Wed, 27 Feb 2013 12:09:29 +0100 (CET) Received: from [192.168.1.2] (unknown [89.177.49.69]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id A058228433; Wed, 27 Feb 2013 12:09:28 +0100 (CET) Message-ID: <512DE968.4020409@quip.cz> Date: Wed, 27 Feb 2013 12:09:28 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: pyunyh@gmail.com Subject: Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout References: <201302241106.42477.vegeta@tuxpowered.net> <20130225082042.GB1426@michelle.cdnetworks.com> <512CF97B.8030805@norma.perm.ru> <20130227020123.GA3581@michelle.cdnetworks.com> In-Reply-To: <20130227020123.GA3581@michelle.cdnetworks.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2013 11:16:40 -0000 YongHyeon PYUN wrote: > On Wed, Feb 27, 2013 at 12:05:47AM +0600, Eugene M. Zheganin wrote: [...] > bge(4)'s IPMI support for old controllers had many issues and > didn't work well. Only some of users had luck to enjoy it. However > IPMI support for 5717/5718/5719/5720 has no known issues and it > should work. I also got a report that mentions IPMI does not work > any more on 5715 after adding support for 5717/5718/5719/5720. > The sanitized public data sheet does not mention IPMI interface so > Linux tg3 would be the only source of information. Given that I > don't have access to IPMI-capable controllers I have no idea when > it could be fixed. Somebody with the IPMI-capable controllers have > to sit down and verify all possible combinations. I have a spare machine Sun Fire X2100 M2 with 5715C: bge0@pci0:6:4:0: class=0x020000 card=0x534c108e chip=0x167814e4 rev=0xa3 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5715C 10/100/100 PCIe Ethernet Controller' class = network subclass = ethernet bge1@pci0:6:4:1: class=0x020000 card=0x534c108e chip=0x167814e4 rev=0xa3 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5715C 10/100/100 PCIe Ethernet Controller' class = network subclass = ethernet I can provide you full access to this machine (if you want) or let me know, what version I should check. Older versions (6.x - 8.3) are working fine with hw.bge.allow_asf="1" in loader.conf. I didn't test newer releases on these old machines. Miroslav Lachman From owner-freebsd-net@FreeBSD.ORG Wed Feb 27 14:20:02 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 61667E2 for ; Wed, 27 Feb 2013 14:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 538B6379 for ; Wed, 27 Feb 2013 14:20:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1REK1Bb003965 for ; Wed, 27 Feb 2013 14:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1REK1QL003964; Wed, 27 Feb 2013 14:20:01 GMT (envelope-from gnats) Date: Wed, 27 Feb 2013 14:20:01 GMT Message-Id: <201302271420.r1REK1QL003964@freefall.freebsd.org> To: freebsd-net@FreeBSD.org Cc: From: "Charbon, Julien" Subject: Re: kern/176446: Concurrency in ixgbe driving out-of-order packet process and spurious RST X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: "Charbon, Julien" List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2013 14:20:02 -0000 The following reply was made to PR kern/176446; it has been noted by GNATS. From: "Charbon, Julien" To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org Cc: jfv@FreeBSD.org, "De La Gueronniere, Marc" Subject: Re: kern/176446: Concurrency in ixgbe driving out-of-order packet process and spurious RST Date: Wed, 27 Feb 2013 13:54:20 +0100 I successfully reproduced this issue using only the socat tool: Server side: Enable TCP debug, and launch socat server: # sysctl net.inet.tcp.log_debug=1 net.inet.tcp.log_debug: 0 -> 1 $ cat /some/where/response.sh #!/usr/bin/env bash read line echo -n "01234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567" $ socat TCP4-LISTEN:8181,fork,reuseaddr EXEC:/some/where/response.sh Client side: Create socat client TCP load: $ cat ./request 128 $ while true; do socat ./request,ignoreeof\!\!./response TCP4:192.168.100.144:8181 & sleep 0.0001; done Then on server side just wait for a TCP debug in /var/log/debug.log like: kernel: TCP: [192.168.100.136]:48359 to [192.168.100.144]:8181; syncache_socket: in_pcbconnect failed with error 48 kernel: TCP: [192.168.100.136]:48359 to [192.168.100.144]:8181 tcpflags 0x10; tcp_input: Listen socket: Socket allocation failed due to limits or memory shortage, sending RST kernel: TCP: [192.168.100.136]:48359 to [192.168.100.144]:8181 tcpflags 0x4; syncache_chkrst: Spurious RST without matching syncache entry (possibly syncookie only), segment ignored Adding Jack F. Vogel (ixgbe driver maintainer), and Marc De La Gueronniere (author of our work in progress patch for this issue). -- Julien From owner-freebsd-net@FreeBSD.ORG Thu Feb 28 01:40:27 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3799ED8A for ; Thu, 28 Feb 2013 01:40:27 +0000 (UTC) (envelope-from cvaruneng04@gmail.com) Received: from mail-lb0-f180.google.com (mail-lb0-f180.google.com [209.85.217.180]) by mx1.freebsd.org (Postfix) with ESMTP id A4D3D8B for ; Thu, 28 Feb 2013 01:40:26 +0000 (UTC) Received: by mail-lb0-f180.google.com with SMTP id q12so964378lbc.25 for ; Wed, 27 Feb 2013 17:40:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=hc+4wdtPTYQNQqg+KAPnrB0RKbYuRfHLTfTaST3keYg=; b=PRfQHJQsbfusAciLOHqz2CNFgoDUuH2XtDt8TGPD7lisDFnq88x1cgOR9n3Rohl9lC 6QfpOBbDp3u6502XLvVFtMOq5K2lWgf5BEnahDpbEGiIaWLUFEbHRtyZyggD0kklwDC/ af+2XgDVr45faGRB0xGuDAPRsgWsis2yTjjNu6XBnQqGyFvOyeKA5YU3kIqWriINqNmq GqjtKsO8hZrZGhGOqvBNKu2vMy59voHWzT66My/9SizPsZ+UjzK9SaE8NkPzBM4A44ym mKTCW4SA1Ch1WxZ20sSSAaHEI8mFHYpgbd7exEODfns295xP81WV+TtWkoex6X4Lmz8e Icwg== MIME-Version: 1.0 X-Received: by 10.152.110.167 with SMTP id ib7mr3891151lab.22.1362015625312; Wed, 27 Feb 2013 17:40:25 -0800 (PST) Received: by 10.112.76.167 with HTTP; Wed, 27 Feb 2013 17:40:25 -0800 (PST) Date: Thu, 28 Feb 2013 12:40:25 +1100 Message-ID: Subject: Divert socket issues From: Varun Chandramohan To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 28 Feb 2013 01:40:27 -0000 Hi All, I wrote a small program using divert sockets to capture packets using ipfw at outgoing. The packets that are captured is for application mangling (mostly http headers) and resent it back to browser. That means I need to reinject it back in incoming instead of outgoing. I believe this is possible based on what is said in the man pages. Man page: if sendto(2) is used with a destination IP address of INADDR_ANY, then the packet is treated as if it were outgoing, i.e., destined for a non-local address. Otherwise, the packet is assumed to be incoming and full packet routing is done. In the latter case, the IP address specified must match the address of some local interface, or an interface name must be found after the IP address. If an interface name is found, that interface will be used and the value of the IP address will be ignored (other than the fact that it is not INADDR_ANY). This is to indicate on which interface the packet ``arrived.'' According to these instructions, I want my packet In-bound so I set my local ip address for the sendto data structure using the below code. ssize_t divert_get(int sd, struct sockaddr_in *sa, char *pkt_buf, int buflen){ ssize_t len; unsigned int addrlen; addrlen = sizeof(*sa); len = recvfrom(sd, pkt_buf, buflen, 0, (struct sockaddr *) sa, &addrlen); if(len == -1) { bps_log(LOG_ERR, "Unable to recieve message from socket", errno); } return(len);} /* addr is passed &sa from the above code */ rebuild_header(void *ptr, struct sockaddr_in *addr) { ssize_t new_len = change_header(ptr);struct ip *ip = (struct ip*)ptr; /* this is to divert it to input instead of output */ addr->sin_addr.s_addr = ip->ip_src.s_addr; /* Recompute checksums */ ip->ip_len = htons(new_len); cal_ip_cksum(ptr); cal_tcp_cksum(ptr); if(divert_send(sd, addr, ptr, pkt_len) < 0) { printf("No data sent from divert socket %d", errno); } } I expect the packet to now be inbound but my application is not getting the response sent by me. The possible case could be kernel dropping the packet. I even set the port number which is the rule I want to match for example, I have only two rules 1 and 65535. I tried setting port number to 0,1 and even 65535 but still the kernel drops the packet. addr->sin_port = htons(65535); sento seems to work fine but the packet does not go through. If I re-inject the packet back in the outgoing path (same place I took the packet) things seem to work fine. Can someone please tell me whats wrong here? I don't seem to understand. The man page is not very clear. I looked a bit into divert code and it seem to call ip_input() for the packet I re-injected. If thats the case, won't my packet get dropped because it has src address as my local address (it expects it to be other way around if server has responded)? Can someone please clarify this? If I have to still do it, do I need to modify TCP/IP header fields as well? Regards, Varun From owner-freebsd-net@FreeBSD.ORG Thu Feb 28 02:38:58 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AE787110; Thu, 28 Feb 2013 02:38:58 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 0452C2E3; Thu, 28 Feb 2013 02:38:57 +0000 (UTC) Received: by mail-wi0-f170.google.com with SMTP id hm11so8455848wib.1 for ; Wed, 27 Feb 2013 18:38:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=LyL+IJ/2aaAQmRj3i2IBlcb1Z3VVqEXaGoLICwWP5EU=; b=SjsIoB9xJYkoRqOJhUIhVDvjJcDtr/xlpP5Ndt43p10JqJ4D8hgvyoagId2ieeWndz S5qNRtRXm1KM2STyD4gqSkW2No7v9HRtj1IDH7SNIFwNPU3ZkbD7wrsz5X+9ginGkJ/c 1PQ3XYZFtUTGWR8LqMEePa9G2xdAfCJL9NRfocXV6Sb9ObX2K7hAVUeL2GPx3/XaAZD8 x9IqegTBJXZTEiAnf1oMCxPdZ1WrTyRchXDMwQl1Xnxo0zP1ddx7nvSrTbH1+YinmheB JHqRqWK5116dHCebQylzFLNKnuGQgZlo3h+nzzkdfEbEaHb3zFqPzBkA9f7QlfyX34yx 1lVg== MIME-Version: 1.0 X-Received: by 10.194.110.69 with SMTP id hy5mr7942237wjb.1.1362018815827; Wed, 27 Feb 2013 18:33:35 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.114.201 with HTTP; Wed, 27 Feb 2013 18:33:35 -0800 (PST) In-Reply-To: <201302270009.r1R09tEb012438@freefall.freebsd.org> References: <201302270009.r1R09tEb012438@freefall.freebsd.org> Date: Wed, 27 Feb 2013 18:33:35 -0800 X-Google-Sender-Auth: 5X5Ou1mjES3YhsUvFai2EWiijJw Message-ID: Subject: Re: kern/176446: [netinet] [patch] Concurrency in ixgbe driving out-of-order packet process and spurious RST From: Adrian Chadd To: FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1 Cc: Jack F Vogel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 28 Feb 2013 02:38:58 -0000 Hi, This is an interesting bug in ixgbe worth reading and poking. Yay concurrency bugs. :-) Adrian On 26 February 2013 16:09, wrote: > Old Synopsis: Concurrency in ixgbe driving out-of-order packet process and spurious RST > New Synopsis: [netinet] [patch] Concurrency in ixgbe driving out-of-order packet process and spurious RST > > Responsible-Changed-From-To: freebsd-bugs->freebsd-net > Responsible-Changed-By: linimon > Responsible-Changed-When: Wed Feb 27 00:09:22 UTC 2013 > Responsible-Changed-Why: > Over to maintainer(s). > > http://www.freebsd.org/cgi/query-pr.cgi?pr=176446 > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Thu Feb 28 05:36:11 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8A3F4964 for ; Thu, 28 Feb 2013 05:36:11 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pb0-f51.google.com (mail-pb0-f51.google.com [209.85.160.51]) by mx1.freebsd.org (Postfix) with ESMTP id 6291FB7E for ; Thu, 28 Feb 2013 05:36:11 +0000 (UTC) Received: by mail-pb0-f51.google.com with SMTP id un15so853243pbc.10 for ; Wed, 27 Feb 2013 21:36:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:date:to:cc:subject:message-id:reply-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=oLRZc57rTpj2mWkeRPYxBXoEPOIZ76PH5w2yP3jzwU8=; b=MzepqzaEm6sHoLEgyMogVY1XPYpcwPf0n1eL1VMetaCZnuH4wk3oWaAg12acbdpf9D 8NCwoOIebX2Y/K3UYT8CpCTwmrT8ZXwd9QrPD73rYhZtn+oKfe70OlFa+o0WxAbIUt0M kOEV540+apMmYlW8kBsWM3HGIuw4bJQzrxZbV01RAoZn/wOhHjbREUDsO4vYSOyMPDUr iRnO9wk/hRL5nyqefhj/67V5RAfPLh4n6NnrdS21vkEYYhKx815sRbJ2kmKioUen0jy4 q8LTHp+x8JaVseTe2K51i+Px2HiwlwKwL/ADvFHhW1Su30hzrhwKHqYysOlsgDxa3ZVy UeIw== X-Received: by 10.66.144.105 with SMTP id sl9mr11310479pab.154.1362029765617; Wed, 27 Feb 2013 21:36:05 -0800 (PST) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id x2sm7937638paw.8.2013.02.27.21.36.02 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 27 Feb 2013 21:36:04 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 28 Feb 2013 14:35:58 +0900 From: YongHyeon PYUN Date: Thu, 28 Feb 2013 14:35:58 +0900 To: Miroslav Lachman <000.fbsd@quip.cz> Subject: Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout Message-ID: <20130228053558.GA1474@michelle.cdnetworks.com> References: <201302241106.42477.vegeta@tuxpowered.net> <20130225082042.GB1426@michelle.cdnetworks.com> <512CF97B.8030805@norma.perm.ru> <20130227020123.GA3581@michelle.cdnetworks.com> <512DE968.4020409@quip.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <512DE968.4020409@quip.cz> User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 05:36:11 -0000 On Wed, Feb 27, 2013 at 12:09:28PM +0100, Miroslav Lachman wrote: > YongHyeon PYUN wrote: > >On Wed, Feb 27, 2013 at 12:05:47AM +0600, Eugene M. Zheganin wrote: > > [...] > > >bge(4)'s IPMI support for old controllers had many issues and > >didn't work well. Only some of users had luck to enjoy it. However > >IPMI support for 5717/5718/5719/5720 has no known issues and it > >should work. I also got a report that mentions IPMI does not work > >any more on 5715 after adding support for 5717/5718/5719/5720. > >The sanitized public data sheet does not mention IPMI interface so > >Linux tg3 would be the only source of information. Given that I > >don't have access to IPMI-capable controllers I have no idea when > >it could be fixed. Somebody with the IPMI-capable controllers have > >to sit down and verify all possible combinations. > > I have a spare machine Sun Fire X2100 M2 with 5715C: > > bge0@pci0:6:4:0: class=0x020000 card=0x534c108e chip=0x167814e4 > rev=0xa3 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM5715C 10/100/100 PCIe Ethernet Controller' > class = network > subclass = ethernet > bge1@pci0:6:4:1: class=0x020000 card=0x534c108e chip=0x167814e4 > rev=0xa3 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM5715C 10/100/100 PCIe Ethernet Controller' > class = network > subclass = ethernet > > I can provide you full access to this machine (if you want) or let me > know, what version I should check. Older versions (6.x - 8.3) are > working fine with hw.bge.allow_asf="1" in loader.conf. I didn't test > newer releases on these old machines. The reporter said the machine was Sun Fire X2200 M2 so I guess you may see the same issue on both stable/9 and stable/8. Ideally the loader tunable hw.bge.allow_asf should not be there and driver should take care of it by checking the existence of ASF/IPMI firmware. Can you setup a remote debugging environments(+ IPMI access) like the following URL? http://people.freebsd.org/~yongari/remote_debugging.txt > > Miroslav Lachman From owner-freebsd-net@FreeBSD.ORG Thu Feb 28 11:37:11 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 46AA9F7C for ; Thu, 28 Feb 2013 11:37:11 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 019AB1C63 for ; Thu, 28 Feb 2013 11:37:10 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 7366928433; Thu, 28 Feb 2013 12:37:03 +0100 (CET) Received: from [192.168.1.2] (unknown [89.177.49.69]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 1E8FF28429; Thu, 28 Feb 2013 12:37:02 +0100 (CET) Message-ID: <512F415F.3040807@quip.cz> Date: Thu, 28 Feb 2013 12:37:03 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: pyunyh@gmail.com Subject: Re: FreeBSD 9.1-RELEASE + bge0 == watchdog timeout References: <201302241106.42477.vegeta@tuxpowered.net> <20130225082042.GB1426@michelle.cdnetworks.com> <512CF97B.8030805@norma.perm.ru> <20130227020123.GA3581@michelle.cdnetworks.com> <512DE968.4020409@quip.cz> <20130228053558.GA1474@michelle.cdnetworks.com> In-Reply-To: <20130228053558.GA1474@michelle.cdnetworks.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 28 Feb 2013 11:37:11 -0000 YongHyeon PYUN wrote: > On Wed, Feb 27, 2013 at 12:09:28PM +0100, Miroslav Lachman wrote: [...] >> I can provide you full access to this machine (if you want) or let me >> know, what version I should check. Older versions (6.x - 8.3) are >> working fine with hw.bge.allow_asf="1" in loader.conf. I didn't test >> newer releases on these old machines. > > The reporter said the machine was Sun Fire X2200 M2 so I guess you > may see the same issue on both stable/9 and stable/8. Ideally the > loader tunable hw.bge.allow_asf should not be there and driver > should take care of it by checking the existence of ASF/IPMI > firmware. > > Can you setup a remote debugging environments(+ IPMI access) like > the following URL? > http://people.freebsd.org/~yongari/remote_debugging.txt The one Sun Fire X2100 M2 is idling in datacenter and connected to internet, so I can remotely reinstall it to stable/9 withing day or two and give you full access to it (ssh user, root, BMC / IPMI admin account with remote KVM + remote media). But as I understand, you need another machine connected to it with serial and another ethernet. It will take me some more time, as I will need to go to the datacenter, find some serial cable etc. Let me know if ssh + ipmi access to X2100 alone is useful for you to start, or only full remote debugging setup is needed. Can you point me to the original problem report with X2200 M2? Miroslav Lachman From owner-freebsd-net@FreeBSD.ORG Thu Feb 28 17:10:01 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 651A9D4A for ; Thu, 28 Feb 2013 17:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 3CE0C286 for ; Thu, 28 Feb 2013 17:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1SHA12L011751 for ; Thu, 28 Feb 2013 17:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1SHA1pF011750; Thu, 28 Feb 2013 17:10:01 GMT (envelope-from gnats) Date: Thu, 28 Feb 2013 17:10:01 GMT Message-Id: <201302281710.r1SHA1pF011750@freefall.freebsd.org> To: freebsd-net@FreeBSD.org Cc: From: John Baldwin Subject: Re: kern/176446: [netinet] [patch] Concurrency in ixgbe driving out-of-order packet process and spurious RST X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: John Baldwin List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 17:10:01 -0000 The following reply was made to PR kern/176446; it has been noted by GNATS. From: John Baldwin To: bug-followup@freebsd.org, jcharbon@verisign.com Cc: Subject: Re: kern/176446: [netinet] [patch] Concurrency in ixgbe driving out-of-order packet process and spurious RST Date: Thu, 28 Feb 2013 10:57:24 -0500 Can you try the fixes from http://svnweb.freebsd.org/base?view=revision&revision=240968? -- John Baldwin From owner-freebsd-net@FreeBSD.ORG Thu Feb 28 19:10:36 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 385A817C for ; Thu, 28 Feb 2013 19:10:36 +0000 (UTC) (envelope-from emaste@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 27CB1D38 for ; Thu, 28 Feb 2013 19:10:36 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1SJAaeh038529 for ; Thu, 28 Feb 2013 19:10:36 GMT (envelope-from emaste@freebsd.org) Received: (from emaste@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1SJAZPe038528 for freebsd-net@freebsd.org; Thu, 28 Feb 2013 19:10:35 GMT (envelope-from emaste@freebsd.org) X-Authentication-Warning: freefall.freebsd.org: emaste set sender to emaste@freebsd.org using -f Date: Thu, 28 Feb 2013 19:10:35 +0000 From: Ed Maste To: freebsd-net@freebsd.org Subject: [PATCH] Handle PACKET_TAG_IPFORWARD and TIMEWAIT state Message-ID: <20130228191035.GA36576@sandvine.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 28 Feb 2013 19:10:36 -0000 --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline SVN rev 244157 introduced a fix for a crash in tcp_input() which would occur in the case of a packet with a PACKET_TAG_IPFORWARD m_tag arriving for a flow in TIMEWAIT. Such packets resulted in a goto findpcb an a double free of the m_tag. Unfortunately the fix causes the fwd_tag to be lost for any subsequent trips through the pcb lookup code. The attached patch keeps the fwd_tag around until finished with pcb lookup. The #ifdef INET / INET6 is a bit torturous, but no worse than what was there. --VbJkn9YxBvnuCH5J Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="fwd_tag_findpcb.diff" Index: tcp_input.c =================================================================== --- tcp_input.c (revision 247398) +++ tcp_input.c (working copy) @@ -768,6 +768,28 @@ } else ti_locked = TI_UNLOCKED; + /* + * Grab info from PACKET_TAG_IPFORWARD tag prepended to the chain. + */ +#ifdef INET6 + if (isipv6 && (m->m_flags & M_IP6_NEXTHOP)) { + m->m_flags &= ~M_IP6_NEXTHOP; + fwd_tag = m_tag_find(m, PACKET_TAG_IPFORWARD, NULL); + m_tag_unlink(m, fwd_tag); + } +#ifdef INET + else if (!isipv6 && (m->m_flags & M_IP_NEXTHOP)) { +#endif +#elif defined(INET) + if (m->m_flags & M_IP_NEXTHOP) { +#endif +#if defined(INET) + m->m_flags &= ~M_IP_NEXTHOP; + fwd_tag = m_tag_find(m, PACKET_TAG_IPFORWARD, NULL); + m_tag_unlink(m, fwd_tag); + } +#endif + findpcb: #ifdef INVARIANTS if (ti_locked == TI_WLOCKED) { @@ -777,23 +799,7 @@ } #endif - /* - * Grab info from PACKET_TAG_IPFORWARD tag prepended to the chain. - */ - if ( #ifdef INET6 - (isipv6 && (m->m_flags & M_IP6_NEXTHOP)) -#ifdef INET - || (!isipv6 && (m->m_flags & M_IP_NEXTHOP)) -#endif -#endif -#if defined(INET) && !defined(INET6) - (m->m_flags & M_IP_NEXTHOP) -#endif - ) - fwd_tag = m_tag_find(m, PACKET_TAG_IPFORWARD, NULL); - -#ifdef INET6 if (isipv6 && fwd_tag != NULL) { struct sockaddr_in6 *next_hop6; @@ -817,10 +823,6 @@ th->th_dport, INPLOOKUP_WILDCARD | INPLOOKUP_WLOCKPCB, m->m_pkthdr.rcvif); } - /* Remove the tag from the packet. We don't need it anymore. */ - m_tag_delete(m, fwd_tag); - m->m_flags &= ~M_IP6_NEXTHOP; - fwd_tag = NULL; } else if (isipv6) { inp = in6_pcblookup_mbuf(&V_tcbinfo, &ip6->ip6_src, th->th_sport, &ip6->ip6_dst, th->th_dport, @@ -855,10 +857,6 @@ th->th_dport, INPLOOKUP_WILDCARD | INPLOOKUP_WLOCKPCB, m->m_pkthdr.rcvif); } - /* Remove the tag from the packet. We don't need it anymore. */ - m_tag_delete(m, fwd_tag); - m->m_flags &= ~M_IP_NEXTHOP; - fwd_tag = NULL; } else inp = in_pcblookup_mbuf(&V_tcbinfo, ip->ip_src, th->th_sport, ip->ip_dst, th->th_dport, @@ -970,6 +968,8 @@ if (tcp_twcheck(inp, &to, th, m, tlen)) goto findpcb; INP_INFO_WUNLOCK(&V_tcbinfo); + if (fwd_tag != NULL) + m_tag_free(fwd_tag); return; } /* @@ -1020,6 +1020,10 @@ } INP_INFO_WLOCK_ASSERT(&V_tcbinfo); } + if (fwd_tag) { + m_tag_free(fwd_tag); + fwd_tag = NULL; + } #ifdef MAC INP_WLOCK_ASSERT(inp); @@ -1429,6 +1433,8 @@ drop: INP_INFO_UNLOCK_ASSERT(&V_tcbinfo); + if (fwd_tag != NULL) + m_tag_free(fwd_tag); if (s != NULL) free(s, M_TCPLOG); if (m != NULL) --VbJkn9YxBvnuCH5J-- From owner-freebsd-net@FreeBSD.ORG Thu Feb 28 19:20:01 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EF372349 for ; Thu, 28 Feb 2013 19:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id D0AA3DA1 for ; Thu, 28 Feb 2013 19:20:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1SJK1dm040991 for ; Thu, 28 Feb 2013 19:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1SJK1FU040990; Thu, 28 Feb 2013 19:20:01 GMT (envelope-from gnats) Date: Thu, 28 Feb 2013 19:20:01 GMT Message-Id: <201302281920.r1SJK1FU040990@freefall.freebsd.org> To: freebsd-net@FreeBSD.org Cc: From: "Charbon, Julien" Subject: Re: kern/176446: [netinet] [patch] Concurrency in ixgbe driving out-of-order packet process and spurious RST X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: "Charbon, Julien" List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 19:20:02 -0000 The following reply was made to PR kern/176446; it has been noted by GNATS. From: "Charbon, Julien" To: John Baldwin Cc: bug-followup@freebsd.org, "De La Gueronniere, Marc" , jfv@freebsd.org Subject: Re: kern/176446: [netinet] [patch] Concurrency in ixgbe driving out-of-order packet process and spurious RST Date: Thu, 28 Feb 2013 20:10:39 +0100 On 2/28/13 4:57 PM, John Baldwin wrote: > Can you try the fixes from http://svnweb.freebsd.org/base?view=revision&revision=240968? Actually, Marc (I CC'ed him) did find the r240968 fix for concurrency between ixgbe_msix_que() and ixgbe_handle_que(), and made a backport for release-8.3.0 (see patch [1] below). However, the issue was still reproducible, then Marc found another place for concurrency from ixgbe_local_timer() and fix it (see patch [2]). But it was still not enough, and he found a last place for concurrency due to ixgbe_rearm_queues() call (see patch [3]). We all these patches applied, we were not able to reproduce this issue. If patch [1] and [2] seems clearly legitimates, patch [3] would need more discussions/feedback I guess. -- Julien [1] Patch ixgbe (1/3): Backport r240968 in release-8.3.0 Index: sys/dev/ixgbe/ixgbe.c =================================================================== --- sys/dev/ixgbe/ixgbe.c +++ sys/dev/ixgbe/ixgbe.c @@ -102,13 +102,15 @@ static int ixgbe_attach(device_t); static int ixgbe_detach(device_t); static int ixgbe_shutdown(device_t); -static void ixgbe_start(struct ifnet *); -static void ixgbe_start_locked(struct tx_ring *, struct ifnet *); #if __FreeBSD_version >= 800000 static int ixgbe_mq_start(struct ifnet *, struct mbuf *); static int ixgbe_mq_start_locked(struct ifnet *, struct tx_ring *, struct mbuf *); static void ixgbe_qflush(struct ifnet *); +static void ixgbe_deferred_mq_start(void *, int); +#else +static void ixgbe_start(struct ifnet *); +static void ixgbe_start_locked(struct tx_ring *, struct ifnet *); #endif static int ixgbe_ioctl(struct ifnet *, u_long, caddr_t); static void ixgbe_init(void *); @@ -645,6 +647,7 @@ { struct adapter *adapter = device_get_softc(dev); struct ix_queue *que = adapter->queues; + struct tx_ring *txr = adapter->tx_rings; u32 ctrl_ext; INIT_DEBUGOUT("ixgbe_detach: begin"); @@ -659,8 +662,11 @@ ixgbe_stop(adapter); IXGBE_CORE_UNLOCK(adapter); - for (int i = 0; i < adapter->num_tx_queues; i++, que++) { + for (int i = 0; i < adapter->num_tx_queues; i++, que++, txr++) { if (que->tq) { +#if __FreeBSD_version >= 800000 + taskqueue_drain(que->tq, &txr->txq_task); +#endif taskqueue_drain(que->tq, &que->que_task); taskqueue_free(que->tq); } @@ -722,6 +728,7 @@ } +#if __FreeBSD_version < 800000 /********************************************************************* * Transmit entry point * @@ -793,7 +800,7 @@ return; } -#if __FreeBSD_version >= 800000 +#else /* ** Multiqueue Transmit driver ** @@ -821,7 +828,7 @@ IXGBE_TX_UNLOCK(txr); } else { err = drbr_enqueue(ifp, txr->br, m); - taskqueue_enqueue(que->tq, &que->que_task); + taskqueue_enqueue(que->tq, &txr->txq_task); } return (err); @@ -887,6 +894,22 @@ } /* + * Called from a taskqueue to drain queued transmit packets. + */ +static void +ixgbe_deferred_mq_start(void *arg, int pending) +{ + struct tx_ring *txr = arg; + struct adapter *adapter = txr->adapter; + struct ifnet *ifp = adapter->ifp; + + IXGBE_TX_LOCK(txr); + if (!drbr_empty(ifp, txr->br)) + ixgbe_mq_start_locked(ifp, txr, NULL); + IXGBE_TX_UNLOCK(txr); +} + +/* ** Flush all ring buffers */ static void @@ -2210,6 +2233,9 @@ { device_t dev = adapter->dev; struct ix_queue *que = adapter->queues; +#if __FreeBSD_version >= 800000 + struct tx_ring *txr = adapter->tx_rings; +#endif int error, rid = 0; /* MSI RID at 1 */ @@ -2229,6 +2255,9 @@ * Try allocating a fast interrupt and the associated deferred * processing contexts. */ +#if __FreeBSD_version >= 800000 + TASK_INIT(&txr->txq_task, 0, ixgbe_deferred_mq_start, txr); +#endif TASK_INIT(&que->que_task, 0, ixgbe_handle_que, que); que->tq = taskqueue_create_fast("ixgbe_que", M_NOWAIT, taskqueue_thread_enqueue, &que->tq); @@ -2275,9 +2304,10 @@ { device_t dev = adapter->dev; struct ix_queue *que = adapter->queues; + struct tx_ring *txr = adapter->tx_rings; int error, rid, vector = 0; - for (int i = 0; i < adapter->num_tx_queues; i++, vector++, que++) { + for (int i = 0; i < adapter->num_tx_queues; i++, vector++, que++, txr++) { rid = vector + 1; que->res = bus_alloc_resource_any(dev, SYS_RES_IRQ, &rid, RF_SHAREABLE | RF_ACTIVE); @@ -2307,6 +2337,9 @@ if (adapter->num_tx_queues > 1) bus_bind_intr(dev, que->res, i); +#if __FreeBSD_version >= 800000 + TASK_INIT(&txr->txq_task, 0, ixgbe_deferred_mq_start, txr); +#endif TASK_INIT(&que->que_task, 0, ixgbe_handle_que, que); que->tq = taskqueue_create_fast("ixgbe_que", M_NOWAIT, taskqueue_thread_enqueue, &que->tq); @@ -2555,12 +2588,13 @@ ifp->if_softc = adapter; ifp->if_flags = IFF_BROADCAST | IFF_SIMPLEX | IFF_MULTICAST; ifp->if_ioctl = ixgbe_ioctl; - ifp->if_start = ixgbe_start; #if __FreeBSD_version >= 800000 ifp->if_transmit = ixgbe_mq_start; ifp->if_qflush = ixgbe_qflush; +#else + ifp->if_start = ixgbe_start; + IFQ_SET_MAXLEN(&ifp->if_snd, adapter->num_tx_desc - 2); #endif - ifp->if_snd.ifq_maxlen = adapter->num_tx_desc - 2; ether_ifattach(ifp, adapter->hw.mac.addr); Index: sys/dev/ixgbe/ixgbe.h =================================================================== --- sys/dev/ixgbe/ixgbe.h +++ sys/dev/ixgbe/ixgbe.h @@ -298,6 +298,7 @@ char mtx_name[16]; #if __FreeBSD_version >= 800000 struct buf_ring *br; + struct task txq_task; #endif #ifdef IXGBE_FDIR u16 atr_sample; [2] Patch ixgbe (2/3): Do not schedule ixgbe_handle_que() from ixgbe_local_timer(). Index: sys/dev/ixgbe/ixgbe.c =================================================================== --- sys/dev/ixgbe/ixgbe.c +++ sys/dev/ixgbe/ixgbe.c @@ -2033,7 +2033,7 @@ if (txr->queue_status & IXGBE_QUEUE_DEPLETED) ++busy; if ((txr->queue_status & IXGBE_QUEUE_IDLE) == 0) - taskqueue_enqueue(que->tq, &que->que_task); + taskqueue_enqueue(que->tq, &txr->txq_task); } /* Only truely watchdog if all queues show hung */ if (hung == adapter->num_tx_queues) [3] Patch ixgbe (3/3): ixgbe_rearm_queues() directly schedules an interruption and drives not wanted concurrency, should we called it at all? Index: sys/dev/ixgbe/ixgbe.c =================================================================== --- sys/dev/ixgbe/ixgbe.c +++ sys/dev/ixgbe/ixgbe.c @@ -2046,7 +2046,7 @@ ifp->if_drv_flags &= ~IFF_DRV_OACTIVE; out: - ixgbe_rearm_queues(adapter, adapter->que_mask); + // ixgbe_rearm_queues(adapter, adapter->que_mask); callout_reset(&adapter->timer, hz, ixgbe_local_timer, adapter); return; @@ -4674,7 +4674,7 @@ ** Schedule another interrupt if so. */ if ((staterr & IXGBE_RXD_STAT_DD) != 0) { - ixgbe_rearm_queues(adapter, (u64)(1 << que->msix)); + // ixgbe_rearm_queues(adapter, (u64)(1 << que->msix)); return (TRUE); } From owner-freebsd-net@FreeBSD.ORG Thu Feb 28 21:06:22 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 33D259C4 for ; Thu, 28 Feb 2013 21:06:22 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by mx1.freebsd.org (Postfix) with ESMTP id D25E4214 for ; Thu, 28 Feb 2013 21:06:21 +0000 (UTC) Received: by mail-ob0-f172.google.com with SMTP id tb18so545178obb.31 for ; Thu, 28 Feb 2013 13:06:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=QAzyMlvWs1ksnjlCqinvkpHjPiyTZMmbtItZl3/2Nd8=; b=pgGk0dEUtKupJ4YSJaeYse/1ocLcrqvOsXMYQbUFCABMm2pndCpYBS76hVDnVMadlj ej9LNbRMfjIMY7HCv/6TKqp4RA+B0cLlDzYCmpaoz2/7sOKJ1BwxCkcMw2ARJuTQAtPw qYrnIlya4r7oVncg5DzRPV2Tzf96GlHUpaMumeM+fIyhN+gDAC1ygSV47qkvhAFVRg34 //P04LkYVBBoZHqh7kttVswELM3bTEkWIwxCu3rKA/5kxwNPAJwR6pVqyskCMGQMr8CT Qj4V2q7+K1hs6dAVkzrSW65mxdNopaF+nVM/H45I3ubR670TLexgDc4Kpjk22JctnUl3 rKEA== MIME-Version: 1.0 X-Received: by 10.60.170.20 with SMTP id ai20mr6981817oec.33.1362085581347; Thu, 28 Feb 2013 13:06:21 -0800 (PST) Sender: carpeddiem@gmail.com Received: by 10.60.150.239 with HTTP; Thu, 28 Feb 2013 13:06:21 -0800 (PST) In-Reply-To: <20130228191035.GA36576@sandvine.com> References: <20130228191035.GA36576@sandvine.com> Date: Thu, 28 Feb 2013 16:06:21 -0500 X-Google-Sender-Auth: xzo9jXk2tT7XLayWbwX7vHvIHDU Message-ID: Subject: Re: [PATCH] Handle PACKET_TAG_IPFORWARD and TIMEWAIT state From: Ed Maste To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 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, 28 Feb 2013 21:06:22 -0000 On 28 February 2013 14:10, Ed Maste wrote: > The attached patch keeps the fwd_tag > around until finished with pcb lookup. There's a small bug in that patch - a corrected version, which handles a NULL return from m_tag_find, can be found at: http://people.freebsd.org/~emaste/patches/fwd_tag_findpcb.diff From owner-freebsd-net@FreeBSD.ORG Fri Mar 1 06:59:21 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E3C813CB; Fri, 1 Mar 2013 06:59:21 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id A4A13BDC; Fri, 1 Mar 2013 06:59:21 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r216xLGF075785; Fri, 1 Mar 2013 06:59:21 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r216xLwA075781; Fri, 1 Mar 2013 06:59:21 GMT (envelope-from linimon) Date: Fri, 1 Mar 2013 06:59:21 GMT Message-Id: <201303010659.r216xLwA075781@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/176510: [udp] [panic] Kernel Panic in udp_input @ offset 0x475 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2013 06:59:22 -0000 Old Synopsis: Kernel Panic in udp_input @ offset 0x475 New Synopsis: [udp] [panic] Kernel Panic in udp_input @ offset 0x475 Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Mar 1 06:59:04 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=176510 From owner-freebsd-net@FreeBSD.ORG Fri Mar 1 13:38:03 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9E252B85 for ; Fri, 1 Mar 2013 13:38:03 +0000 (UTC) (envelope-from VenkatKumar.Duvvuru@Emulex.Com) Received: from CMEXEDGE1.ext.emulex.com (cmexedge1.ext.emulex.com [138.239.224.99]) by mx1.freebsd.org (Postfix) with ESMTP id 721AFDF4 for ; Fri, 1 Mar 2013 13:38:03 +0000 (UTC) Received: from CMEXHTCAS2.ad.emulex.com (138.239.115.218) by CMEXEDGE1.ext.emulex.com (138.239.224.99) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 1 Mar 2013 05:38:07 -0800 Received: from CMEXMB1.ad.emulex.com ([169.254.1.137]) by CMEXHTCAS2.ad.emulex.com ([2002:8aef:73da::8aef:73da]) with mapi id 14.02.0318.004; Fri, 1 Mar 2013 05:36:52 -0800 From: "Duvvuru,Venkat Kumar" To: Josh Paetzel Subject: RE: OCE driver patches Thread-Topic: OCE driver patches Thread-Index: Ac4FKZvQ2m3Cu1QRR3u/QVUeigTouwB8AcmAA9n7JiA= Date: Fri, 1 Mar 2013 13:36:52 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [138.239.140.189] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2013 13:38:03 -0000 Hi Josh, I have a bunch of patches (~25 in number) to submit. Please let me know the= process to submit them. Do I just attach them in a single email or open pr's for each of them?? Pls suggest. /Venkat -----Original Message----- From: Josh Paetzel [mailto:josh@tcbug.org]=20 Sent: Saturday, February 09, 2013 8:33 PM To: Duvvuru,Venkat Kumar Cc: freebsd-net@freebsd.org Subject: Re: OCE driver patches Vencat, There's been a breakdown in communication. I've been working on oce with Ad= am and have a bunch of oce hardware. Please cc me on any patches you have. = (pr's are fine, but they won't get my attention) Thanks, Josh Paetzel On Feb 7, 2013, at 3:57 AM, "Duvvuru,Venkat Kumar" wrote: > Hi, > I have submitted this patch http://www.freebsd.org/cgi/query-pr.cgi?pr= =3D171838 some time back. Could you please let me know when this will be pu= lled in? > I have some more patches to submit. Please let me know if submitting it o= nline at this link http://www.freebsd.org/send-pr.html is the only way to g= et them in or is there an alternative to the patch submission? >=20 > Thanks, > Venkat >=20 > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Fri Mar 1 14:38:25 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 03CAFBF0 for ; Fri, 1 Mar 2013 14:38:25 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id CF90CFC for ; Fri, 1 Mar 2013 14:38:24 +0000 (UTC) Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id F09352079F; Fri, 1 Mar 2013 09:38:23 -0500 (EST) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute5.internal (MEProxy); Fri, 01 Mar 2013 09:38:23 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=references:mime-version:in-reply-to :content-type:content-transfer-encoding:message-id:cc:from :subject:date:to; s=smtpout; bh=N8AmOjb2Jdl2o9Qy+kMic/6LwMI=; b= RSKb1cUWJevzLNTM3idzhxmsm7XClFSTfQQ3jJZ5h9lbgLhfBTwmKG9mjddsCQW8 SJWztel0LSOlUUDOW++SWF2DcV91jUrFIXjj/foF2I4ZVetme64SAVMyyjUdI+FS M50nrTKDYWECe/dbQeXtds6hdOIHglHx3CeRN/RNsIU= X-Sasl-enc: 32ee7DuKugNyzOObqo2yAC+RpHd/Oe27U5o/KFeY0R4q 1362148702 Received: from [10.168.164.122] (unknown [166.137.187.187]) by mail.messagingengine.com (Postfix) with ESMTPA id DE33EC80E8B; Fri, 1 Mar 2013 09:38:22 -0500 (EST) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPhone Mail (10B146) From: Josh Paetzel Subject: Re: OCE driver patches Date: Fri, 1 Mar 2013 06:38:18 -0800 To: "Duvvuru,Venkat Kumar" Cc: "freebsd-net@freebsd.org" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2013 14:38:25 -0000 On Mar 1, 2013, at 5:36 AM, "Duvvuru,Venkat Kumar" wrote: > Hi Josh, > I have a bunch of patches (~25 in number) to submit. Please let me know th= e process to submit them. > Do I just attach them in a single email or open pr's for each of them?? > Pls suggest. >=20 > /Venkat >=20 Venkat, I think it depends on how you want them committed to FreeBSD.=20 If the patches are atomic changes that should be kept atomic in the FreeBSD s= ource tree then I'll commit them seperately. This is a tad time consuming as= I test them atomically before committing them. If they can be committed in= one go then I can just apply them all, test the end result, and commit that= . One PR with the patches attached and a note saying these can all go in in on= e go is appropriate in the latter case, the former would be best served by s= eperate PRs. Thanks, Josh Paetzel= From owner-freebsd-net@FreeBSD.ORG Fri Mar 1 15:55:27 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx2.freebsd.org (mx2.FreeBSD.org [8.8.178.116]) by hub.freebsd.org (Postfix) with ESMTP id 6FA927E5; Fri, 1 Mar 2013 15:55:27 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from butcher-nb.yandex.net (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) by mx2.freebsd.org (Postfix) with ESMTP id B6C4A2977; Fri, 1 Mar 2013 15:55:26 +0000 (UTC) Message-ID: <5130CF14.4090606@FreeBSD.org> Date: Fri, 01 Mar 2013 19:53:56 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Ed Maste Subject: Re: [PATCH] Handle PACKET_TAG_IPFORWARD and TIMEWAIT state References: <20130228191035.GA36576@sandvine.com> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2013 15:55:27 -0000 On 01.03.2013 01:06, Ed Maste wrote: > On 28 February 2013 14:10, Ed Maste wrote: >> The attached patch keeps the fwd_tag >> around until finished with pcb lookup. > > There's a small bug in that patch - a corrected version, which handles > a NULL return from m_tag_find, can be found at: > http://people.freebsd.org/~emaste/patches/fwd_tag_findpcb.diff Hi Ed, it seems this problem was there before my breakage. Also, it think that m_tag_unlink is redundant here, because you clear the M_IP_NEXTHOP/M_IP6_NEXTHOP flag. -- WBR, Andrey V. Elsukov From owner-freebsd-net@FreeBSD.ORG Fri Mar 1 16:04:10 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E32989FD for ; Fri, 1 Mar 2013 16:04:10 +0000 (UTC) (envelope-from ncrogers@gmail.com) Received: from mail-vc0-f180.google.com (mail-vc0-f180.google.com [209.85.220.180]) by mx1.freebsd.org (Postfix) with ESMTP id 7BF6B726 for ; Fri, 1 Mar 2013 16:04:10 +0000 (UTC) Received: by mail-vc0-f180.google.com with SMTP id fo13so2038805vcb.39 for ; Fri, 01 Mar 2013 08:04:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=HLtbcI2TMYPT25tfTxFO2LpDgBj5+bWNzhjTNpqv/aI=; b=I0MOk3Obh0oURq0FtcurjQ81KQlYnXMNszxzsJ6gnJssNFu6UaRCX1JyPFe09Czufm jqEMO/EsmXmQIRBv+OOmeo2fzoz4JjWgjHYuXiZBCiT/FWgUkboA/+o9/1xyaWFiNm+0 VSC0JqcHGirWZaXPgN4kaJKDNTcFWazH35lAsbWADgYT7OU69KwjzSElXe17WcJfsM6p 6uEtbf4UxRMSl0KTapz5gevvR+B9mVrWMn2Bv/owt9xXmKrb5Nyofrayhbxd9hBFae8r TIOgVKcNmMgqbG8mVdksa7qzuhDC9yCTl+gK7AO1MZd26G4OZ/r/U9CUrt8UgaOVdC8R ijGA== MIME-Version: 1.0 X-Received: by 10.58.188.48 with SMTP id fx16mr4320756vec.22.1362153849662; Fri, 01 Mar 2013 08:04:09 -0800 (PST) Received: by 10.52.176.131 with HTTP; Fri, 1 Mar 2013 08:04:09 -0800 (PST) In-Reply-To: References: <512BAA60.3060703@biostat.wisc.edu> <512BAF8D.7080308@biostat.wisc.edu> Date: Fri, 1 Mar 2013 08:04:09 -0800 Message-ID: Subject: Re: igb network lockups From: Nick Rogers To: Jack Vogel Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org, "Christopher D. Harrison" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2013 16:04:10 -0000 FWIW I have been experiencing a similar issue on a number of systems using the em(4) driver under 9.1-RELEASE. This is after upgrading from a snapshot of 8.3-STABLE. My systems use PF+ALTQ as well. The symptoms are: interface stops passing traffic until the system is rebooted. I have not yet been able to gain access to the systems to dig around (after they have crashed), however my kernel/network settings are properly tuned (high mbuf limit, hw.em.rxd/txd=4096, etc). It seems to happen about once a day on systems with around a sustained 50Mb/s of traffic. I realize this is not much to go on but perhaps it helps. I am debating trying the e1000 driver in the latest CURRENT on top of 9.1-RELEASE. I noticed the Intel shared code was updated about a week ago. Would this change or perhaps another change to e1000 since 9.1-RELEASE possibly affect stability in a positive way? Thanks. On Mon, Feb 25, 2013 at 10:45 AM, Jack Vogel wrote: > Have you done any poking around, looking at stats to determine why the > hangs? For instance, > might your mbuf pool be depleted? Some other network resource perhaps? > > Jack > > > On Mon, Feb 25, 2013 at 10:38 AM, Christopher D. Harrison < > harrison@biostat.wisc.edu> wrote: > >> Sure, >> The problem appears on both systems running with ALTQ and vanilla. >> -C >> >> On 02/25/13 12:29, Jack Vogel wrote: >> >> I've not heard of this problem, but I think most users do not use ALTQ, >> and we (Intel) do not >> test using it. Can it be eliminated from the equation? >> >> Jack >> >> >> On Mon, Feb 25, 2013 at 10:16 AM, Christopher D. Harrison < >> harrison@biostat.wisc.edu> wrote: >> >>> I recently have been experiencing network "freezes" and network "lockups" >>> on our Freebsd 9.1 systems which are running zfs and nfs file servers. >>> I upgraded from 9.0 to 9.1 about 2 months ago and we have been having >>> issues with almost bi-monthly. The issue manifests in the system becomes >>> unresponsive to any/all nfs clients. The system is not resource bound as >>> our I/O is low to disk and our network is usually in the 20mbit/40mbit >>> range. We do notice a correlation between temporary i/o spikes and >>> network freezes but not enough to send our system in to "lockup" mode for >>> the next 5min. Currently we have 4 igb nics in 2 aggr's with 8 queue's >>> per nic and our dev.igb reports: >>> >>> dev.igb.3.%desc: Intel(R) PRO/1000 Network Connection version - 2.3.4 >>> >>> I am almost certain the problem is with the ibg driver as a friend is >>> also experiencing the same problem with the same intel igb nic. He has >>> addressed the issue by restarting the network using netif on his systems. >>> According to my friend, once the network interfaces get cleared, everything >>> comes back and starts working as expected. >>> >>> I have noticed an issue with the igb driver and I was looking for >>> thoughts on how to help address this problem. >>> >>> http://freebsd.1045724.n5.nabble.com/em-igb-if-transmit-drbr-and-ALTQ-td5760338.html >>> >>> Thoughts/Ideas are greatly appreciated!!! >>> >>> -C >>> >>> _______________________________________________ >>> freebsd-net@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >>> >> >> >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Fri Mar 1 16:18:41 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EEF43FA0 for ; Fri, 1 Mar 2013 16:18:41 +0000 (UTC) (envelope-from ncrogers@gmail.com) Received: from mail-ve0-f182.google.com (mail-ve0-f182.google.com [209.85.128.182]) by mx1.freebsd.org (Postfix) with ESMTP id AA53F7E5 for ; Fri, 1 Mar 2013 16:18:41 +0000 (UTC) Received: by mail-ve0-f182.google.com with SMTP id ox1so3062005veb.13 for ; Fri, 01 Mar 2013 08:18:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=7LmYd61o1y2dsHNLzuR0TXgbRFWXlS7FVGrTgYFeLmw=; b=o8b6GZE789nWXaOvNgA8k3lMiapSdDLMPSikFPrE3T5ZsY7FNkOvJ9ypQysA3zCE6J qVGoIkwFVXD7SeihuY3yGoOmgF8zxMcxGbbHzayZtkRgAM6JDGfwuCImvl4xfTK68Xbv 0BThmi/ngA6NwNp8xhQhnoXUzq1t9ifEtWV7O29eoGKY0oUTJI63ZBJMVuwkg/L3T/lZ rDlgXxdzutf4Xyv8IQ+N7ji4XO1oas2b3eSUbR8A0SUJekreGiC4bUno4lMyFkJvxLvg tpgrJt5UvwqrnCtHBxL60Dv3Pye+ptNpXUkWYrNziRUrKRi8X7RAH8CL7BBPfrWD9STz pvww== MIME-Version: 1.0 X-Received: by 10.220.151.144 with SMTP id c16mr4216077vcw.18.1362154720931; Fri, 01 Mar 2013 08:18:40 -0800 (PST) Received: by 10.52.176.131 with HTTP; Fri, 1 Mar 2013 08:18:40 -0800 (PST) In-Reply-To: References: <512BAA60.3060703@biostat.wisc.edu> <512BAF8D.7080308@biostat.wisc.edu> Date: Fri, 1 Mar 2013 08:18:40 -0800 Message-ID: Subject: Re: igb network lockups From: Nick Rogers To: Jack Vogel Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org, "Christopher D. Harrison" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2013 16:18:42 -0000 On Fri, Mar 1, 2013 at 8:04 AM, Nick Rogers wrote: > FWIW I have been experiencing a similar issue on a number of systems > using the em(4) driver under 9.1-RELEASE. This is after upgrading from > a snapshot of 8.3-STABLE. My systems use PF+ALTQ as well. The symptoms > are: interface stops passing traffic until the system is rebooted. I > have not yet been able to gain access to the systems to dig around > (after they have crashed), however my kernel/network settings are > properly tuned (high mbuf limit, hw.em.rxd/txd=4096, etc). It seems to > happen about once a day on systems with around a sustained 50Mb/s of > traffic. > > I realize this is not much to go on but perhaps it helps. I am > debating trying the e1000 driver in the latest CURRENT on top of > 9.1-RELEASE. I noticed the Intel shared code was updated about a week > ago. Would this change or perhaps another change to e1000 since > 9.1-RELEASE possibly affect stability in a positive way? > > Thanks. Heres relevant pciconf output: em0@pci0:1:0:0: class=0x020000 card=0x10d315d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected em1@pci0:2:0:0: class=0x020000 card=0x10d315d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected em2@pci0:7:0:0: class=0x020000 card=0x10d315d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected em3@pci0:8:0:0: class=0x020000 card=0x10d315d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) cap 11[a0] = MSI-X supports 5 messages in map 0x1c enabled ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected > > On Mon, Feb 25, 2013 at 10:45 AM, Jack Vogel wrote: >> Have you done any poking around, looking at stats to determine why the >> hangs? For instance, >> might your mbuf pool be depleted? Some other network resource perhaps? >> >> Jack >> >> >> On Mon, Feb 25, 2013 at 10:38 AM, Christopher D. Harrison < >> harrison@biostat.wisc.edu> wrote: >> >>> Sure, >>> The problem appears on both systems running with ALTQ and vanilla. >>> -C >>> >>> On 02/25/13 12:29, Jack Vogel wrote: >>> >>> I've not heard of this problem, but I think most users do not use ALTQ, >>> and we (Intel) do not >>> test using it. Can it be eliminated from the equation? >>> >>> Jack >>> >>> >>> On Mon, Feb 25, 2013 at 10:16 AM, Christopher D. Harrison < >>> harrison@biostat.wisc.edu> wrote: >>> >>>> I recently have been experiencing network "freezes" and network "lockups" >>>> on our Freebsd 9.1 systems which are running zfs and nfs file servers. >>>> I upgraded from 9.0 to 9.1 about 2 months ago and we have been having >>>> issues with almost bi-monthly. The issue manifests in the system becomes >>>> unresponsive to any/all nfs clients. The system is not resource bound as >>>> our I/O is low to disk and our network is usually in the 20mbit/40mbit >>>> range. We do notice a correlation between temporary i/o spikes and >>>> network freezes but not enough to send our system in to "lockup" mode for >>>> the next 5min. Currently we have 4 igb nics in 2 aggr's with 8 queue's >>>> per nic and our dev.igb reports: >>>> >>>> dev.igb.3.%desc: Intel(R) PRO/1000 Network Connection version - 2.3.4 >>>> >>>> I am almost certain the problem is with the ibg driver as a friend is >>>> also experiencing the same problem with the same intel igb nic. He has >>>> addressed the issue by restarting the network using netif on his systems. >>>> According to my friend, once the network interfaces get cleared, everything >>>> comes back and starts working as expected. >>>> >>>> I have noticed an issue with the igb driver and I was looking for >>>> thoughts on how to help address this problem. >>>> >>>> http://freebsd.1045724.n5.nabble.com/em-igb-if-transmit-drbr-and-ALTQ-td5760338.html >>>> >>>> Thoughts/Ideas are greatly appreciated!!! >>>> >>>> -C >>>> >>>> _______________________________________________ >>>> freebsd-net@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >>>> >>> >>> >>> >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Fri Mar 1 16:24:03 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EAFC65A1; Fri, 1 Mar 2013 16:24:03 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by mx1.freebsd.org (Postfix) with ESMTP id AB3E3849; Fri, 1 Mar 2013 16:24:03 +0000 (UTC) Received: by mail-oa0-f45.google.com with SMTP id o6so6009234oag.18 for ; Fri, 01 Mar 2013 08:23:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=LuhCD7HqxDNqarnyXtQhqbXV4pJgB8+7YsDlQ3tRI4g=; b=yMK210W3SWJalcIT4mWlS1nTeVt51WAmGpXKzQ1cPBtf3Jf3nRZN7YYgW9iWVhzCPn vUW8RWdhSIJf8OqI3NETlu6tgWUH+fLRD/BG/b7J6H/20w97hDP4jnHzQxXaXA4qz0Cn xPXtFZyAAQNWUNGr3v/Ztto+uL/EmotcWnuwO7oz+QfYlu5LK7Izw0qsZQ7g20QnW/JA SEZrM1gvWPwF+SEdusJe4JSNDrLhe0MMk+B9WHH3SjC68Cb/L92QcIJG8AewinF2HEbi pSHM4lXwZ/UNicQp9h2GRh/O2qtcilwq+8Utf3vXMWggmQFU1KbyNTfGhdEUR5jF0NZY ENeA== MIME-Version: 1.0 X-Received: by 10.60.8.40 with SMTP id o8mr8862380oea.112.1362155037557; Fri, 01 Mar 2013 08:23:57 -0800 (PST) Sender: carpeddiem@gmail.com Received: by 10.60.150.239 with HTTP; Fri, 1 Mar 2013 08:23:57 -0800 (PST) In-Reply-To: <5130CF14.4090606@FreeBSD.org> References: <20130228191035.GA36576@sandvine.com> <5130CF14.4090606@FreeBSD.org> Date: Fri, 1 Mar 2013 11:23:57 -0500 X-Google-Sender-Auth: uwbSLfhQNwp3nv9c-8R-ptsP-cg Message-ID: Subject: Re: [PATCH] Handle PACKET_TAG_IPFORWARD and TIMEWAIT state From: Ed Maste To: "Andrey V. Elsukov" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Mar 2013 16:24:04 -0000 On 1 March 2013 10:53, Andrey V. Elsukov wrote: > On 01.03.2013 01:06, Ed Maste wrote: >> On 28 February 2013 14:10, Ed Maste wrote: >>> The attached patch keeps the fwd_tag >>> around until finished with pcb lookup. >> >> There's a small bug in that patch - a corrected version, which handles >> a NULL return from m_tag_find, can be found at: >> http://people.freebsd.org/~emaste/patches/fwd_tag_findpcb.diff > > Hi Ed, > > it seems this problem was there before my breakage. Yes, I had a chat with glebius@ about it, and it looks like this problem has existed for years. > Also, it think that m_tag_unlink is redundant here, because you clear > the M_IP_NEXTHOP/M_IP6_NEXTHOP flag. I split the old m_tag_delete into m_tag_unlink after finding the tag, and m_tag_free on the exit paths from the pcb lookup. I could leave it attached to the mbuf and m_tag_delete it in the cases I modified, although I don't think it makes much difference. From owner-freebsd-net@FreeBSD.ORG Sat Mar 2 01:31:28 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 660B03C6 for ; Sat, 2 Mar 2013 01:31:28 +0000 (UTC) (envelope-from prvs=1773e84f73=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 034A4135 for ; Sat, 2 Mar 2013 01:31:27 +0000 (UTC) Received: from r2d2 ([46.65.172.4]) by mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) (MDaemon PRO v10.0.4) with ESMTP id md50002474076.msg for ; Sat, 02 Mar 2013 01:31:21 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Sat, 02 Mar 2013 01:31:21 +0000 (not processed: message from valid local sender) X-MDDKIM-Result: neutral (mail1.multiplay.co.uk) X-MDRemoteIP: 46.65.172.4 X-Return-Path: prvs=1773e84f73=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-net@freebsd.org Message-ID: <23773B97555741F68384CD67B2123077@multiplay.co.uk> From: "Steven Hartland" To: Subject: Review of carp patch for stable Date: Sat, 2 Mar 2013 01:31:18 -0000 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_079B_01CE16E5.A326E480" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Mar 2013 01:31:28 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_079B_01CE16E5.A326E480 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit We've got a lovely shiny new carp thanks to glebius in head but unfortunately its not going to get MFC'ed so for the time being those users on -RELEASE / -STABLE need to use the current implementation which has a nasty issue where by it doesn't cleanup when IP's are removed hence gets into an invalid state. The code was there for address cleanup but was never being called because in_control was never calling ifp->if_ioctl in the SIOCDIFADDR case. Once I wired this up it uncovered a few more issues with carp_del_addr* methods, so I've patched those too. The call from in_control ignores EINVAL and ENOTTY (which seems like compat and appears to only be used in if_mxge) to try and ensure backwards compatibility, I could go further and ignore all error returns but I don't think that would be a good idea. Given this can't go into head first as carp has changed so much I'd like to get feedback to confirm it all looks good and isn't going to break the world. What do people think? Did I miss anything or is there a better way to do this that anyone knows of? I should mention Glebius has already looked at it and seemed to think it looked sane. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. ------=_NextPart_000_079B_01CE16E5.A326E480 Content-Type: application/octet-stream; name="carp-addr-del.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="carp-addr-del.patch" Fix carp not deleting addresses correctly, which breaks carp interfaces = setup using the rc.d/jail.=0A= --- sys/netinet/in.c.orig 2013-02-19 17:06:48.000000000 +0000=0A= +++ sys/netinet/in.c 2013-02-26 14:52:53.293628430 +0000=0A= @@ -583,6 +583,20 @@=0A= =0A= case SIOCDIFADDR:=0A= /*=0A= + * Carp and possibly others expect their if_ioctl handler=0A= + * called for SIOCDIFADDR=0A= + */=0A= + if (ifp->if_ioctl !=3D NULL) {=0A= + error =3D (*ifp->if_ioctl)(ifp, SIOCDIFADDR, (caddr_t)ia);=0A= + /*=0A= + * We ignore EINVAL and ENOTTY as this call is likely not=0A= + * supported by most drivers=0A= + */=0A= + if (error && error !=3D EINVAL && error !=3D ENOTTY)=0A= + goto out;=0A= + }=0A= +=0A= + /*=0A= * in_ifscrub kills the interface route.=0A= */=0A= in_ifscrub(ifp, ia, LLE_STATIC);=0A= --- sys/netinet/ip_carp.c.orig 2013-02-25 19:03:18.801241179 +0000=0A= +++ sys/netinet/ip_carp.c 2013-02-25 19:30:54.401573772 +0000=0A= @@ -1628,21 +1628,17 @@=0A= =0A= if (!--sc->sc_naddrs) {=0A= struct carp_if *cif =3D (struct carp_if *)sc->sc_carpdev->if_carp;=0A= - struct ip_moptions *imo =3D &sc->sc_imo;=0A= =0A= CARP_LOCK(cif);=0A= - callout_stop(&sc->sc_ad_tmo);=0A= - SC2IFP(sc)->if_flags &=3D ~IFF_UP;=0A= - SC2IFP(sc)->if_drv_flags &=3D ~IFF_DRV_RUNNING;=0A= - sc->sc_vhid =3D -1;=0A= - in_delmulti(imo->imo_membership[--imo->imo_num_memberships]);=0A= - imo->imo_multicast_ifp =3D NULL;=0A= - TAILQ_REMOVE(&cif->vhif_vrs, sc, sc_list);=0A= - if (!--cif->vhif_nvrs) {=0A= - sc->sc_carpdev->if_carp =3D NULL;=0A= - CARP_LOCK_DESTROY(cif);=0A= - free(cif, M_CARP);=0A= + if (cif->vhif_nvrs =3D=3D 1) {=0A= + /* Last address so detach */=0A= + carpdetach(sc, 1);=0A= } else {=0A= + /* Just the last IPv4 address */=0A= + callout_stop(&sc->sc_md_tmo);=0A= + carp_multicast_cleanup(sc, 1);=0A= + TAILQ_REMOVE(&cif->vhif_vrs, sc, sc_list);=0A= + cif->vhif_nvrs--;=0A= CARP_UNLOCK(cif);=0A= }=0A= }=0A= @@ -1836,18 +1831,17 @@=0A= struct carp_if *cif =3D (struct carp_if *)sc->sc_carpdev->if_carp;=0A= =0A= CARP_LOCK(cif);=0A= - callout_stop(&sc->sc_ad_tmo);=0A= - SC2IFP(sc)->if_flags &=3D ~IFF_UP;=0A= - SC2IFP(sc)->if_drv_flags &=3D ~IFF_DRV_RUNNING;=0A= - sc->sc_vhid =3D -1;=0A= - carp_multicast6_cleanup(sc, 1);=0A= - TAILQ_REMOVE(&cif->vhif_vrs, sc, sc_list);=0A= - if (!--cif->vhif_nvrs) {=0A= - CARP_LOCK_DESTROY(cif);=0A= - sc->sc_carpdev->if_carp =3D NULL;=0A= - free(cif, M_CARP);=0A= - } else=0A= + if (cif->vhif_nvrs =3D=3D 1) {=0A= + /* Last address so detach */=0A= + carpdetach(sc, 1);=0A= + } else {=0A= + /* Just the last IPv6 address */=0A= + callout_stop(&sc->sc_md6_tmo);=0A= + carp_multicast6_cleanup(sc, 1);=0A= + TAILQ_REMOVE(&cif->vhif_vrs, sc, sc_list);=0A= + cif->vhif_nvrs--;=0A= CARP_UNLOCK(cif);=0A= + }=0A= }=0A= =0A= return (error);=0A= ------=_NextPart_000_079B_01CE16E5.A326E480-- From owner-freebsd-net@FreeBSD.ORG Sat Mar 2 14:28:13 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2F70AD2E for ; Sat, 2 Mar 2013 14:28:13 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from nm21.bullet.mail.ne1.yahoo.com (nm21.bullet.mail.ne1.yahoo.com [98.138.90.84]) by mx1.freebsd.org (Postfix) with ESMTP id EB5E0DF4 for ; Sat, 2 Mar 2013 14:28:12 +0000 (UTC) Received: from [98.138.90.51] by nm21.bullet.mail.ne1.yahoo.com with NNFMP; 02 Mar 2013 14:24:55 -0000 Received: from [98.138.89.195] by tm4.bullet.mail.ne1.yahoo.com with NNFMP; 02 Mar 2013 14:24:55 -0000 Received: from [127.0.0.1] by omp1053.mail.ne1.yahoo.com with NNFMP; 02 Mar 2013 14:24:55 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 434675.77859.bm@omp1053.mail.ne1.yahoo.com Received: (qmail 55959 invoked by uid 60001); 2 Mar 2013 14:24:55 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1362234294; bh=z/yNbsIJnDO5uB4iQSPDjlJGVtWpfeghoM3k2/cWJWY=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=rpF1FaC1tc2NNdsZENdX6VSwCTZ1fGhoXQh4RUWa2Amit5foAAVdbLy1OUtwydwklDL+XPdcS6TgoBgWppaCWab8/iQ7Hu4mNtAIuPn1YbH066iJ06DN7tHWYyEk5Y2PjswKYB4lI/sD5fq05UoaolbJy4/HTMfQ6elzTECa7d0= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=v4E1PadyK8BLyW965uJgNReAhyBpRjJFeORMC3kZnMvPk3qYyHHCyMY/WFk/yTc1rqmK7ipNheGtYpBjDtx8XM+WdxpKjHhlzZyw37ndrbzTKB20Gs5I6osUw3bQpCShJkGGHo9N9apSe6eJlCitiRIIZVflvpUY2O1fX96y36U=; X-YMail-OSG: scGalDEVM1n8rjL_.RV4L9oDa3IlDLNTFeo5M2vc_Lg88w0 _0QvbujD0KoBX6c73EXH4QtavYDvLUA2jM6Sv_tp0otPOhy8qIdE41tsuO5c 2VxWapmCdmCJ.mFtwK3MACd0oonGhX7hyNfUnL4SRWNkNbxJVqL8uSYFYOJ0 kS4EYqTbFhlVQjHMnw_Sqvzl.CuxRMUfm56sEmWj0DFrlqeOHM7_r0f_QUN7 Ft7t9hKn36ilem_v_MiGwTbpUsPY8UNNgVe2fKbACtR2jyePCsZhZlgV4JUN COFsZQSr.QU1JkXdweQK4KUBDwosIASy2svHjB5EQ.jPFekBo2C5nD4WARmE 9BibtYJp86f30vWjj.DMBGsmh6xNEkjfdaUcVpGrZrg6UZBC9KBYcMELSMSd MgCdA321EZLMYcqomaApjPyQBIffIkAVfj33OxNINPumjEc.cnshZo9MtJxP 2s1emBTq6IHBZnzv8aiQ_St.XZVVRIwUgZSL48puZuzS_0k6MCF5FtMIMWNN rPaSSNkIHWo3m7b0syMF9IhEI99ULsE1T0T9FlNMKByiaAcuKn9UFPwHMASf t369ipyTtBCyxcS04C0vKrvIuaqujVayWEhzW6fzGP4VthYSXOTJj7.8MTOr cGT71Jr2Nhgo_py7qBc_fvM8DuMqfx4cjgWTIyb1ZeORn9xTP9HcJnV3PEPu zzmcwfu2cRlZuvKV3Q6CNWbio8pamLqVgof9_vY2g85M.IEANQB1WIw-- Received: from [174.48.128.27] by web121603.mail.ne1.yahoo.com via HTTP; Sat, 02 Mar 2013 06:24:54 PST X-Rocket-MIMEInfo: 001.001, DQoNCi0tLSBPbiBNb24sIDIvMjUvMTMsIENocmlzdG9waGVyIEQuIEhhcnJpc29uIDxoYXJyaXNvbkBiaW9zdGF0Lndpc2MuZWR1PiB3cm90ZToNCg0KPiBGcm9tOiBDaHJpc3RvcGhlciBELiBIYXJyaXNvbiA8aGFycmlzb25AYmlvc3RhdC53aXNjLmVkdT4NCj4gU3ViamVjdDogUmU6IGlnYiBuZXR3b3JrIGxvY2t1cHMNCj4gVG86ICJKYWNrIFZvZ2VsIiA8amZ2b2dlbEBnbWFpbC5jb20.DQo.IENjOiBmcmVlYnNkLW5ldEBmcmVlYnNkLm9yZw0KPiBEYXRlOiBNb25kYXksIEZlYnJ1YXJ5IDI1LCAyMDEzLCABMAEBAQE- X-Mailer: YahooMailClassic/15.1.4 YahooMailWebService/0.8.135.514 Message-ID: <1362234294.77730.YahooMailClassic@web121603.mail.ne1.yahoo.com> Date: Sat, 2 Mar 2013 06:24:54 -0800 (PST) From: Barney Cordoba Subject: Re: igb network lockups To: "Christopher D. Harrison" In-Reply-To: <512BAF8D.7080308@biostat.wisc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-net@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Mar 2013 14:28:13 -0000 --- On Mon, 2/25/13, Christopher D. Harrison wr= ote: > From: Christopher D. Harrison > Subject: Re: igb network lockups > To: "Jack Vogel" > Cc: freebsd-net@freebsd.org > Date: Monday, February 25, 2013, 1:38 PM > Sure, > The problem appears on both systems running with ALTQ and > vanilla. > =A0 =A0=A0=A0-C > On 02/25/13 12:29, Jack Vogel wrote: > > I've not heard of this problem, but I think most users > do not use=20 > > ALTQ, and we (Intel) do not > > test using it. Can it be eliminated from the equation? > > > > Jack > > > > > > On Mon, Feb 25, 2013 at 10:16 AM, Christopher D. > Harrison=20 > > > > wrote: > > > >=A0 =A0=A0=A0I recently have been > experiencing network "freezes" and network > >=A0 =A0=A0=A0"lockups" on our Freebsd 9.1 > systems which are running zfs and nfs > >=A0 =A0=A0=A0file servers. > >=A0 =A0=A0=A0I upgraded from 9.0 to 9.1 > about 2 months ago and we have been > >=A0 =A0=A0=A0having issues with almost > bi-monthly.=A0=A0=A0The issue manifests in the > >=A0 =A0=A0=A0system becomes unresponsive to > any/all nfs clients.=A0=A0=A0The system > >=A0 =A0=A0=A0is not resource bound as our > I/O is low to disk and our network is > >=A0 =A0=A0=A0usually in the 20mbit/40mbit > range.=A0=A0=A0We do notice a correlation > >=A0 =A0=A0=A0between temporary i/o spikes > and network freezes but not enough to > >=A0 =A0=A0=A0send our system in to "lockup" > mode for the next 5min.=A0=A0=A0Currently > >=A0 =A0=A0=A0we have 4 igb nics in 2 aggr's > with 8 queue's per nic and our > >=A0 =A0=A0=A0dev.igb reports: > > > >=A0 =A0=A0=A0dev.igb.3.%desc: Intel(R) > PRO/1000 Network Connection version - 2.3.4 > > > >=A0 =A0=A0=A0I am almost certain the problem > is with the ibg driver as a friend > >=A0 =A0=A0=A0is also experiencing the same > problem with the same intel igb nic. > >=A0 =A0 =A0=A0=A0He has addressed the > issue by restarting the network using netif > >=A0 =A0=A0=A0on his > systems.=A0=A0=A0According to my friend, once the > network > >=A0 =A0=A0=A0interfaces get cleared, > everything comes back and starts working > >=A0 =A0=A0=A0as expected. > > > >=A0 =A0=A0=A0I have noticed an issue with > the igb driver and I was looking for > >=A0 =A0=A0=A0thoughts on how to help address > this problem. > >=A0 =A0=A0=A0http://freebsd.1045724.n5.nabble.com/em-igb-if-transmit-drb= r-and-ALTQ-td5760338.html > > > >=A0 =A0=A0=A0Thoughts/Ideas are greatly > appreciated!!! > > > >=A0 =A0 =A0 =A0=A0=A0-C Do you have 32 cpus in the system? You've created a lock contention nightmare; frankly Im surprised that the system runs at all. Try running with 1 queue per nic. The point of using queues is to spread the load; the fact that you're even using queues with such a minuscule load is a commentary on the blind use of "features" without any explanation or understanding of what they do. Does igb still bind to CPUs without regard to whether its a real cpu or a hyper thread? This needs to be removed. I wish that someone who understood this stuff would have a beer with Jack and explain to him why this design is defective. The "default" for this driver is almost always the wrong configuration. You don't need to spread the load with 40Mb/s throughput, and using multiple queues will use a lot more CPU than using just 1. do you really want 4 cpus using 10% instead of 1 using 14%? You also should consider increasing your tx buffers; a property of=20 applications like ALTQ is that they tend to send out big bursts of=20 packets and they can overflow the rings. I'm not specifically familiar with ALTQ so Im not sure how it handles such things; nor am I sure of how it handles multiple tx queues, if at all. BC From owner-freebsd-net@FreeBSD.ORG Sat Mar 2 23:35:12 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AD56AEF; Sat, 2 Mar 2013 23:35:12 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 7A35F95A; Sat, 2 Mar 2013 23:35:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r22NZCda031964; Sat, 2 Mar 2013 23:35:12 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r22NZCoB031960; Sat, 2 Mar 2013 23:35:12 GMT (envelope-from linimon) Date: Sat, 2 Mar 2013 23:35:12 GMT Message-Id: <201303022335.r22NZCoB031960@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/176596: [firewire] [ip6] Crash with IPv6 and Firewire X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Mar 2013 23:35:12 -0000 Old Synopsis: Crash with IPv6 and Firewire New Synopsis: [firewire] [ip6] Crash with IPv6 and Firewire Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat Mar 2 23:34:38 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=176596