From owner-freebsd-net@freebsd.org Thu Mar 29 12:49:05 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9B87F735D5 for ; Thu, 29 Mar 2018 12:49:05 +0000 (UTC) (envelope-from reshadpatuck1@gmail.com) Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 447426BEAD for ; Thu, 29 Mar 2018 12:49:05 +0000 (UTC) (envelope-from reshadpatuck1@gmail.com) Received: by mail-pg0-x22f.google.com with SMTP id n11so2985942pgp.4 for ; Thu, 29 Mar 2018 05:49:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:to:cc:from:message-id; bh=vHCIZqrs/p9LfBZ7qE4cj4u9ZwfwNDbgZSYZeT5pe4c=; b=oYeFF3GmvKyfPWeQncqYp4BECGj2n5cAkv5pAaRpciXVbaiib3hkwe8Pu5yVw/WXmp JmA7nAdW6awuYndVrAVC+LIMKAyUigs4nruvsTpiIyk3rVQ+F/Dty2OAERiwnka1Zij4 OMBVVjd5UktuK4KG25ofSTnu+9ttni6ozHIt9D6RcykE4AODrVYY4F6JgPpuTY9kcIMR 6rmSJl9TmuTsBqNJVqbwHZYp3RdDCOw4UunwRxRU+hPHIIsYjXwapEXDfzvmJjdiXZwc Jipd03zzTQLK7MivZ7FTGYyhhrpCVFGeW9nDhKjjITRIlABXmW62IXnBOyjgS5i5OyIB 9Itg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:cc:from :message-id; bh=vHCIZqrs/p9LfBZ7qE4cj4u9ZwfwNDbgZSYZeT5pe4c=; b=OdTGu3YOrdaU2Tx+thx7b+r9XM0InmBgNQA7GQuYDMVhhgltFEy8qBTDRUKoMpnNAB e89TP6b5V5O+loe6zDbV14fNchkx3h2M3tIYDGwoctMhWakyGcoDMUXKV+k9taQvHVyR Gi7nfDdHSpGb9BCbKZ6Ee3GagJbbhMs87UWGTLJbQtFipMXsz32nu3bPEkd1LFoA1HFH 9CxZhNS0n5cIRBzXXgvyNywUg/FLyGhOptcSN4dlFXxrj0iblqiD8jk3xI9vZEJ6ZoQl OzrwwukGsHM6km+2cmtXFCRnsxAd0RuTMGtx8p5RmuzNnKYLwSmPnf+MkJoLiAwSUcW8 YcWg== X-Gm-Message-State: AElRT7GBj6PkQ4LeWJNpek/8t4sfUJIDmwrxzJmXuublaPOD7a7KjPbH yfFt47RSenh9lkrQykw61KGr2KXnG9fnPg== X-Google-Smtp-Source: AIpwx4+IhBaJvJEF8UKRItyDHjjpYKya2aW1NFdl4yrbCnTjf18Hxk01+mW1RWYOEJ5uaweu2sf0Bw== X-Received: by 10.99.155.2 with SMTP id r2mr5549426pgd.450.1522327744323; Thu, 29 Mar 2018 05:49:04 -0700 (PDT) Received: from [10.190.139.106] ([42.106.196.181]) by smtp.gmail.com with ESMTPSA id a5sm14276117pfl.159.2018.03.29.05.49.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Mar 2018 05:49:03 -0700 (PDT) Date: Thu, 29 Mar 2018 18:18:58 +0530 User-Agent: K-9 Mail for Android In-Reply-To: <277350C5-3B1F-4105-AF0A-886B6133218E@sigsegv.be> References: <71B1A1BD-6FCF-47BB-9523-CCAAC03799A5@sigsegv.be> <1563563.7DUcjoHYMp@reshadlaptop.patuck.net> <1D6101CD-BCB4-4206-838B-1A75152ACCC4@sigsegv.be> <38C78C2B-87D2-4225-8F4B-A5EA48BA5D17@patuck.net> <5803CAA2-DC4A-4E49-B715-6DE472088DDD@sigsegv.be> <9CAB4522-0B0A-42BF-B9A4-BF36AFC60286@patuck.net> <7202AFF2-A314-41FE-BD13-C4C77A95E106@sigsegv.be> <2D15ABDE-0C25-4C97-AEA6-0098459A2795@lists.zabbadoz.net> <277350C5-3B1F-4105-AF0A-886B6133218E@sigsegv.be> MIME-Version: 1.0 Subject: Re: [vnet] [epair] epair interface stops working after some time To: Kristof Provost CC: freebsd-net@freebsd.org, "Bjoern A. Zeeb" , Reshad Patuck From: Reshad Patuck Message-ID: <97945712-B53E-4CF6-B20E-6001CF40CDFC@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Mar 2018 12:49:06 -0000 =E2=80=8B Hi, pulling the 'net=2Elink=2Eepair=2Enetisr_maxqlen' down does seem to make t= his occur faster=2E =E2=80=8B When I dropped it to 2 like Kristof did and I have the same symptoms on a = box which was not exhibiting the problems manually began to have the same s= ymptoms=2E Bumping it back up to 2100 did not restore the functionality (I don't know= if it should)=2E =E2=80=8B I will create a PR for this later today with all the information I have ga= thered so that we can have it all in one place=2E Till then I have still have access to a box which is naturally in this sta= te=2E Let me know if there is anything you would like me to check =E2=80=8B Thanks for the help, =E2=80=8B Reshad On 28 March 2018 12:32:44 AM IST, Kristof Provost w= rote: >On 27 Mar 2018, at 20:59, Reshad Patuck wrote: >> The current value of 'net=2Elink=2Eepair=2Enetisr_maxqlen' is 2100, I w= ill=20 >> make it 210=2E >> Will this require a reboot? or can I just change the sysctl and >reload=20 >> the epair module? >> =E2=80=8B >You shouldn=E2=80=99t need to reboot or reload the epair module=2E When I= set it=20 >to 2 on my box it pretty much immediately lost connectivity over the=20 >epair interfaces=2E > >I=E2=80=99d expect you to get hit by the bug relatively quickly now, so b= e=20 >aware of that=2E > >Regards, >Kristof