Date: Wed, 10 Jan 2018 21:50:06 +0100 From: "Kristof Provost" <kristof@sigsegv.be> To: "Reshad Patuck" <reshadpatuck1@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: [vnet] [epair] epair interface stops working after some time Message-ID: <71B1A1BD-6FCF-47BB-9523-CCAAC03799A5@sigsegv.be> In-Reply-To: <CADaJeD2LZy=RU0vtqD7%2BdkZkUs0GKW%2B7duGDQkZ19GR-_cS=MQ@mail.gmail.com> References: <CADaJeD2LZy=RU0vtqD7%2BdkZkUs0GKW%2B7duGDQkZ19GR-_cS=MQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 5 Jan 2018, at 20:54, Reshad Patuck wrote: > I have done the following on both servers to test what happens: > - Created a new epair interface epair3a and epair3b > - upped both interfaces > - given epair3a IP address 10.20.30.40/24 (I don't have this subnet > anywhere in my network) > - attempted to ping 10.20.30.50 > - checked for any packets on epair3b > On the server where epairs are working, I can see APR packets for > 10.20.30.50, but on the server where epairs are not working I cant see > any > packets on epair3b. > I can however see the arp packets on epair3a on both servers. > So epair3a was not added to the bridge and epair3b was not added to a jail? That’s interesting, because it should mean the problem is not with the bridge or jail. As it affects ARP packets it also shouldn’t be a pf problem. It might be worth unloading the pf module, just to re-confirm, but I wouldn’t expect it to make a difference. > Please let me know if there is anything I can do the debug this issue > or if > you need any other information. > Are you creating/destroying vnet jails at any point? Is there a correlation with that and the start of the epair issues? Are there any errors in `netstat -s` or `netstat -i epair3a` ? Regards, Kristof From owner-freebsd-net@freebsd.org Fri Jan 12 09:23:32 2018 Return-Path: <owner-freebsd-net@freebsd.org> Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58BF0E7D13F; Fri, 12 Jan 2018 09:23:32 +0000 (UTC) (envelope-from bhughes@freebsd.org) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 316917FAA7; Fri, 12 Jan 2018 09:23:31 +0000 (UTC) (envelope-from bhughes@freebsd.org) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id EFA7D20BB8; Fri, 12 Jan 2018 04:23:29 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 12 Jan 2018 04:23:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=t70e03tqjyV1mIKE82t/0hVNERQtS fR/GmghQQtRWCI=; b=Z1xs8mNiKIvIFaSx0T4iXjGE9ziOjE3PUaxx1/HCoNEBp 2n19epn3ZjBgCxbm5nQp3oEOVoAdIX/aHNsTObVkgPWNVVEDhxfAa18E+msOEyNw rj6eNIo0LOOeA5Q5N/L34xsAAFb4DrKujinOtCt5YOUIQXNRY7zvII5gtTZx7/o8 A1lGJVBYZRtAteuTPChyIM+qyX8d/LVFOp/zRRBaCUvI6lRSlrH4MvBH403EJcc8 IwGnI7S8MWrwuJeG/6tmuNWy4LXVzsFeji6/nAwPj5PRMqroxoHjEnW1VQx/CH1R FKg0oQ+Le8pfhCs4MVlCg0j2iGAu6Znrr/fEmH7EQ== X-ME-Sender: <xms:kX5YWgBIcYyCN-h5whKT1Xmg8dsuKyD9Gsoe8dMFxQEvMZ0ey8W_vA> Received: from hayseed.lan (90.89-11-136.nextgentel.com [89.11.136.90]) by mail.messagingengine.com (Postfix) with ESMTPA id 594DE7E51F; Fri, 12 Jan 2018 04:23:29 -0500 (EST) From: "Bradley T. Hughes" <bhughes@freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Panic with recent -CURRENT kernel in EC2 Message-Id: <E708396E-B987-4B1A-A373-101B2B62CB64@freebsd.org> Date: Fri, 12 Jan 2018 10:23:27 +0100 Cc: freebsd-net@freebsd.org To: freebsd-cloud@freebsd.org X-Mailer: Apple Mail (2.3445.5.20) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>, <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>; List-Post: <mailto:freebsd-net@freebsd.org> List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>, <mailto:freebsd-net-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 12 Jan 2018 09:23:32 -0000 (Cross-posting to -net, but I'm not subscribed there... yet) I was wondering if anyone else has experienced this panic when dhclient = tries to get an IP address after booting a recent 12.0-CURRENT kernel? = Using the 12.0-CURRENT AMI from early November works, but with the = latest snapshot or when using a kernel built from source I get this: ixv0: <Intel(R) PRO/10GbE Virtual Function Network Driver> mem = 0xf3000000-0xf3003fff,0xf3004000-0xf3007fff at device 3.0 on pci0 ixv0: using 2048 tx descriptors and 2048 rx descriptors ixv0: msix_init qsets capped at 1 ixv0: pxm cpus: 2 queue msgs: 2 admincnt: 1 ixv0: using 1 rx queues 1 tx queues=20 ixv0: Using MSIX interrupts with 2 vectors ixv0: allocated for 1 queues ixv0: allocated for 1 rx queues taskqgroup_attach_cpu: setaffinity failed: 22 taskqgroup_attach_cpu: setaffinity failed: 22 ixv0: Ethernet address: 0a:ad:68:70:ea:78 ixv0: netmap queues/slots: TX 1/2048, RX 1/2048 ... panic: Assertion if_getdrvflags(ifp) =3D=3D i failed at = /usr/src/sys/net/iflib.c:2199 cpuid =3D 3 time =3D 1515673176 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame = 0xfffffe008a8ee600 vpanic() at vpanic+0x19c/frame 0xfffffe008a8ee680 kassert_panic() at kassert_panic+0x126/frame 0xfffffe008a8ee6f0 iflib_init_locked() at iflib_init_locked+0x75f/frame 0xfffffe008a8ee750 iflib_if_ioctl() at iflib_if_ioctl+0x744/frame 0xfffffe008a8ee7b0 ifioctl() at ifioctl+0x1903/frame 0xfffffe008a8ee850 kern_ioctl() at kern_ioctl+0x2c4/frame 0xfffffe008a8ee8b0 sys_ioctl() at sys_ioctl+0x15c/frame 0xfffffe008a8ee980 amd64_syscall() at amd64_syscall+0x79b/frame 0xfffffe008a8eeab0 Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe008a8eeab0 --- syscall (54, FreeBSD ELF64, sys_ioctl), rip =3D 0x80100a4fa, rsp =3D = 0x7fffffffe408, rbp =3D 0x7fffffffe460 --- Thanks in advance :) -- Bradley T. Hughes bhughes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?71B1A1BD-6FCF-47BB-9523-CCAAC03799A5>