From owner-freebsd-net@freebsd.org Sun Oct 9 21:00:22 2016 Return-Path: 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 1300BC07285 for ; Sun, 9 Oct 2016 21:00:22 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 DA39B15E for ; Sun, 9 Oct 2016 21:00:21 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u99L01ZO089625 for ; Sun, 9 Oct 2016 21:00:21 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201610092100.u99L01ZO089625@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-net@FreeBSD.org Subject: Problem reports for freebsd-net@FreeBSD.org that need special attention Date: Sun, 09 Oct 2016 21:00:21 +0000 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 09 Oct 2016 21:00:22 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- In Progress | 203422 | mpd/ppoe not working with re(4) with revision 285 In Progress | 206581 | bxe_ioctl_nvram handler is faulty New | 204438 | setsockopt() handling of kern.ipc.maxsockbuf limi New | 205592 | TCP processing in IPSec causes kernel panic New | 206053 | kqueue support code of netmap causes panic Open | 193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc Open | 194485 | Userland cannot add IPv6 prefix routes Open | 194515 | Fatal Trap 12 Kernel with vimage Open | 199136 | [if_tap] Added down_on_close sysctl variable to t Open | 206544 | sendmsg(2) (sendto(2) too?) can fail with EINVAL; Open | 211031 | [panic] in ng_uncallout when argument is NULL Open | 211962 | bxe driver queue soft hangs and flooding tx_soft_ 12 problems total for which you should take action. From owner-freebsd-net@freebsd.org Tue Oct 11 01:17:57 2016 Return-Path: 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 A0300C0B31E for ; Tue, 11 Oct 2016 01:17:57 +0000 (UTC) (envelope-from lohithbsd@gmail.com) Received: from mail-pa0-x241.google.com (mail-pa0-x241.google.com [IPv6:2607:f8b0:400e:c03::241]) (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 737EB13B; Tue, 11 Oct 2016 01:17:57 +0000 (UTC) (envelope-from lohithbsd@gmail.com) Received: by mail-pa0-x241.google.com with SMTP id r9so469112paz.1; Mon, 10 Oct 2016 18:17:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=hx5s9YP/uYI50ML/6qQQ6BrZe0vRWD35h1rThhgEdUA=; b=dtXRCOeY8qNke8cCmUKarSca2ZHn0bOgJhGHfztodNzClY22IiN/T8eETlaMahSKKw hbghVhtP6CGLGTxG7iraQORnetJmPN9ouKgXpa8wg7e/rcgcK+gdU3EJy6GxyUtMGLyg Bwy9FAM1a3yDVfKrO0PwfF902Fnb1HGM0YWAUA18MnVwPSbt/RCpKCPYESNvHmAN7NTe 2BliidIJlyQDJ5EYqlM/3QeYlW9sFpehB5bRrQZe9mdI0ncBfjr0Ezo1mP744PMQAuEN FcilmSTHhTTqGHGpOuarJErL/TWs0vCCU1lQ1lO6bhxIo6Ub7tW3nJ9Q0Hj1kV9t8Rpe 7aTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=hx5s9YP/uYI50ML/6qQQ6BrZe0vRWD35h1rThhgEdUA=; b=VtApJMup+USefyGvDM/lcFy/jNvyJpBku7c6NzDhEMh0H2qgaGOvGg583cdziQ5a1m Kbjjg7gWuA4yuNhcsSFwN/Uh4xdp/7yrsPerglj02uXwe1OcLAl7JsR1CZdQnywtWP88 k575yS5PkgEgLZ0vZBFsR/M3CpZzJ7K2Gl8f4yxqWTHFeBXoTQXxpZ6+WNRSJdFAb4j7 c2kcgyflZtQkPypzsxERE56BGaotpOdFoHSnzVBfopx0y3o3rcko1GmUhhlun18A1TfE tG/fOMB7ENRV6nB7TR98ChjJ5sxOlMgxF3uibxdDGpN1q4TmFNMhci6ZQwAsABuBsVK/ BGKw== X-Gm-Message-State: AA6/9RlDhHmRodwMMd7RqDcHxCBdeCTZEUUr1GaaJuKiblucSDC5qG354OB7ZB1W1dGi+w== X-Received: by 10.66.89.4 with SMTP id bk4mr2121781pab.22.1476148676786; Mon, 10 Oct 2016 18:17:56 -0700 (PDT) Received: from [172.29.109.159] ([66.129.239.11]) by smtp.gmail.com with ESMTPSA id i8sm671789paw.25.2016.10.10.18.17.55 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 10 Oct 2016 18:17:56 -0700 (PDT) From: Lohith Bellad Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Problem with Virtio using JUMBO frame config. Message-Id: Date: Mon, 10 Oct 2016 18:17:54 -0700 To: freebsd-net@freebsd.org, bryanv@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Oct 2016 01:17:57 -0000 Hi All, I want to use Virtio with JUMBO frame support without TSOv4, TSOv6 and = GSO. Looks like without TSOv4, TSOv6 and GSO. The max number of segments = allowed for scatter gather operations is 4.=20 But, if TSOv4, TSOv6 or GSO feature is enabled, max segments for scatter = gather is set to 64. sys/dev/virtio/network/if_vtnet.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D if (virtio_with_feature(dev, VIRTIO_NET_F_GSO) || virtio_with_feature(dev, VIRTIO_NET_F_HOST_TSO4) || virtio_with_feature(dev, VIRTIO_NET_F_HOST_TSO6)) sc->vtnet_tx_nsegs =3D VTNET_MAX_TX_SEGS; <=3D=3D 64 else sc->vtnet_tx_nsegs =3D VTNET_MIN_TX_SEGS; <=3D=3D 4 In my case since I don=E2=80=99t have TSOv4, TSOv6 or GSO enabled, so = max segments is 4. And if I try to send PING echo with size 18000 or more (results into 3 = frames), driver is failing to send it. PING with size less than 15000 = works always. Using dtrace and vtnet sysctls found that, in my case scatter gather = segments are more than 4 and thats why EFBIG error is returned by = sglist_append_mbuf(). Also, vtnet defrag failed stats are increasing, dev.vtnet.4.tx_defragged: 111443 dev.vtnet.4.tx_defrag_failed: 7917 These changes were done in following commit https://svnweb.freebsd.org/base?view=3Drevision&revision=3D261394 So, is JUMBO frame support allowed only with TSO support or am I missing = something. Any help is appreciated. Thanks, Lohith From owner-freebsd-net@freebsd.org Tue Oct 11 02:30:11 2016 Return-Path: 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 843DDC0C966 for ; Tue, 11 Oct 2016 02:30:11 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id 6095262D for ; Tue, 11 Oct 2016 02:30:11 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id B87E8140CF; Tue, 11 Oct 2016 02:30:10 +0000 (UTC) Date: Tue, 11 Oct 2016 02:30:10 +0000 To: freebsd-net@freebsd.org From: "sepherosa_gmail.com (Sepherosa Ziehau)" Reply-to: D8214+325+1c6d6dd19d32a9c0@reviews.freebsd.org Subject: [Differential] D8214: ifnet: Use if_link_state snapshot to invoke ifnet_link_event Message-ID: X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , , Thread-Topic: D8214: ifnet: Use if_link_state snapshot to invoke ifnet_link_event X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: Precedence: bulk Thread-Index: Zjc3NzgxNjgwMTk5OWNkOTQzZDBmNGQzMGI5 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b1_2a884883d945a5974a0d919cda9702a7" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Oct 2016 02:30:11 -0000 --b1_2a884883d945a5974a0d919cda9702a7 Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: base64 c2VwaGVyb3NhX2dtYWlsLmNvbSBjcmVhdGVkIHRoaXMgcmV2aXNpb24uCnNlcGhlcm9zYV9nbWFp bC5jb20gYWRkZWQgcmV2aWV3ZXJzOiBnbGViaXVzLCBhZHJpYW4sIGdubiwgYnouCnNlcGhlcm9z YV9nbWFpbC5jb20gYWRkZWQgYSBzdWJzY3JpYmVyOiBmcmVlYnNkLW5ldC1saXN0LgoKUkVWSVNJ T04gU1VNTUFSWQogIFNvIHRoYXQgZXZlcnlvbmUgaW4gdGhpcyB0YXNrIGhhdmUgY29uc2lzdGVu dCB2aWV3IG9mIGxpbmsgc3RhdGUuCgpSRVZJU0lPTiBERVRBSUwKICBodHRwczovL3Jldmlld3Mu ZnJlZWJzZC5vcmcvRDgyMTQKCkFGRkVDVEVEIEZJTEVTCiAgc3lzL25ldC9pZi5jCgpDSEFOR0Ug REVUQUlMUwoKZGlmZiAtLWdpdCBhL3N5cy9uZXQvaWYuYyBiL3N5cy9uZXQvaWYuYwotLS0gYS9z eXMvbmV0L2lmLmMKKysrIGIvc3lzL25ldC9pZi5jCkBAIC0yMjA2LDcgKzIyMDYsNyBAQAogCWlm IChsb2dfbGlua19zdGF0ZV9jaGFuZ2UpCiAJCWxvZyhMT0dfTk9USUNFLCAiJXM6IGxpbmsgc3Rh dGUgY2hhbmdlZCB0byAlc1xuIiwgaWZwLT5pZl94bmFtZSwKIAkJICAgIChsaW5rX3N0YXRlID09 IExJTktfU1RBVEVfVVApID8gIlVQIiA6ICJET1dOIiApOwotCUVWRU5USEFORExFUl9JTlZPS0Uo aWZuZXRfbGlua19ldmVudCwgaWZwLCBpZnAtPmlmX2xpbmtfc3RhdGUpOworCUVWRU5USEFORExF Ul9JTlZPS0UoaWZuZXRfbGlua19ldmVudCwgaWZwLCBsaW5rX3N0YXRlKTsKIAlDVVJWTkVUX1JF U1RPUkUoKTsKIH0KIAoKCgpFTUFJTCBQUkVGRVJFTkNFUwogIGh0dHBzOi8vcmV2aWV3cy5mcmVl YnNkLm9yZy9zZXR0aW5ncy9wYW5lbC9lbWFpbHByZWZlcmVuY2VzLwoKVG86IHNlcGhlcm9zYV9n bWFpbC5jb20sIGdsZWJpdXMsIGFkcmlhbiwgZ25uLCBiegpDYzogZnJlZWJzZC1uZXQtbGlzdAo= --b1_2a884883d945a5974a0d919cda9702a7 Content-Type: text/x-patch; charset=utf-8; name="D8214.21239.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="D8214.21239.patch" ZGlmZiAtLWdpdCBhL3N5cy9uZXQvaWYuYyBiL3N5cy9uZXQvaWYuYwotLS0gYS9zeXMvbmV0L2lm LmMKKysrIGIvc3lzL25ldC9pZi5jCkBAIC0yMjA2LDcgKzIyMDYsNyBAQAogCWlmIChsb2dfbGlu a19zdGF0ZV9jaGFuZ2UpCiAJCWxvZyhMT0dfTk9USUNFLCAiJXM6IGxpbmsgc3RhdGUgY2hhbmdl ZCB0byAlc1xuIiwgaWZwLT5pZl94bmFtZSwKIAkJICAgIChsaW5rX3N0YXRlID09IExJTktfU1RB VEVfVVApID8gIlVQIiA6ICJET1dOIiApOwotCUVWRU5USEFORExFUl9JTlZPS0UoaWZuZXRfbGlu a19ldmVudCwgaWZwLCBpZnAtPmlmX2xpbmtfc3RhdGUpOworCUVWRU5USEFORExFUl9JTlZPS0Uo aWZuZXRfbGlua19ldmVudCwgaWZwLCBsaW5rX3N0YXRlKTsKIAlDVVJWTkVUX1JFU1RPUkUoKTsK IH0KIAoK --b1_2a884883d945a5974a0d919cda9702a7-- From owner-freebsd-net@freebsd.org Tue Oct 11 04:02:36 2016 Return-Path: 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 6301FC078C1 for ; Tue, 11 Oct 2016 04:02:36 +0000 (UTC) (envelope-from laa88rf@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 449B2EBB for ; Tue, 11 Oct 2016 04:02:36 +0000 (UTC) (envelope-from laa88rf@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 43FA2C078C0; Tue, 11 Oct 2016 04:02:36 +0000 (UTC) Delivered-To: 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 439C5C078BF for ; Tue, 11 Oct 2016 04:02:36 +0000 (UTC) (envelope-from laa88rf@gmail.com) Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c:c05::231]) (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 F3F34EBA for ; Tue, 11 Oct 2016 04:02:35 +0000 (UTC) (envelope-from laa88rf@gmail.com) Received: by mail-vk0-x231.google.com with SMTP id z126so8360322vkd.0 for ; Mon, 10 Oct 2016 21:02:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=LL3TiT+Ifry9uXN9nUm09Ui73lWDrg1D1OG20eAUsYw=; b=dO/kxG80gcrn+WxF9olKLYC9PD8yXoysU6/2q49Ao0qHNHUqur80xpFkTEDeZe0ODV 8tUO8wVcQ0Jgx5IUNoDAjJGRfN0bDDyt3zP5i1CtLyil6ILf1qqy+nKg+6hGFyHQxZdH L8e3l4mlBx1vMNNCTYOnCIRnSaMUhggMFyKGFIIwe1oo/Ch2K2tfnP1c12IpT/rqb3Vy fR7H/sKAnqh+poLgPBNymDw56+xFOgS2TzLomw3Gyg1k+Y430nsZkjmbHikB6M99G9t6 QtCVQ4EM8pzEOYW6ZsO/26eTe/095vJU5fAynlUjX6plCRp7h20silkLoPpr3dAnBJQI ZOow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=LL3TiT+Ifry9uXN9nUm09Ui73lWDrg1D1OG20eAUsYw=; b=j1PKMMIOwFQP+5JA7oPN7bPmSb9V1OG6xaMEu+bkDu9vM/rlaOQ0JCWufr5m1FE7Vr fT4BTE2W1wUTYpkBUCIStoN5rvANMlgcWLo5cX8oWmMWcKbQB+x9G+yKFMMydfK97uLX tYX5ZXxpnjvm8S5PNTvwvWbg/ULafdoxNztSczUAtcGJulIVVWi53vsrLT3pq3xTJ2ca PI1PfGFdRLEosJNT+V7KzqviGHQb2DAbjJTjXQJ/ejTui9WnH7ZTwoIX9DqlMSRIa2IP ok/Ij4x+sQtBeM2YhZWKJj3kEMAtRjNPIW5rWmPsF9sPpuLjnVRyPYIrkSEMGbesr2+d q+0w== X-Gm-Message-State: AA6/9Rks0fXcvW9yP334TvRGpIoygPwGhdw6DwMuUyYj77M5DYujZDxSLFWDFmhu5N8YcqCkOjAsWb9MKc0Brg== X-Received: by 10.31.92.216 with SMTP id q207mr1481805vkb.147.1476158554901; Mon, 10 Oct 2016 21:02:34 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.143.23 with HTTP; Mon, 10 Oct 2016 21:02:34 -0700 (PDT) From: =?UTF-8?B?0JDQvdC00YDQtdC5INCb0LXRg9GI0LrQuNC9?= Date: Tue, 11 Oct 2016 09:02:34 +0500 Message-ID: Subject: FreeBSD10.3-RELEASE. Kernel panic. To: net@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Oct 2016 04:02:36 -0000 Hello. I have problem with "FreeBSD nas 10.3-RELEASE FreeBSD 10.3-RELEASE #0: Fri Oct 7 21:12:56 YEKT 2016 nas@nas:/usr/obj/usr/src/sys/nasv3 amd64" Kernel panic is repeated at intervals of 2-3 days. At first I thought that the problem is in the hardware, but the problem did not go away after replacing the server platform. Coredumps and more info on link https://drive.google.com/open?id=0BxciMy2q7ZjTTkIxem9wTE1tM2M Sorry for my english. I'll wait for an answer. From owner-freebsd-net@freebsd.org Tue Oct 11 06:36:03 2016 Return-Path: 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 076C3C0C9C3 for ; Tue, 11 Oct 2016 06:36:03 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E1BBF30E for ; Tue, 11 Oct 2016 06:36:02 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: by mailman.ysv.freebsd.org (Postfix) id E1222C0C9C2; Tue, 11 Oct 2016 06:36:02 +0000 (UTC) Delivered-To: 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 E0CE6C0C9C1 for ; Tue, 11 Oct 2016 06:36:02 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from hz.grosbein.net (hz.grosbein.net [78.47.246.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hz.grosbein.net", Issuer "hz.grosbein.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 74AA230C for ; Tue, 11 Oct 2016 06:36:01 +0000 (UTC) (envelope-from eugen@grosbein.net) Received: from eg.sd.rdtc.ru (root@eg.sd.rdtc.ru [62.231.161.221]) by hz.grosbein.net (8.14.9/8.14.9) with ESMTP id u9B6OadL019453 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 11 Oct 2016 08:24:37 +0200 (CEST) (envelope-from eugen@grosbein.net) X-Envelope-From: eugen@grosbein.net X-Envelope-To: laa88rf@gmail.com Received: from [10.58.0.10] (dadvw [10.58.0.10]) by eg.sd.rdtc.ru (8.15.2/8.15.2) with ESMTPS id u9B6OaNV044351 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 11 Oct 2016 13:24:36 +0700 (KRAT) (envelope-from eugen@grosbein.net) Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. To: =?UTF-8?B?0JDQvdC00YDQtdC5INCb0LXRg9GI0LrQuNC9?= , net@freebsd.org References: From: Eugene Grosbein Message-ID: <57FC859F.5000200@grosbein.net> Date: Tue, 11 Oct 2016 13:24:31 +0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00,LOCAL_FROM autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hz.grosbein.net X-Spam-Report: * -2.3 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 2.6 LOCAL_FROM From my domains X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Oct 2016 06:36:03 -0000 11.10.2016 11:02, Андрей Леушкин пишет: > Hello. I have problem with "FreeBSD nas 10.3-RELEASE FreeBSD 10.3-RELEASE > #0: Fri Oct 7 21:12:56 YEKT 2016 nas@nas:/usr/obj/usr/src/sys/nasv3 > amd64" > > Kernel panic is repeated at intervals of 2-3 days. At first I thought that > the problem is in the hardware, but the problem did not go away after > replacing the server platform. > > Coredumps and more info on link > https://drive.google.com/open?id=0BxciMy2q7ZjTTkIxem9wTE1tM2M > > Sorry for my english. > I'll wait for an answer. This is known and long-stanging problem in the FreeBSD network stack. It shows up when you have lots of network interfaced created/removed frequently like in your case of Network Access Server (PPtP, PPPoE etc). Generally, people run into this problem using mpd5 network daemon. mpd5 uses NETGRAPH kernel subsystem to process traffic and if an interface disappears (f.e., ,user disconnected) while kernel still processes traffic obtained from this interface, it panices. There were lots of reports of this problem. Noone seems to be working on it at the moment. You should fill a PR using Bugzilla and attach your logs to it. Eugene Grosbein From owner-freebsd-net@freebsd.org Tue Oct 11 11:30:08 2016 Return-Path: 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 388CAC0D418 for ; Tue, 11 Oct 2016 11:30:08 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 164CFB7C for ; Tue, 11 Oct 2016 11:30:08 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 12E08C0D415; Tue, 11 Oct 2016 11:30:08 +0000 (UTC) Delivered-To: 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 1281CC0D414 for ; Tue, 11 Oct 2016 11:30:08 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (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 C0B46B7A for ; Tue, 11 Oct 2016 11:30:07 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mail-qk0-x22c.google.com with SMTP id n189so28019011qke.0 for ; Tue, 11 Oct 2016 04:30:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gr+gaHJ8VSdeczawGVSVf7wYvwWoVkcs1JN67wdfD78=; b=EY9S5otMw30rnICXgvS+yYUgNr10qYL+9Rbyh9qBlC0fVd53lJagXN6aZmgjrxsYSU +6GorEIGkSYsT5gJFyDsL+4eVypfq1CotUDuC+aAFkUhfcMz5TUFBxz1v8k9g24MIXQV CDVa/l1trBqK+NCrpeY+LxpNYvncvmbE2c0waMNZzo22emmYbuEWxvteB7aTmQ0iz5dG ctxbuiZC1VkLkUTyeqqPuZJf9CMC+rIYKHPIZG64ZZNMhhdvf64qERKJw8e2YGhrtPdu ksT3x9YSYQZ0UORN0py+U3OwjXfE2VaQZz94tBXbPxptLI627+xSTApg6UtKCL/rYRWc gx5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gr+gaHJ8VSdeczawGVSVf7wYvwWoVkcs1JN67wdfD78=; b=gsJqUrcSS3bwG/ynRG32RUXYIcl5OBDZQUW5XRCqWUanUUpcNe7gwJmrNpKbduThts TFnqdZdtD/SbHt55xU9jOoihq9Kn3HwCMVjHl7mjiD1E9Ci4JjBxcXqMm/XS1jzHiO26 e6/Mg3OACgxcrJwlxSMed2rKXL2/825ZWbIOI7xVa0B/HyG9tqtHCOWCj+9uL3a2QxsY 29KGVg9ukRt8gm2RnvlN3BoAoHNrooR7FvEAHFu8jKX6s1aY1uqXbEFIzUXTxd6L8rri ZLHaHWCQUcfPh4kUclp04JL7OJcPFQ41Z4sBH+2OoF3VcVgK4YpJgITMop8XU+4+MLGB QDOA== X-Gm-Message-State: AA6/9RnkE0SYI4p6mayruyNlNl1tlwT9Bsx5Nr6+CSOQUoXEEzD/go0JmL8cUpgXgpNLi3uJzLJK2YmhzgJvqw== X-Received: by 10.55.79.71 with SMTP id d68mr3101409qkb.95.1476185406460; Tue, 11 Oct 2016 04:30:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.166.26 with HTTP; Tue, 11 Oct 2016 04:30:06 -0700 (PDT) In-Reply-To: <57FC859F.5000200@grosbein.net> References: <57FC859F.5000200@grosbein.net> From: Cassiano Peixoto Date: Tue, 11 Oct 2016 08:30:06 -0300 Message-ID: Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. To: Eugene Grosbein Cc: =?UTF-8?B?0JDQvdC00YDQtdC5INCb0LXRg9GI0LrQuNC9?= , net@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Oct 2016 11:30:08 -0000 Hi, There are many users complaining about this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114 I've been dealing with this issue for one year with no solution. mpd5 as pppoe server on FreeBSD is useless with this bug. I really would like to see it working again, i think it's quite important to both project and many users. Thanks. On Tue, Oct 11, 2016 at 3:24 AM, Eugene Grosbein wrote= : > 11.10.2016 11:02, =D0=90=D0=BD=D0=B4=D1=80=D0=B5=D0=B9 =D0=9B=D0=B5=D1=83= =D1=88=D0=BA=D0=B8=D0=BD =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >> Hello. I have problem with "FreeBSD nas 10.3-RELEASE FreeBSD 10.3-RELEAS= E >> #0: Fri Oct 7 21:12:56 YEKT 2016 nas@nas:/usr/obj/usr/src/sys/nasv3 >> amd64" >> >> Kernel panic is repeated at intervals of 2-3 days. At first I thought th= at >> the problem is in the hardware, but the problem did not go away after >> replacing the server platform. >> >> Coredumps and more info on link >> https://drive.google.com/open?id=3D0BxciMy2q7ZjTTkIxem9wTE1tM2M >> >> Sorry for my english. >> I'll wait for an answer. >> > > This is known and long-stanging problem in the FreeBSD network stack. > It shows up when you have lots of network interfaced created/removed > frequently > like in your case of Network Access Server (PPtP, PPPoE etc). > > Generally, people run into this problem using mpd5 network daemon. > mpd5 uses NETGRAPH kernel subsystem to process traffic and > if an interface disappears (f.e., ,user disconnected) > while kernel still processes traffic obtained from this interface, it > panices. > > There were lots of reports of this problem. Noone seems to be working on > it at the moment. > You should fill a PR using Bugzilla and attach your logs to it. > > Eugene Grosbein > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://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 Oct 11 11:53:50 2016 Return-Path: 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 653DCC0D0B1 for ; Tue, 11 Oct 2016 11:53:50 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id 42F0079 for ; Tue, 11 Oct 2016 11:53:50 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id B34BB165F6; Tue, 11 Oct 2016 11:53:49 +0000 (UTC) Date: Tue, 11 Oct 2016 11:53:49 +0000 To: freebsd-net@freebsd.org From: "ae (Andrey V. Elsukov)" Reply-to: D8214+325+1c6d6dd19d32a9c0@reviews.freebsd.org Subject: [Differential] D8214: ifnet: Use if_link_state snapshot to invoke ifnet_link_event Message-ID: <3f892c2aebb638c049c129f3e08a315a@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , , Thread-Topic: D8214: ifnet: Use if_link_state snapshot to invoke ifnet_link_event X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: Zjc3NzgxNjgwMTk5OWNkOTQzZDBmNGQzMGI5IFf80s0= MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Oct 2016 11:53:50 -0000 YWUgYWNjZXB0ZWQgdGhpcyByZXZpc2lvbi4KYWUgYWRkZWQgYSByZXZpZXdlcjogYWUuCmFlIGFk ZGVkIGEgY29tbWVudC4KVGhpcyByZXZpc2lvbiBoYXMgYSBwb3NpdGl2ZSByZXZpZXcuCgoKICBM b29rcyBvayB0byBtZS4KClJFVklTSU9OIERFVEFJTAogIGh0dHBzOi8vcmV2aWV3cy5mcmVlYnNk Lm9yZy9EODIxNAoKRU1BSUwgUFJFRkVSRU5DRVMKICBodHRwczovL3Jldmlld3MuZnJlZWJzZC5v cmcvc2V0dGluZ3MvcGFuZWwvZW1haWxwcmVmZXJlbmNlcy8KClRvOiBzZXBoZXJvc2FfZ21haWwu Y29tLCBnbGViaXVzLCBhZHJpYW4sIGdubiwgYnosIGFlCkNjOiBhZSwgZnJlZWJzZC1uZXQtbGlz dAo= From owner-freebsd-net@freebsd.org Tue Oct 11 11:55:13 2016 Return-Path: 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 1C8ACC0D206 for ; Tue, 11 Oct 2016 11:55:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 0C8A61F2 for ; Tue, 11 Oct 2016 11:55:13 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9BBtCSD095017 for ; Tue, 11 Oct 2016 11:55:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213370] Kernel panic with ng_tcpmss Date: Tue, 11 Oct 2016 11:55:13 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 11 Oct 2016 11:55:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213370 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org CC|freebsd-amd64@FreeBSD.org | --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 12 01:52:48 2016 Return-Path: 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 27351C0CE63 for ; Wed, 12 Oct 2016 01:52:48 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: from reviews.nyi.freebsd.org (reviews.nyi.freebsd.org [IPv6:2610:1c1:1:607c::16:b]) by mx1.freebsd.org (Postfix) with ESMTP id 03720A65 for ; Wed, 12 Oct 2016 01:52:48 +0000 (UTC) (envelope-from daemon-user@freebsd.org) Received: by reviews.nyi.freebsd.org (Postfix, from userid 1346) id 7B6C01448D; Wed, 12 Oct 2016 01:52:47 +0000 (UTC) Date: Wed, 12 Oct 2016 01:52:47 +0000 To: freebsd-net@freebsd.org From: Phabricator Reply-to: D8214+325+1c6d6dd19d32a9c0@reviews.freebsd.org Subject: [Differential] D8214: ifnet: Use if_link_state snapshot to invoke ifnet_link_event Message-ID: <1f3b44c43b6a03a18bed63e9d5751f0b@localhost.localdomain> X-Priority: 3 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , Thread-Topic: D8214: ifnet: Use if_link_state snapshot to invoke ifnet_link_event X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Precedence: bulk In-Reply-To: References: Thread-Index: Zjc3NzgxNjgwMTk5OWNkOTQzZDBmNGQzMGI5IFf9l28= MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="b1_1f3b44c43b6a03a18bed63e9d5751f0b" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2016 01:52:48 -0000 --b1_1f3b44c43b6a03a18bed63e9d5751f0b Content-Type: text/plain; charset = "utf-8" Content-Transfer-Encoding: base64 VGhpcyByZXZpc2lvbiB3YXMgYXV0b21hdGljYWxseSB1cGRhdGVkIHRvIHJlZmxlY3QgdGhlIGNv bW1pdHRlZCBjaGFuZ2VzLgpDbG9zZWQgYnkgY29tbWl0IHJTMzA3MDc4OiBpZm5ldDogVXNlIGlm X2xpbmtfc3RhdGUgc25hcHNob3QgdG8gaW52b2tlIGlmbmV0X2xpbmtfZXZlbnQgKGF1dGhvcmVk IGJ5IHNlcGhlKS4KCkNIQU5HRUQgUFJJT1IgVE8gQ09NTUlUCiAgaHR0cHM6Ly9yZXZpZXdzLmZy ZWVic2Qub3JnL0Q4MjE0P3ZzPTIxMjM5JmlkPTIxMjg2I3RvYwoKUkVQT1NJVE9SWQogIHJTIEZy ZWVCU0Qgc3JjIHJlcG9zaXRvcnkKCkNIQU5HRVMgU0lOQ0UgTEFTVCBVUERBVEUKICBodHRwczov L3Jldmlld3MuZnJlZWJzZC5vcmcvRDgyMTQ/dnM9MjEyMzkmaWQ9MjEyODYKClJFVklTSU9OIERF VEFJTAogIGh0dHBzOi8vcmV2aWV3cy5mcmVlYnNkLm9yZy9EODIxNAoKQUZGRUNURUQgRklMRVMK ICBoZWFkL3N5cy9uZXQvaWYuYwoKQ0hBTkdFIERFVEFJTFMKCmRpZmYgLS1naXQgYS9oZWFkL3N5 cy9uZXQvaWYuYyBiL2hlYWQvc3lzL25ldC9pZi5jCi0tLSBhL2hlYWQvc3lzL25ldC9pZi5jCisr KyBiL2hlYWQvc3lzL25ldC9pZi5jCkBAIC0yMjA2LDcgKzIyMDYsNyBAQAogCWlmIChsb2dfbGlu a19zdGF0ZV9jaGFuZ2UpCiAJCWxvZyhMT0dfTk9USUNFLCAiJXM6IGxpbmsgc3RhdGUgY2hhbmdl ZCB0byAlc1xuIiwgaWZwLT5pZl94bmFtZSwKIAkJICAgIChsaW5rX3N0YXRlID09IExJTktfU1RB VEVfVVApID8gIlVQIiA6ICJET1dOIiApOwotCUVWRU5USEFORExFUl9JTlZPS0UoaWZuZXRfbGlu a19ldmVudCwgaWZwLCBpZnAtPmlmX2xpbmtfc3RhdGUpOworCUVWRU5USEFORExFUl9JTlZPS0Uo aWZuZXRfbGlua19ldmVudCwgaWZwLCBsaW5rX3N0YXRlKTsKIAlDVVJWTkVUX1JFU1RPUkUoKTsK IH0KIAoKCgpFTUFJTCBQUkVGRVJFTkNFUwogIGh0dHBzOi8vcmV2aWV3cy5mcmVlYnNkLm9yZy9z ZXR0aW5ncy9wYW5lbC9lbWFpbHByZWZlcmVuY2VzLwoKVG86IHNlcGhlcm9zYV9nbWFpbC5jb20s IGdsZWJpdXMsIGFkcmlhbiwgZ25uLCBieiwgYWUKQ2M6IGFlLCBmcmVlYnNkLW5ldC1saXN0Cg== --b1_1f3b44c43b6a03a18bed63e9d5751f0b Content-Type: text/x-patch; charset=utf-8; name="D8214.21286.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="D8214.21286.patch" ZGlmZiAtLWdpdCBhL2hlYWQvc3lzL25ldC9pZi5jIGIvaGVhZC9zeXMvbmV0L2lmLmMKLS0tIGEv aGVhZC9zeXMvbmV0L2lmLmMKKysrIGIvaGVhZC9zeXMvbmV0L2lmLmMKQEAgLTIyMDYsNyArMjIw Niw3IEBACiAJaWYgKGxvZ19saW5rX3N0YXRlX2NoYW5nZSkKIAkJbG9nKExPR19OT1RJQ0UsICIl czogbGluayBzdGF0ZSBjaGFuZ2VkIHRvICVzXG4iLCBpZnAtPmlmX3huYW1lLAogCQkgICAgKGxp bmtfc3RhdGUgPT0gTElOS19TVEFURV9VUCkgPyAiVVAiIDogIkRPV04iICk7Ci0JRVZFTlRIQU5E TEVSX0lOVk9LRShpZm5ldF9saW5rX2V2ZW50LCBpZnAsIGlmcC0+aWZfbGlua19zdGF0ZSk7CisJ RVZFTlRIQU5ETEVSX0lOVk9LRShpZm5ldF9saW5rX2V2ZW50LCBpZnAsIGxpbmtfc3RhdGUpOwog CUNVUlZORVRfUkVTVE9SRSgpOwogfQogCgo= --b1_1f3b44c43b6a03a18bed63e9d5751f0b-- From owner-freebsd-net@freebsd.org Wed Oct 12 03:52:52 2016 Return-Path: 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 BCCAEC0B335 for ; Wed, 12 Oct 2016 03:52:52 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 9BB4E925 for ; Wed, 12 Oct 2016 03:52:52 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) Received: by mailman.ysv.freebsd.org (Postfix) id 9B15DC0B333; Wed, 12 Oct 2016 03:52:52 +0000 (UTC) Delivered-To: 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 9AB96C0B332 for ; Wed, 12 Oct 2016 03:52:52 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) Received: from nm6-vm3.bullet.mail.gq1.yahoo.com (nm6-vm3.bullet.mail.gq1.yahoo.com [98.136.218.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7498F922 for ; Wed, 12 Oct 2016 03:52:52 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1476244220; bh=o7N7dHMBJI4Q4XA+R6+yjKKR5hS1dUNf06m6um+KX0w=; h=Date:From:To:In-Reply-To:References:Subject:From:Subject; b=olN0m4ww9CzhKlRFvHnrAG52rRDErj9TOuugbQWhDISHhoxu+Bm4YC4JpKEFsoTByNZAFuwhKM9o9X5Iy81bO0f60+lKz91i+Nam72N1Y2xjbcp6bHseX587REGmr58mMocI9KllP/7Tovj5Uo3Wf7RSq/FPkYrlOHD+6gVThZdGIYoOP2JvBjkKKldGmIsnLbR0ZvB7HntZTA5WQxAb4C6p2d0oXl0zyULSypCanFrze8S5pPbmX2tV0/DRxt6Votc9m7T+RpFBHli3B4D+V/WOR+pJPgWR6ak4PpTeprVHVnYSumLvWcb4kCLzxf0WviB0bsbNGBWOXezL+gGkZA== Received: from [216.39.60.180] by nm6.bullet.mail.gq1.yahoo.com with NNFMP; 12 Oct 2016 03:50:20 -0000 Received: from [208.71.42.193] by tm16.bullet.mail.gq1.yahoo.com with NNFMP; 12 Oct 2016 03:50:20 -0000 Received: from [127.0.0.1] by smtp204.mail.gq1.yahoo.com with NNFMP; 12 Oct 2016 03:50:20 -0000 X-Yahoo-Newman-Id: 288588.65595.bm@smtp204.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 8HwH1fwVM1nPlBoJ_T6ibqHubxzPycYvGnBoZiEZWdu.KPE vvc4sz0ym2uqVxe2bmQqSZoGtEd11TNmAbxBr3XCudBjzvY5mQlQH8zRMmiT b66GYu0rIC76SArNSLHTI033SF2cxvGBdg6ULkoZO2l07j7_C2I_Go.SR7cJ hGnp.d.CoNiv7_rC8jGicd8fbboVbrs.686kTjzrO2P5O_BJue.AN7wzpb9G o7JcJZiGNa6FB3kSTEfkydRGGr4amXZHabWbHrgV7O19IgP0U280h7voy.wC 6xgVrCBGluD4MesIW7S3VDbGAnwulAxSGCTvyyr23FOSxPg9FwPDFZBin0u6 1a4vI5yQAbAO_sYEfFxuyR0lOFZHNTAhDyCw5sfDgx0RJcvI4TAlcaweV8cU ooOV.E97o_Av1nNuxO5hFViKDRYWGqncllA5jgqjL5udxe62hd5y7MJ_K58. 38gIqFvaDYSeovxokpTUyMo0vZIsJ7qfk1lOeBptRN3jN8ZIQbCqVutiWGyo a5UmuRZjU2TUAQf5rFRvY74SGFDRWnsfnPbS4D8DvEM2uWfIfGzc8 X-Yahoo-SMTP: fRRiyyGswBB1GYfBhw8frTz_QYRdpxY- Date: Wed, 12 Oct 2016 03:50:19 +0000 (UTC) From: Donald Baud To: Message-ID: In-Reply-To: References: <57FC859F.5000200@grosbein.net> Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. MIME-Version: 1.0 X-Mailer: Outlook for iOS and Android Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Oct 2016 03:52:52 -0000 I've been plagued with these =3Ddaily=3D panics until I tried the following= recipes and the server has been up for 30 days so far:=C2=A0 Normally I should expermient more to see which one of the recipes is really= the fix, but I'm just glad that the server is stable for now. recipe-1: Don't let mpd5 start automatically when server boots:i.e. in: /et= c/rc.conf=C2=A0mpd5_enable=3D"NO"and wait about 5 minutes after server boot= s then issue:=C2=A0/usr/local/etc/rc.d/mpd5 onestart recipe-2: recompile the kernel with the NETGRAPH_DEBUG option:options = NETGRAPH =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0options NETGRAPH_DEBUG =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0options NETGRAPH_KSOCKET=C2=A0= options NETGRAPH_L2TPoptions NETGRAPH_SOCKEToptions = NETGRAPH_TEEoptions NETGRAPH_VJCoptions NETGRAPH_PPPoption= s NETGRAPH_IFACEoptions NETGRAPH_MPPC_COMPRESSIONoptions = NETGRAPH_MPPC_ENCRYPTIONoptions NETGRAPH_TCPMSSoptions = IPFIREWALL recipe-3: recompile the kernel and disable the IPv6 and SCTP options:noopti= ons INET6nooptions SCTP recipe-4: Don't use any of the sysctl optimizations=C2=A0in other words I c= ommented out all values in sysctl.conf:# net.graph.maxdgram=3D20480 (this = is the default)# net.graph.recvspace=3D20480 (this is the default) recipe-5: Don't use any of the loader.conf optimizationsin other words I co= mmented out all values in loader.conf# net.graph.maxdata=3D4096 (this is t= he default)# net.graph.maxalloc=3D4096 (this is the default) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3DIn my case, I had the panics with 10.3 and 11-PRERELEA= SE11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #2 r305587 With those recipes, I have been running without any crash for a month and c= ounting. That's 300 l2tp tunnels and 1400 l2tp sessions generating 700Mbit= /s. =09=09_____________________________ From: Cassiano Peixoto Sent: Tuesday, October 11, 2016 07:30 Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. To: Eugene Grosbein Cc: , =D0=90=D0=BD=D0=B4=D1=80=D0=B5=D0=B9 =D0=9B=D0=B5= =D1=83=D1=88=D0=BA=D0=B8=D0=BD Hi, There are many users complaining about this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114 I've been dealing with this issue for one year with no solution. mpd5 as pppoe server on FreeBSD is useless with this bug. I really would like to see it working again, i think it's quite important to both project and many users. Thanks. On Tue, Oct 11, 2016 at 3:24 AM, Eugene Grosbein wrote= : > 11.10.2016 11:02, =D0=90=D0=BD=D0=B4=D1=80=D0=B5=D0=B9 =D0=9B=D0=B5=D1=83= =D1=88=D0=BA=D0=B8=D0=BD =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >> Hello. I have problem with "FreeBSD nas 10.3-RELEASE FreeBSD 10.3-RELEAS= E >> #0: Fri Oct 7 21:12:56 YEKT 2016 nas@nas:/usr/obj/usr/src/sys/nasv3 >> amd64" >> >> Kernel panic is repeated at intervals of 2-3 days. At first I thought th= at >> the problem is in the hardware, but the problem did not go away after >> replacing the server platform. >> >> Coredumps and more info on link >> https://drive.google.com/open?id=3D0BxciMy2q7ZjTTkIxem9wTE1tM2M >> >> Sorry for my english. >> I'll wait for an answer. >> > > This is known and long-stanging problem in the FreeBSD network stack. > It shows up when you have lots of network interfaced created/removed > frequently > like in your case of Network Access Server (PPtP, PPPoE etc). > > Generally, people run into this problem using mpd5 network daemon. > mpd5 uses NETGRAPH kernel subsystem to process traffic and > if an interface disappears (f.e., ,user disconnected) > while kernel still processes traffic obtained from this interface, it > panices. > > There were lots of reports of this problem. Noone seems to be working on > it at the moment. > You should fill a PR using Bugzilla and attach your logs to it. > > Eugene Grosbein > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" =09 From owner-freebsd-net@freebsd.org Wed Oct 12 03:59:17 2016 Return-Path: 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 2F5BCC0B4E4 for ; Wed, 12 Oct 2016 03:59:17 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0DEBCAE3 for ; Wed, 12 Oct 2016 03:59:17 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) Received: by mailman.ysv.freebsd.org (Postfix) id 0A580C0B4E3; Wed, 12 Oct 2016 03:59:17 +0000 (UTC) Delivered-To: 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 09F51C0B4E2 for ; Wed, 12 Oct 2016 03:59:17 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) Received: from nm41-vm5.bullet.mail.gq1.yahoo.com (nm41-vm5.bullet.mail.gq1.yahoo.com [67.195.87.92]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D7AEBAE2 for ; Wed, 12 Oct 2016 03:59:16 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1476244755; bh=WEmjCXG5f5cjTuDYYMDOc0/5gXZGZ89FhtjrVI/tOmU=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=th+G26hnT+6uZgkVew55GieOS/HR0IMvQq07TKTzgMZZGJhtTTrs3o38QrbBjMdii/qnPf3TAgTBGy9bpPx3Ju/rWYqoCnF1AB9crK5sofbyiPKnacvKCWptZcpXpLAVTD3/vUh+Ws3bvDfz/ymTkchq/XpgnptWsEZimlnj2pu1oI8lbH7w/RBx4IdWP5Fwp088qbEPpEL+1XtWRltWU6tfE8iU1Rjh+u0Ysw3ajJZyVqMiKaZztE9N7jzQkX28luPg3yLui93jgXePwxiM9fBLAAY4cWvSVwCkkpnoy5eVry0kEg/0b7QshttkdK5LhsfIqeVlzTWtWG/10BESpg== Received: from [127.0.0.1] by nm41.bullet.mail.gq1.yahoo.com with NNFMP; 12 Oct 2016 03:59:15 -0000 Received: from [98.137.12.62] by nm41.bullet.mail.gq1.yahoo.com with NNFMP; 12 Oct 2016 03:56:15 -0000 Received: from [98.139.170.180] by tm7.bullet.mail.gq1.yahoo.com with NNFMP; 12 Oct 2016 03:56:15 -0000 Received: from [98.139.212.240] by tm23.bullet.mail.bf1.yahoo.com with NNFMP; 12 Oct 2016 03:56:15 -0000 Received: from [127.0.0.1] by omp1049.mail.bf1.yahoo.com with NNFMP; 12 Oct 2016 03:56:15 -0000 X-Yahoo-Newman-Property: ymail-4 X-Yahoo-Newman-Id: 391573.37393.bm@omp1049.mail.bf1.yahoo.com X-YMail-OSG: FpTv8n8VM1lv5tvjNpeNy7XU5bhaSbOTFoK2bUgtr0pN.hIaQdIIZwyWGsNWMKk ppJN8w5Kwwg38ji0qFplmkG6PrmQECD1joOc_6Hl1wtPM83KvNXeds9PZZFM742PS6i4il1ynT9Z WYMu5s_HiHaPXQFqmpJ7zwMuguYZkka2lA_rN2nkLQ.R3mC8UuFZf3AXDwzGFP7KEi1bb2oTOIlo _qMwzi24STFiAg6xNENgv.Fl8YdKhq9zxkvyQfwUY5JPVmMZtLTdcakm6GjQFGoAG0ZuQ1OTURI3 vLFVylccemBjXWMGmyRp9lT3QqCVlZ0Pa8PMqt81mTU1CGOfazfy1OKzybYBoXKzKNW9OCocqoWi zh2igyW2r0r8k.rrTJqLeKQj9ii4LVoifh9DXqQFB4o7jr_SY4f.i0T3qUjeBc4ck57PYRJNvBlT kL2R0BDS6HVVXiwuELTj10jYDk5CkrEF1ytnhcmlOta9iAmiCUh_15RZECKjf5F8hxWkJx4oYYJb M40uswtufZk1nCWGJw.V7N8FVJuczQk_pMeQZzwA- Received: from jws106182.mail.bf1.yahoo.com by sendmailws118.mail.bf1.yahoo.com; Wed, 12 Oct 2016 03:56:15 +0000; 1476244575.026 Date: Wed, 12 Oct 2016 03:56:08 +0000 (UTC) From: Reply-To: To: "net@freebsd.org" Message-ID: <2033449965.65391.1476244568309@mail.yahoo.com> In-Reply-To: References: <57FC859F.5000200@grosbein.net> Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Oct 2016 03:59:17 -0000 I've been plagued with these =3Ddaily=3D panics until I tried the following= recipes and the server has been up for 30 days so far:=20 Normally I should expermient more to see which one of the receipes is reall= y the fix, but I'm just glad that the server is stable for now. recipe-1: Don't let mpd5 start automatically when server boots: i.e. in: /etc/rc.conf=20 mpd5_enable=3D"NO" and wait about 5 minutes after server boots then issue:=20 /usr/local/etc/rc.d/mpd5 onestart recipe-2: recompile the kernel with the NETGRAPH_DEBUG option: options NETGRAPH=20 options NETGRAPH_DEBUG=20 options NETGRAPH_KSOCKET=20 options NETGRAPH_L2TP options NETGRAPH_SOCKET options NETGRAPH_TEE options NETGRAPH_VJC options NETGRAPH_PPP options NETGRAPH_IFACE options NETGRAPH_MPPC_COMPRESSION options NETGRAPH_MPPC_ENCRYPTION options NETGRAPH_TCPMSS options IPFIREWALL recipe-3: recompile the kernel and disable the IPv6 and SCTP options: nooptions INET6 nooptions SCTP recipe-4: Don't use any of the sysctl optimizations=20 in other words I commented out all values in sysctl.conf: # net.graph.maxdgram=3D20480 (this is the default) # net.graph.recvspace=3D20480 (this is the default) recipe-5: Don't use any of the loader.conf optimizations in other words I commented out all values in loader.conf # net.graph.maxdata=3D4096 (this is the default) # net.graph.maxalloc=3D4096 (this is the default) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D In my case, I had the panics with 10.3 and 11-PRERELEASE 11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #2 r305587 With those recipes, I have been running without any crash for a month and c= ounting. Thats' 300 l2tp tunnels and 1400 l2tp sessions generating 700Mbit= /s. -DBaud=20 On Tuesday, October 11, 2016 7:30 AM, Cassiano Peixoto wrote: Hi, There are many users complaining about this: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114 I've been dealing with this issue for one year with no solution. mpd5 as pppoe server on FreeBSD is useless with this bug. I really would like to see it working again, i think it's quite important to both project and many users. Thanks. On Tue, Oct 11, 2016 at 3:24 AM, Eugene Grosbein wrote= : > 11.10.2016 11:02, =D0=90=D0=BD=D0=B4=D1=80=D0=B5=D0=B9 =D0=9B=D0=B5=D1=83= =D1=88=D0=BA=D0=B8=D0=BD =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >> Hello. I have problem with "FreeBSD nas 10.3-RELEASE FreeBSD 10.3-RELEAS= E >> #0: Fri Oct 7 21:12:56 YEKT 2016 nas@nas:/usr/obj/usr/src/sys/nasv3 >> amd64" >> >> Kernel panic is repeated at intervals of 2-3 days. At first I thought th= at >> the problem is in the hardware, but the problem did not go away after >> replacing the server platform. >> >> Coredumps and more info on link >> https://drive.google.com/open?id=3D0BxciMy2q7ZjTTkIxem9wTE1tM2M >> >> Sorry for my english. >> I'll wait for an answer. >> > > This is known and long-stanging problem in the FreeBSD network stack. > It shows up when you have lots of network interfaced created/removed > frequently > like in your case of Network Access Server (PPtP, PPPoE etc). > > Generally, people run into this problem using mpd5 network daemon. > mpd5 uses NETGRAPH kernel subsystem to process traffic and > if an interface disappears (f.e., ,user disconnected) > while kernel still processes traffic obtained from this interface, it > panices. > > There were lots of reports of this problem. Noone seems to be working on > it at the moment. > You should fill a PR using Bugzilla and attach your logs to it. > > Eugene Grosbein > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@freebsd.org Wed Oct 12 05:13:45 2016 Return-Path: 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 3EB48C0DB91 for ; Wed, 12 Oct 2016 05:13:45 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2929E1B3A for ; Wed, 12 Oct 2016 05:13:45 +0000 (UTC) (envelope-from julian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 288AEC0DB90; Wed, 12 Oct 2016 05:13:45 +0000 (UTC) Delivered-To: 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 2831EC0DB8F for ; Wed, 12 Oct 2016 05:13:45 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EE43A1B39 for ; Wed, 12 Oct 2016 05:13:44 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from julian-mbp3.pixel8networks.com (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u9C5Dg9U083276 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 11 Oct 2016 22:13:43 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. To: donaldbaud@yahoo.com, "net@freebsd.org" References: <57FC859F.5000200@grosbein.net> <2033449965.65391.1476244568309@mail.yahoo.com> From: Julian Elischer Message-ID: Date: Tue, 11 Oct 2016 22:13:37 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <2033449965.65391.1476244568309@mail.yahoo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Oct 2016 05:13:45 -0000 On 11/10/2016 8:56 PM, Donald Baud via freebsd-net wrote: > I've been plagued with these =daily= panics until I tried the following recipes and the server has been up for 30 days so far: > > Normally I should expermient more to see which one of the receipes is really the fix, but I'm just glad that the server is stable for now. this is really great information. It makes debugging a lot more possible. I know it is a hard question, but do you have a way to simulate this workload? I have no real way to simulate this kind of workload > > > recipe-1: Don't let mpd5 start automatically when server boots: > i.e. in: /etc/rc.conf > mpd5_enable="NO" > and wait about 5 minutes after server boots then issue: > /usr/local/etc/rc.d/mpd5 onestart > > > recipe-2: recompile the kernel with the NETGRAPH_DEBUG option: > options NETGRAPH > options NETGRAPH_DEBUG > options NETGRAPH_KSOCKET > options NETGRAPH_L2TP > options NETGRAPH_SOCKET > options NETGRAPH_TEE > options NETGRAPH_VJC > options NETGRAPH_PPP > options NETGRAPH_IFACE > options NETGRAPH_MPPC_COMPRESSION > options NETGRAPH_MPPC_ENCRYPTION > options NETGRAPH_TCPMSS > options IPFIREWALL > > recipe-3: recompile the kernel and disable the IPv6 and SCTP options: > nooptions INET6 > nooptions SCTP > > recipe-4: Don't use any of the sysctl optimizations > in other words I commented out all values in sysctl.conf: > # net.graph.maxdgram=20480 (this is the default) > # net.graph.recvspace=20480 (this is the default) > > recipe-5: Don't use any of the loader.conf optimizations > in other words I commented out all values in loader.conf > # net.graph.maxdata=4096 (this is the default) > # net.graph.maxalloc=4096 (this is the default) > > ================================ > In my case, I had the panics with 10.3 and 11-PRERELEASE > 11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #2 r305587 > > With those recipes, I have been running without any crash for a month and counting. Thats' 300 l2tp tunnels and 1400 l2tp sessions generating 700Mbit/s. > > > -DBaud > > > On Tuesday, October 11, 2016 7:30 AM, Cassiano Peixoto wrote: > Hi, > > There are many users complaining about this: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114 > > I've been dealing with this issue for one year with no solution. mpd5 as > pppoe server on FreeBSD is useless with this bug. > > I really would like to see it working again, i think it's quite important > to both project and many users. > > Thanks. > > On Tue, Oct 11, 2016 at 3:24 AM, Eugene Grosbein wrote: > >> 11.10.2016 11:02, Андрей Леушкин пишет: >> >>> Hello. I have problem with "FreeBSD nas 10.3-RELEASE FreeBSD 10.3-RELEASE >>> #0: Fri Oct 7 21:12:56 YEKT 2016 nas@nas:/usr/obj/usr/src/sys/nasv3 >>> amd64" >>> >>> Kernel panic is repeated at intervals of 2-3 days. At first I thought that >>> the problem is in the hardware, but the problem did not go away after >>> replacing the server platform. >>> >>> Coredumps and more info on link >>> https://drive.google.com/open?id=0BxciMy2q7ZjTTkIxem9wTE1tM2M >>> >>> Sorry for my english. >>> I'll wait for an answer. >>> >> This is known and long-stanging problem in the FreeBSD network stack. >> It shows up when you have lots of network interfaced created/removed >> frequently >> like in your case of Network Access Server (PPtP, PPPoE etc). >> >> Generally, people run into this problem using mpd5 network daemon. >> mpd5 uses NETGRAPH kernel subsystem to process traffic and >> if an interface disappears (f.e., ,user disconnected) >> while kernel still processes traffic obtained from this interface, it >> panices. >> >> There were lots of reports of this problem. Noone seems to be working on >> it at the moment. >> You should fill a PR using Bugzilla and attach your logs to it. >> >> Eugene Grosbein >> >> >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > From owner-freebsd-net@freebsd.org Wed Oct 12 12:07:54 2016 Return-Path: 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 2EC46C0EB64 for ; Wed, 12 Oct 2016 12:07:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 1E43E6AD for ; Wed, 12 Oct 2016 12:07:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9CC7rLK041401 for ; Wed, 12 Oct 2016 12:07:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 138782] [panic] sbflush_internal: cc 0 || mb 0xffffff004127b000 || mbcnt 2304 Date: Wed, 12 Oct 2016 12:07:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: john@saltant.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Oct 2016 12:07:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D138782 John W. O'Brien changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |john@saltant.com --- Comment #7 from John W. O'Brien --- I just encountered this panic on 10-STABLE r306933 with under two days of uptime. I upgraded a few days ago from r301164 which had been running continuously for over 120 days. Unfortunately I don't have a core, but I wo= uld be glad to provide any other information and am interested in pursuing a fi= x. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 12 14:03:14 2016 Return-Path: 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 B4629C0E6EE for ; Wed, 12 Oct 2016 14:03:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 A3E29200 for ; Wed, 12 Oct 2016 14:03:14 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9CE3EbR081154 for ; Wed, 12 Oct 2016 14:03:14 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213410] [carp] service netif restart causes hang only when carp is enabled Date: Wed, 12 Oct 2016 14:03:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Oct 2016 14:03:14 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213410 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-net@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 12 14:54:07 2016 Return-Path: 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 5956BC0F42A for ; Wed, 12 Oct 2016 14:54:07 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 38F3D1D6 for ; Wed, 12 Oct 2016 14:54:07 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) Received: by mailman.ysv.freebsd.org (Postfix) id 35700C0F429; Wed, 12 Oct 2016 14:54:07 +0000 (UTC) Delivered-To: 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 3361FC0F428 for ; Wed, 12 Oct 2016 14:54:07 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) Received: from nm22-vm8.bullet.mail.gq1.yahoo.com (nm22-vm8.bullet.mail.gq1.yahoo.com [98.136.217.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 039A91D5 for ; Wed, 12 Oct 2016 14:54:06 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1476283887; bh=D+IihGdmm6CRuUF18KCZuJ5BrDcKxYVadQzmjZFGp+E=; h=Subject:To:References:From:Date:In-Reply-To:From:Subject; b=Gu4NGbrv4HWjlTQ6OGa6Vg/yz7yL3YOyefIr0z4wAzKY/XElbSGp3kbb6aMKoCpyBimkJtOawAACXmg0O+Jzx8ux6u8CTIlF+hh1+7rm5ITkhvS0nEeJ1/1jnC7tGe3bd9opWduaaThZVbmaHS6hce3XoWWJR+RgD63eN62iC+Wk7ftJRm1FKb9vhjix/TWOU3l6ttX3saJ8D4EJXsS0ng0e06waiRRQiUKGINBsjIqEjqv8L8Qqg5UrnC9exivDDN4RoOE4khmUGFhf9p9jBnKtMfUPTHoJ2Rkkj9zvbuoTinLhM+8QZEt2sqCSd5Qzzb6aoqqfcMDyKp8Rno3uRQ== Received: from [98.137.12.58] by nm22.bullet.mail.gq1.yahoo.com with NNFMP; 12 Oct 2016 14:51:27 -0000 Received: from [208.71.42.213] by tm3.bullet.mail.gq1.yahoo.com with NNFMP; 12 Oct 2016 14:51:26 -0000 Received: from [127.0.0.1] by smtp224.mail.gq1.yahoo.com with NNFMP; 12 Oct 2016 14:51:26 -0000 X-Yahoo-Newman-Id: 958998.41214.bm@smtp224.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: RmaPDhkVM1kmNmkJPi5lz0eUzf915AuT_ybQftD7DgQv8v0 AkU4SlKtsJyRtUAbfCA5spuryREm5xrJNuJi6rSFYgcV.OQIyRdbwCaWA7Lr zHPnLs4ZWotTUtNCR8N1d2oZJL3spb9cGdQhgnQkBGGLlRHkHyVAEKneGGj. Vy.x.9wSwTn.My2MolfOXSOqoKKoU1tvo7gYkgurPksvK5wY53kCQ4EOKjj6 OtPkpSmRSDgUyj93vyW.xBJvtTsVqqd6ZxzUAWLOa42U8mMXG0gfu5rhdKP1 tOIQtWwEqi_MMiF14c2bT.8sd0fpqYpcaW1Jd0ifbVrXlPKh_E8gYTJrRAmn NFUV2TmwYiGpVcENHyZUtOIWw0Zt.NYRbjcXyJAUXVW087cmL5Kc8dWB0UtW Eauo4IDD33IPc32BLZYDgaMHdrq4tpxxhkvbHiAvmk5mse0JFyZKLuicIA6y y6w8XaShftYQzeqED3EdT_F_tNF2rZLvADSeTxW32eaHcxZPENLQObgnUO2H JR6tZllghxrxFei9.7V8nYlMzB8lUVuvCj0g6zFsdYpo7IZ0W5HX4YanB X-Yahoo-SMTP: fRRiyyGswBB1GYfBhw8frTz_QYRdpxY- Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. To: "net@freebsd.org" References: <57FC859F.5000200@grosbein.net> <2033449965.65391.1476244568309@mail.yahoo.com> From: Donald Baud Message-ID: <86183ea5-5855-5fb3-22f6-d25454859186@yahoo.com> Date: Wed, 12 Oct 2016 10:51:25 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Oct 2016 14:54:07 -0000 On 10/12/16 1:13 AM, Julian Elischer wrote: > On 11/10/2016 8:56 PM, Donald Baud via freebsd-net wrote: >> I've been plagued with these =daily= panics until I tried the >> following recipes and the server has been up for 30 days so far: >> >> Normally I should expermient more to see which one of the receipes is >> really the fix, but I'm just glad that the server is stable for now. > > this is really great information. > It makes debugging a lot more possible. > I know it is a hard question, but do you have a way to simulate this > workload? > > I have no real way to simulate this kind of workload Sadly, I don't have a way to simulate the workload but I am very interested to help fix these crashes since as Cassiano said, this makes mpd5/freebsd useless for pppoe/l2tp termination. At this point, I would suggest that Cassiano and Андрей confirm that they don't get panics when they apply the recipes that I am using. I am still running many other cisco-vpdn gateways that I would convert into mpd5/freebsd but my plan was stalled with the daily crashes. I'll wait a couple of weeks to be sure that my recipes are a valid workaround before converting my remaining cisco gateways to mpd5. -Dbaud >> >> >> recipe-1: Don't let mpd5 start automatically when server boots: >> i.e. in: /etc/rc.conf >> mpd5_enable="NO" >> and wait about 5 minutes after server boots then issue: >> /usr/local/etc/rc.d/mpd5 onestart >> >> >> recipe-2: recompile the kernel with the NETGRAPH_DEBUG option: >> options NETGRAPH >> options NETGRAPH_DEBUG >> options NETGRAPH_KSOCKET >> options NETGRAPH_L2TP >> options NETGRAPH_SOCKET >> options NETGRAPH_TEE >> options NETGRAPH_VJC >> options NETGRAPH_PPP >> options NETGRAPH_IFACE >> options NETGRAPH_MPPC_COMPRESSION >> options NETGRAPH_MPPC_ENCRYPTION >> options NETGRAPH_TCPMSS >> options IPFIREWALL >> >> recipe-3: recompile the kernel and disable the IPv6 and SCTP options: >> nooptions INET6 >> nooptions SCTP >> >> recipe-4: Don't use any of the sysctl optimizations >> in other words I commented out all values in sysctl.conf: >> # net.graph.maxdgram=20480 (this is the default) >> # net.graph.recvspace=20480 (this is the default) >> >> recipe-5: Don't use any of the loader.conf optimizations >> in other words I commented out all values in loader.conf >> # net.graph.maxdata=4096 (this is the default) >> # net.graph.maxalloc=4096 (this is the default) >> >> ================================ >> In my case, I had the panics with 10.3 and 11-PRERELEASE >> 11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #2 r305587 >> >> With those recipes, I have been running without any crash for a month >> and counting. Thats' 300 l2tp tunnels and 1400 l2tp sessions >> generating 700Mbit/s. >> >> >> -DBaud >> >> >> On Tuesday, October 11, 2016 7:30 AM, Cassiano Peixoto >> wrote: >> Hi, >> >> There are many users complaining about this: >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114 >> >> I've been dealing with this issue for one year with no solution. mpd5 as >> pppoe server on FreeBSD is useless with this bug. >> >> I really would like to see it working again, i think it's quite >> important >> to both project and many users. >> >> Thanks. >> >> On Tue, Oct 11, 2016 at 3:24 AM, Eugene Grosbein >> wrote: >> >>> 11.10.2016 11:02, Андрей Леушкин пишет: >>> >>>> Hello. I have problem with "FreeBSD nas 10.3-RELEASE FreeBSD >>>> 10.3-RELEASE >>>> #0: Fri Oct 7 21:12:56 YEKT 2016 nas@nas:/usr/obj/usr/src/sys/nasv3 >>>> amd64" >>>> >>>> Kernel panic is repeated at intervals of 2-3 days. At first I >>>> thought that >>>> the problem is in the hardware, but the problem did not go away after >>>> replacing the server platform. >>>> >>>> Coredumps and more info on link >>>> https://drive.google.com/open?id=0BxciMy2q7ZjTTkIxem9wTE1tM2M >>>> >>>> Sorry for my english. >>>> I'll wait for an answer. >>>> >>> This is known and long-stanging problem in the FreeBSD network stack. >>> It shows up when you have lots of network interfaced created/removed >>> frequently >>> like in your case of Network Access Server (PPtP, PPPoE etc). >>> >>> Generally, people run into this problem using mpd5 network daemon. >>> mpd5 uses NETGRAPH kernel subsystem to process traffic and >>> if an interface disappears (f.e., ,user disconnected) >>> while kernel still processes traffic obtained from this interface, it >>> panices. >>> >>> There were lots of reports of this problem. Noone seems to be >>> working on >>> it at the moment. >>> You should fill a PR using Bugzilla and attach your logs to it. >>> >>> Eugene Grosbein >>> From owner-freebsd-net@freebsd.org Wed Oct 12 19:24:19 2016 Return-Path: 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 607C1C0FE4C for ; Wed, 12 Oct 2016 19:24:19 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3CC2A75F for ; Wed, 12 Oct 2016 19:24:19 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 3C0AAC0FE45; Wed, 12 Oct 2016 19:24:19 +0000 (UTC) Delivered-To: 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 3B8E3C0FE44 for ; Wed, 12 Oct 2016 19:24:19 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (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 DEDD2754 for ; Wed, 12 Oct 2016 19:24:18 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by mail-yw0-x234.google.com with SMTP id t192so39508494ywf.0 for ; Wed, 12 Oct 2016 12:24:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dzrto6iOdU2evHhBWVY2Qrg8tZes9dgEEMJNBox9ums=; b=V8F0M3ScQJ9SRZP3sW7dk1Q8wVLsjLHO6reTtYmMGwPNuhAkriWHJqNexb9EQ4ZLfw sAXTgcFGY44J9QdRFERtwzaIM6UzPrsUoK9zKBF6Oq0tozar4B8/COQXOvUe6p66NEVe lJyxrQLUvZPz9Cj+qbyKt4lvsEJ3W1ti8w46if3x+S4t47saDgnlD4IBXVO3079AP7Or Bvr9EyOfDFrbAPmCWPbfGZxwYKAdeKN32llLZR158G5XnkyKm5pqOCyjQMq/xQTQ5iUe CJHFjwpcjsjnfDGk9TtPCActi9lGZ4jNM71QdJsjr/cqHLssS2PteTpcFGmUKlPV7VqC q+dQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dzrto6iOdU2evHhBWVY2Qrg8tZes9dgEEMJNBox9ums=; b=CmKHuLfPep2uSf75Zeh2/3Mb9jNx7OPNPXWu03NuarG67FxJ2ZRJJlmaQJX6n8wUJc 9jBzBAXtF0fo8fku/HNwVekFvYQAXIyKvuMG12jst4QCS07J0FWlA4g5cWGQB1DPhyrz tpqjx5NduU9QtWIx0ktFenrjj38umrdYl6XX7IAzifrzTdMr7po81N2OZJKNayTfGfkz zhvrK13XimLnxJKI3fIzADzlSrQedTRDrk0+ZXphgLvjJMYL0D7ZeaIIVCxC6rSfdHtL Jy4CphPPjwcwsa+k7Ce7PxYwMLpzZxaSlDjb5oHWLMMAhDGwoGQGEzS6evQedouIUg1s rVLQ== X-Gm-Message-State: AA6/9RnNqTUPSkQ4q5twx0A4LzgKft/3Q1qdUF2NEVgWYpIesZtIfMawpZ9Meo6ylWeDrh7CoyPNlfYdZUf7mw== X-Received: by 10.129.120.74 with SMTP id t71mr2470948ywc.51.1476300257944; Wed, 12 Oct 2016 12:24:17 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.161.37 with HTTP; Wed, 12 Oct 2016 12:24:17 -0700 (PDT) In-Reply-To: <86183ea5-5855-5fb3-22f6-d25454859186@yahoo.com> References: <57FC859F.5000200@grosbein.net> <2033449965.65391.1476244568309@mail.yahoo.com> <86183ea5-5855-5fb3-22f6-d25454859186@yahoo.com> From: Zaphod Beeblebrox Date: Wed, 12 Oct 2016 15:24:17 -0400 Message-ID: Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. To: Donald Baud Cc: "net@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Oct 2016 19:24:19 -0000 While my mp5 servers are possibly less busy (I havn't had common crashes), I have noticed a "group" of problems. 1. The carrier dropping communication (ie: fiber cut or l2 switch breakage) of the L2TP streams can leave mpd5 in a state where it will not die and will not destroy interfaces (requires reboot to clear). 2. There are race conditions between quagga and mpd5 for adding/dropping routes. 3. if A is a pppoe client and B is the mpd5 server, A cannot access TCP services on B. It can access tcp services _beyond_ B, but not on B. (there is a ticket open for this). On Wed, Oct 12, 2016 at 10:51 AM, Donald Baud via freebsd-net < freebsd-net@freebsd.org> wrote: > > On 10/12/16 1:13 AM, Julian Elischer wrote: > >> On 11/10/2016 8:56 PM, Donald Baud via freebsd-net wrote: >> >>> I've been plagued with these =3Ddaily=3D panics until I tried the follo= wing >>> recipes and the server has been up for 30 days so far: >>> >>> Normally I should expermient more to see which one of the receipes is >>> really the fix, but I'm just glad that the server is stable for now. >>> >> >> this is really great information. >> It makes debugging a lot more possible. >> I know it is a hard question, but do you have a way to simulate this >> workload? >> >> I have no real way to simulate this kind of workload >> > > Sadly, I don't have a way to simulate the workload but I am very > interested to help fix these crashes since as Cassiano said, this makes > mpd5/freebsd useless for pppoe/l2tp termination. > > At this point, I would suggest that Cassiano and =D0=90=D0=BD=D0=B4=D1=80= =D0=B5=D0=B9 confirm that they > don't get panics when they apply the recipes that I am using. > > I am still running many other cisco-vpdn gateways that I would convert > into mpd5/freebsd but my plan was stalled with the daily crashes. > I'll wait a couple of weeks to be sure that my recipes are a valid > workaround before converting my remaining cisco gateways to mpd5. > > -Dbaud > > >>> >>> recipe-1: Don't let mpd5 start automatically when server boots: >>> i.e. in: /etc/rc.conf >>> mpd5_enable=3D"NO" >>> and wait about 5 minutes after server boots then issue: >>> /usr/local/etc/rc.d/mpd5 onestart >>> >>> >>> recipe-2: recompile the kernel with the NETGRAPH_DEBUG option: >>> options NETGRAPH >>> options NETGRAPH_DEBUG >>> options NETGRAPH_KSOCKET >>> options NETGRAPH_L2TP >>> options NETGRAPH_SOCKET >>> options NETGRAPH_TEE >>> options NETGRAPH_VJC >>> options NETGRAPH_PPP >>> options NETGRAPH_IFACE >>> options NETGRAPH_MPPC_COMPRESSION >>> options NETGRAPH_MPPC_ENCRYPTION >>> options NETGRAPH_TCPMSS >>> options IPFIREWALL >>> >>> recipe-3: recompile the kernel and disable the IPv6 and SCTP options: >>> nooptions INET6 >>> nooptions SCTP >>> >>> recipe-4: Don't use any of the sysctl optimizations >>> in other words I commented out all values in sysctl.conf: >>> # net.graph.maxdgram=3D20480 (this is the default) >>> # net.graph.recvspace=3D20480 (this is the default) >>> >>> recipe-5: Don't use any of the loader.conf optimizations >>> in other words I commented out all values in loader.conf >>> # net.graph.maxdata=3D4096 (this is the default) >>> # net.graph.maxalloc=3D4096 (this is the default) >>> >>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D >>> In my case, I had the panics with 10.3 and 11-PRERELEASE >>> 11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #2 r305587 >>> >>> With those recipes, I have been running without any crash for a month >>> and counting. Thats' 300 l2tp tunnels and 1400 l2tp sessions generatin= g >>> 700Mbit/s. >>> >>> >>> -DBaud >>> >>> >>> On Tuesday, October 11, 2016 7:30 AM, Cassiano Peixoto < >>> peixotocassiano@gmail.com> wrote: >>> Hi, >>> >>> There are many users complaining about this: >>> >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114 >>> >>> I've been dealing with this issue for one year with no solution. mpd5 a= s >>> pppoe server on FreeBSD is useless with this bug. >>> >>> I really would like to see it working again, i think it's quite importa= nt >>> to both project and many users. >>> >>> Thanks. >>> >>> On Tue, Oct 11, 2016 at 3:24 AM, Eugene Grosbein >>> wrote: >>> >>> 11.10.2016 11:02, =D0=90=D0=BD=D0=B4=D1=80=D0=B5=D0=B9 =D0=9B=D0=B5=D1= =83=D1=88=D0=BA=D0=B8=D0=BD =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >>>> >>>> Hello. I have problem with "FreeBSD nas 10.3-RELEASE FreeBSD >>>>> 10.3-RELEASE >>>>> #0: Fri Oct 7 21:12:56 YEKT 2016 nas@nas:/usr/obj/usr/src/sys/nasv3 >>>>> amd64" >>>>> >>>>> Kernel panic is repeated at intervals of 2-3 days. At first I thought >>>>> that >>>>> the problem is in the hardware, but the problem did not go away after >>>>> replacing the server platform. >>>>> >>>>> Coredumps and more info on link >>>>> https://drive.google.com/open?id=3D0BxciMy2q7ZjTTkIxem9wTE1tM2M >>>>> >>>>> Sorry for my english. >>>>> I'll wait for an answer. >>>>> >>>>> This is known and long-stanging problem in the FreeBSD network stack. >>>> It shows up when you have lots of network interfaced created/removed >>>> frequently >>>> like in your case of Network Access Server (PPtP, PPPoE etc). >>>> >>>> Generally, people run into this problem using mpd5 network daemon. >>>> mpd5 uses NETGRAPH kernel subsystem to process traffic and >>>> if an interface disappears (f.e., ,user disconnected) >>>> while kernel still processes traffic obtained from this interface, it >>>> panices. >>>> >>>> There were lots of reports of this problem. Noone seems to be working = on >>>> it at the moment. >>>> You should fill a PR using Bugzilla and attach your logs to it. >>>> >>>> Eugene Grosbein >>>> >>>> > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-net@freebsd.org Wed Oct 12 23:27:23 2016 Return-Path: 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 6B8E2C0F9EA for ; Wed, 12 Oct 2016 23:27:23 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 494301282 for ; Wed, 12 Oct 2016 23:27:23 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) Received: by mailman.ysv.freebsd.org (Postfix) id 48914C0F9E9; Wed, 12 Oct 2016 23:27:23 +0000 (UTC) Delivered-To: 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 48323C0F9E8 for ; Wed, 12 Oct 2016 23:27:23 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) Received: from nm5.bullet.mail.gq1.yahoo.com (nm5.bullet.mail.gq1.yahoo.com [98.136.218.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 213F1127A for ; Wed, 12 Oct 2016 23:27:22 +0000 (UTC) (envelope-from donaldbaud@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1476314660; bh=ocylRbvpninONP6/kW7HmeneEplP4o/UiHMYyfh/Y1g=; h=Subject:References:To:From:Date:In-Reply-To:From:Subject; b=cplhnNCkKPJGkwCCHUWABeNg1T7X56YvC2S+BRL1p4oZKE5zuOawUZS59Z/jQUVxXvyRYgZ6WMsLGO5fFSW0eiu4HqlXhT4fxUdD3H8t442GJwQyI763b4Jh6KmwDOsN9dNXUAhaRc9wdWb1tf5XdT3oV6khxmQBs6rmarMt7vQtn/NAHPSQNI2G7cI8pKaq6+7HLK9ShNEA/IjXDDIFzSlpuTAFAIvcy6uUHtm7JLY7bmmseXpbXlEQQUbjyWy7OEauoJBHxvRq0asGJsx68Xxqea9oyqfzlR17SFtyQXnzapGkLYiOCs85ISita7EufHEOL3D/CBOGXz5gwo4FAw== Received: from [216.39.60.184] by nm5.bullet.mail.gq1.yahoo.com with NNFMP; 12 Oct 2016 23:24:20 -0000 Received: from [98.136.164.74] by tm20.bullet.mail.gq1.yahoo.com with NNFMP; 12 Oct 2016 23:24:20 -0000 Received: from [127.0.0.1] by smtp236.mail.gq1.yahoo.com with NNFMP; 12 Oct 2016 23:24:20 -0000 X-Yahoo-Newman-Id: 295206.56890.bm@smtp236.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: QM9IsZAVM1kszAWwoPScgQLFID1bNMX0S5YGr6vyUpqimxr _xjar5awgakqnoXYnnkXY9_uoFTzE06JnzNSkB6NrPw4oRJuNisDVwJO2J.v 8DXlAAH6OkIfEDYT3OKmmdMXISybY6re8Qn9KpcseHbn6iXQuzcNlBaDeQwa V8jcPm3ZdzN5.khsOTvlQkDfXgAAxjdumOKjkWtgp__Qif3HlANzYNiKDTXE JjwFJjJhWTR.0vX2xk1.x.droZ1d5wawXVZiiNGDnBN2KyyfJpeG5kQOnKMr 6PEGZBnI8VtRkPcDo2cv8DW9XPjyz9a4CkDZLosP_7xgBvJoe1IvuAIMbeAB Bg4ugZQrwoQetVgoR2C3A7bbL8FJQAFanJayV1uD0TGP5q74fva44SWsGkZG mri69iCrqjog3oBCs6ipUp__GEXs2u2_7.HxJHTIlzAQ0ur4OryocsU5Bfx9 tHA5Yc0kDhOwgMvS2bnfTppE0ZunYIKv_XKXbcJwnrWseczIKzMtNwRD6rt3 JzQ2vWvQMSEnnyK3JjgsidMRqLETIEqQNwp._w9zgCGT6iI0sSL7iXw-- X-Yahoo-SMTP: fRRiyyGswBB1GYfBhw8frTz_QYRdpxY- Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. References: <57FC859F.5000200@grosbein.net> <2033449965.65391.1476244568309@mail.yahoo.com> <86183ea5-5855-5fb3-22f6-d25454859186@yahoo.com> To: "net@freebsd.org" From: Donald Baud Message-ID: <958e01c2-8459-9614-ddd6-d0953fc86c02@yahoo.com> Date: Wed, 12 Oct 2016 19:24:22 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 12 Oct 2016 23:27:23 -0000 On 10/12/16 3:24 PM, Zaphod Beeblebrox wrote: > While my mp5 servers are possibly less busy (I havn't had common > crashes), I have noticed a "group" of problems. > > 1. The carrier dropping communication (ie: fiber cut or l2 switch > breakage) of the L2TP streams can leave mpd5 in a state where it will > not die and will not destroy interfaces (requires reboot to clear). I've encountered that once on 10.3 and I had tweaked some sysctl values while monitoring : > vmstat -z | head -1; vmstat -z | grep -i netgraph you might want to search other people's experience with the following values: # net.graph.maxdgram #this is set in /etc/sysctl.conf # net.graph.recvspace #this is set in /etc/sysctl.conf # net.graph.maxdata #this is set in /boot/loader.conf # net.graph.maxalloc #this is set in /boot/loader.conf I'll leave others to comment on what's best to set as values with their experience on FreeBSD10.3. In my case, as I had explained, one of the recipes that worked for me is to comment out and leave those kernel values to their default. I've read in mpd5 mailing list some saying that FreeBSD-11 have had upgrades on the netgraph modules. I am now using FreeBSD-11 and It looks like I don't need any of the kernel tweaks that I've described. Also, may I suggest you troubleshoot the fiber-cut or L2 switch breakage by playing with some ipfw values to simulate a fiber-cut.: ex: ipfw add 100 deny ip from 10.10.10.10 to me > 2. There are race conditions between quagga and mpd5 for > adding/dropping routes. While troubleshooting the crashes of the mpd5, I have removed net/quagga and installed net/bird instead. I am now using net/bird I've written a little howto to get you started with net/bird see: https://forums.freebsd.org/threads/56988/ > 3. if A is a pppoe client and B is the mpd5 server, A cannot access > TCP services on B. It can access tcp services _beyond_ B, but not on > B. (there is a ticket open for this). > > On Wed, Oct 12, 2016 at 10:51 AM, Donald Baud via freebsd-net > > wrote: > > > On 10/12/16 1:13 AM, Julian Elischer wrote: > > On 11/10/2016 8:56 PM, Donald Baud via freebsd-net wrote: > > I've been plagued with these =daily= panics until I tried > the following recipes and the server has been up for 30 > days so far: > > Normally I should expermient more to see which one of the > receipes is really the fix, but I'm just glad that the > server is stable for now. > > > this is really great information. > It makes debugging a lot more possible. > I know it is a hard question, but do you have a way to > simulate this workload? > > I have no real way to simulate this kind of workload > > > Sadly, I don't have a way to simulate the workload but I am very > interested to help fix these crashes since as Cassiano said, this > makes mpd5/freebsd useless for pppoe/l2tp termination. > > At this point, I would suggest that Cassiano and Андрей confirm > that they don't get panics when they apply the recipes that I am > using. > > I am still running many other cisco-vpdn gateways that I would > convert into mpd5/freebsd but my plan was stalled with the daily > crashes. > I'll wait a couple of weeks to be sure that my recipes are a valid > workaround before converting my remaining cisco gateways to mpd5. > > -Dbaud > > > > recipe-1: Don't let mpd5 start automatically when server > boots: > i.e. in: /etc/rc.conf > mpd5_enable="NO" > and wait about 5 minutes after server boots then issue: > /usr/local/etc/rc.d/mpd5 onestart > > > recipe-2: recompile the kernel with the NETGRAPH_DEBUG option: > options NETGRAPH > options NETGRAPH_DEBUG > options NETGRAPH_KSOCKET > options NETGRAPH_L2TP > options NETGRAPH_SOCKET > options NETGRAPH_TEE > options NETGRAPH_VJC > options NETGRAPH_PPP > options NETGRAPH_IFACE > options NETGRAPH_MPPC_COMPRESSION > options NETGRAPH_MPPC_ENCRYPTION > options NETGRAPH_TCPMSS > options IPFIREWALL > > recipe-3: recompile the kernel and disable the IPv6 and > SCTP options: > nooptions INET6 > nooptions SCTP > > recipe-4: Don't use any of the sysctl optimizations > in other words I commented out all values in sysctl.conf: > # net.graph.maxdgram=20480 (this is the default) > # net.graph.recvspace=20480 (this is the default) > > recipe-5: Don't use any of the loader.conf optimizations > in other words I commented out all values in loader.conf > # net.graph.maxdata=4096 (this is the default) > # net.graph.maxalloc=4096 (this is the default) > > ================================ > In my case, I had the panics with 10.3 and 11-PRERELEASE > 11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #2 r305587 > > With those recipes, I have been running without any crash > for a month and counting. Thats' 300 l2tp tunnels and > 1400 l2tp sessions generating 700Mbit/s. > > > -DBaud > > > On Tuesday, October 11, 2016 7:30 AM, Cassiano Peixoto > > wrote: > Hi, > > There are many users complaining about this: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114 > > > I've been dealing with this issue for one year with no > solution. mpd5 as > pppoe server on FreeBSD is useless with this bug. > > I really would like to see it working again, i think it's > quite important > to both project and many users. > > Thanks. > > On Tue, Oct 11, 2016 at 3:24 AM, Eugene Grosbein > > wrote: > > 11.10.2016 11:02, Андрей Леушкин пишет: > > Hello. I have problem with "FreeBSD nas > 10.3-RELEASE FreeBSD 10.3-RELEASE > #0: Fri Oct 7 21:12:56 YEKT 2016 > nas@nas:/usr/obj/usr/src/sys/nasv3 > amd64" > > Kernel panic is repeated at intervals of 2-3 days. > At first I thought that > the problem is in the hardware, but the problem > did not go away after > replacing the server platform. > > Coredumps and more info on link > https://drive.google.com/open?id=0BxciMy2q7ZjTTkIxem9wTE1tM2M > > > Sorry for my english. > I'll wait for an answer. > > This is known and long-stanging problem in the FreeBSD > network stack. > It shows up when you have lots of network interfaced > created/removed > frequently > like in your case of Network Access Server (PPtP, > PPPoE etc). > > Generally, people run into this problem using mpd5 > network daemon. > mpd5 uses NETGRAPH kernel subsystem to process traffic and > if an interface disappears (f.e., ,user disconnected) > while kernel still processes traffic obtained from > this interface, it > panices. > > There were lots of reports of this problem. Noone > seems to be working on > it at the moment. > You should fill a PR using Bugzilla and attach your > logs to it. > > Eugene Grosbein > From owner-freebsd-net@freebsd.org Thu Oct 13 04:51:25 2016 Return-Path: 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 44673C0FD12 for ; Thu, 13 Oct 2016 04:51:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 294929EE for ; Thu, 13 Oct 2016 04:51:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9D4pN0k023845 for ; Thu, 13 Oct 2016 04:51:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT) Date: Thu, 13 Oct 2016 04:51:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: crash, needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Oct 2016 04:51:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D148807 --- Comment #31 from Hiren Panchasara --- (In reply to Robert Watson from comment #29) Robert, Thanks for your response. On a slightly modified (nothing in driver space) stable/11, I am seeing repeated panic in sbsndptr() with igb while box is pretty much idle or doing very low traffic. (kgdb) bt #0 __curthread () at ./machine/pcpu.h:221 #1 doadump (textdump=3D-2121667464) at /d2/hiren/freebsd/sys/kern/kern_shutdown.c:298 #2 0xffffffff80389f86 in db_fncall_generic (nargs=3D0, addr=3D, rv=3D,=20 args=3D) at /d2/hiren/freebsd/sys/ddb/db_command.c:568 #3 db_fncall (dummy1=3D, dummy2=3D, dummy3=3D, dummy4=3D) at /d2/hiren/freebsd/sys/ddb/db_command.c:616 #4 0xffffffff80389a29 in db_command (last_cmdp=3D, cmd_table=3D,=20 dopager=3D) at /d2/hiren/freebsd/sys/ddb/db_command.c:440 #5 0xffffffff80389784 in db_command_loop () at /d2/hiren/freebsd/sys/ddb/db_command.c:493 #6 0xffffffff8038c76b in db_trap (type=3D, code=3D) at /d2/hiren/freebsd/sys/ddb/db_main.c:251 #7 0xffffffff809a6f33 in kdb_trap (type=3D, code=3D, tf=3D) at /d2/hiren/freebsd/sys/kern/subr_kdb.c:654 #8 0xffffffff80d93521 in trap_fatal (frame=3D0xfffffe1f2bb38210, eva=3D24) at /d2/hiren/freebsd/sys/amd64/amd64/trap.c:836 #9 0xffffffff80d93753 in trap_pfault (frame=3D0xfffffe1f2bb38210, usermode= =3D0) at /d2/hiren/freebsd/sys/amd64/amd64/trap.c:691 #10 0xffffffff80d92cdc in trap (frame=3D0xfffffe1f2bb38210) at /d2/hiren/freebsd/sys/amd64/amd64/trap.c:442 #11 #12 sbsndptr (sb=3D0xfffff8060f8a5518, off=3D0, len=3D4294967287, moff=3D0xfffffe1f2bb38420) at /d2/hiren/freebsd/sys/kern/uipc_sockbuf.c:1191 #13 0xffffffff80ab9382 in tcp_output (tp=3D) at /d2/hiren/freebsd/sys/netinet/tcp_output.c:1099 #14 0xffffffff80ab6105 in tcp_do_segment (m=3D, th=3D, so=3D0xfffff8060f8a5360,=20 tp=3D, drop_hdrlen=3D60, tlen=3D, iptos= =3D,=20 ti_locked=3D) at /d2/hiren/freebsd/sys/netinet/tcp_input.c:3182 #15 0xffffffff80ab2803 in tcp_input (mp=3D, offp=3D, proto=3D) at /d2/hiren/freebsd/sys/netinet/tcp_input.c:1444 #16 0xffffffff80aa6bc5 in ip_input (m=3D) at /d2/hiren/freebsd/sys/netinet/ip_input.c:809 #17 0xffffffff80a82b35 in netisr_dispatch_src (proto=3D1, source=3D, m=3D0x0) at /d2/hiren/freebsd/sys/net/netisr.c:1120 #18 0xffffffff80a6c2ca in ether_demux (ifp=3D, m=3D0x0) at /d2/hiren/freebsd/sys/net/if_ethersubr.c:850 #19 0xffffffff80a6cf22 in ether_input_internal (ifp=3D, m=3D= 0x0) at /d2/hiren/freebsd/sys/net/if_ethersubr.c:639 #20 ether_nh_input (m=3D) at /d2/hiren/freebsd/sys/net/if_ethersubr.c:669 #21 0xffffffff80a82b35 in netisr_dispatch_src (proto=3D5, source=3D, m=3D0x0) at /d2/hiren/freebsd/sys/net/netisr.c:1120 #22 0xffffffff80a6c546 in ether_input (ifp=3D, m=3D0x0) at /d2/hiren/freebsd/sys/net/if_ethersubr.c:759 #23 0xffffffff804e2b3c in igb_rx_input (rxr=3D, ifp=3D0xfffff80115614800, m=3D0xfffff8014eee7600,=20 ptype=3D) at /d2/hiren/freebsd/sys/dev/e1000/if_igb.c:49= 57 #24 igb_rxeof (que=3D, count=3D358700136, done=3D) at /d2/hiren/freebsd/sys/dev/e1000/if_igb.c:5185 #25 0xffffffff804e1daf in igb_msix_que (arg=3D) at /d2/hiren/freebsd/sys/dev/e1000/if_igb.c:1612 #26 0xffffffff8091425f in intr_event_execute_handlers (p=3D, ie=3D) at /d2/hiren/freebsd/sys/kern/kern_intr.c:1262 #27 0xffffffff80914876 in ithread_execute_handlers (ie=3D, p=3D) at /d2/hiren/freebsd/sys/kern/kern_intr.c:1275 #28 ithread_loop (arg=3D) at /d2/hiren/freebsd/sys/kern/kern_intr.c:1356 #29 0xffffffff80910ea5 in fork_exit (callout=3D0xffffffff809147b0 , arg=3D0xfffff8011561a0e0,=20 frame=3D0xfffffe1f2bb38ac0) at /d2/hiren/freebsd/sys/kern/kern_fork.c:1= 040 #30 ---------------------------------------------------------------- Most interesting frames are these 2: #22 0xffffffff80a6c546 in ether_input (ifp=3D, m=3D0x0) at /d2/hiren/freebsd/sys/net/if_ethersubr.c:759 #23 0xffffffff804e2b3c in igb_rx_input (rxr=3D, ifp=3D0xfffff80115614800, m=3D0xfffff8014eee7600,=20 ptype=3D) at /d2/hiren/freebsd/sys/dev/e1000/if_igb.c:49= 57 #23 has an mbuf while #22 has it null. Does this point to your hunch of "device-driver bugs involving modifications to the mbuf chain after submitt= ing the mbuf to the network stack (e.g., due to concurrency bugs in the device driver)" ? OR something else is going on? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 13 08:37:55 2016 Return-Path: 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 7DA71C0FD2D for ; Thu, 13 Oct 2016 08:37:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 521A1FDE for ; Thu, 13 Oct 2016 08:37:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9D8brjb044082 for ; Thu, 13 Oct 2016 08:37:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT) Date: Thu, 13 Oct 2016 08:37:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: crash, needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ddb@neosystem.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Oct 2016 08:37:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D148807 Daniel Bilik changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ddb@neosystem.org --- Comment #32 from Daniel Bilik --- (In reply to Robert Watson from comment #29) > On the whole, my intuition is towards a device-driver bug based > on past experience. We've been also struggling this in past weeks, and I can confirm Robert's intuition. In our case, the bug affects two hosts running recent 10-STABLE, connected = to each other via igb(4) using a dedicated 100Mb switch. When trying to transf= er directory structure holding several gigabytes of data with rsync protocol, either sender or receiver panics in less then a minute with: Panic String: sbsndptr: sockbuf 0xfffff8000ccc76f8 and mbuf 0xfffff802a0145= 800 clashing Interestingly, scp(1)ing data between the hosts doesn't seem to trigger this panic such easily, but sometimes it does, mostly when copying larger (>1GB) files. We've fixed this just yesterday by limiting number of igb(4) txrx queues, i= e. adding this into loader.conf: hw.igb.num_queues=3D1 Now the hosts run stable, periodically rsyncing data in both directions. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 13 09:12:41 2016 Return-Path: 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 708ADC10B8D for ; Thu, 13 Oct 2016 09:12:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 5F397F01 for ; Thu, 13 Oct 2016 09:12:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9D9CeYu001159 for ; Thu, 13 Oct 2016 09:12:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT) Date: Thu, 13 Oct 2016 09:12:40 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: crash, needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: slw@zxy.spb.ru X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Oct 2016 09:12:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D148807 slw@zxy.spb.ru changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |slw@zxy.spb.ru --- Comment #33 from slw@zxy.spb.ru --- (In reply to Hiren Panchasara from comment #31) > Most interesting frames are these 2: >=20 > #22 0xffffffff80a6c546 in ether_input (ifp=3D, m=3D0x0) at= /d2/hiren/freebsd/sys/net/if_ethersubr.c:759 > #23 0xffffffff804e2b3c in igb_rx_input (rxr=3D, ifp=3D0xff= fff80115614800, m=3D0xfffff8014eee7600,=20 > ptype=3D) at /d2/hiren/freebsd/sys/dev/e1000/if_igb.c:4= 957 > > #23 has an mbuf while #22 has it null. > Does this point to your hunch of > "device-driver bugs involving modifications to the mbuf chain after submi= tting the mbuf to the network stack (e.g., due to concurrency bugs in the d= evice driver)" ? This is just result of compiler optimisation and stack decoding. Compiler use for m same register as passed at call time and do while (m) {=20=20 mn =3D m->m_nextpkt; [...] m =3D mn; } as result m (as decoded argument) will be incorectly displayed. Actualy this is just last loop iteration with last mbuf in chain. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 13 10:28:41 2016 Return-Path: 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 E1382C0F138 for ; Thu, 13 Oct 2016 10:28:41 +0000 (UTC) (envelope-from 32GH_VwgTA18KL-OBMIV799LRKQP.DLLDIB.9LJKBQCOBB8PA.LOD@gaia.bounces.google.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BFF4D651 for ; Thu, 13 Oct 2016 10:28:41 +0000 (UTC) (envelope-from 32GH_VwgTA18KL-OBMIV799LRKQP.DLLDIB.9LJKBQCOBB8PA.LOD@gaia.bounces.google.com) Received: by mailman.ysv.freebsd.org (Postfix) id BC33DC0F137; Thu, 13 Oct 2016 10:28:41 +0000 (UTC) Delivered-To: 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 BA162C0F136 for ; Thu, 13 Oct 2016 10:28:41 +0000 (UTC) (envelope-from 32GH_VwgTA18KL-OBMIV799LRKQP.DLLDIB.9LJKBQCOBB8PA.LOD@gaia.bounces.google.com) Received: from mail-vk0-x248.google.com (mail-vk0-x248.google.com [IPv6:2607:f8b0:400c:c05::248]) (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 6637864F for ; Thu, 13 Oct 2016 10:28:41 +0000 (UTC) (envelope-from 32GH_VwgTA18KL-OBMIV799LRKQP.DLLDIB.9LJKBQCOBB8PA.LOD@gaia.bounces.google.com) Received: by mail-vk0-x248.google.com with SMTP id q126so58160717vkd.4 for ; Thu, 13 Oct 2016 03:28:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=accounts.google.com; s=20120806; h=mime-version:date:feedback-id:message-id:subject:from:to; bh=rvk0vHUggNGVgq/93myPOJNEfStbK9padMqMcwgdqrE=; b=d47+m5UA1TtO6BunV6ukqiUbiSEsu7+nO8pFVDWOHGN1Jiw99vZ8EZpHZj9J9hiRx1 ZvAAMIFpHg1GZP/ayoRVXma/oEzeS56KUljJJUAuIfg5jUwy5IMkrlb2XKS09jMqs1xU ewm8LfuNBOin388Vl+Soxd7rFE+49cP9ufhiCRu4dw2BsYcpoUnfvgHIgR5awYu7e1pR x3RPX/zQjlChEazRM9gNhl8wu95XOVwkxAHYFYOaT9yY6Ac6zosMROknjWkWNGzAeDrT yJcuMlXZ0dDhD5Zpoec++OwDRn0PEGdBXBMfaKKqEOoRgLc0/xKl6cN7xLfh8OF50grx VYqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:feedback-id:message-id:subject :from:to; bh=rvk0vHUggNGVgq/93myPOJNEfStbK9padMqMcwgdqrE=; b=dDxIw+cPGVX5AYshywy1Z0Pf1pLCrNBV+ey99sKYatymg8KuxXyUZSwUq4QNDd4jAx rbBjo9s4Fx4yaS1pGU3+GMCqlPoSdu5JcKjVvG0hFTR0HR+njYLLruHHIDnFdrCB47wp 2Ddih0qudx5sdvqke0oaGqmmVky2nhLIAL1AowwWIPThgb2+6ySflXMNIO3wjsUfDLBl curFjap81K/9BgNve9C+sUMMEcYo/jUEe6SPkJyida61RcqVBXHe4ykoV/WvvenAuReQ 2CAVSgf/WKiHrs3+P3yt0uHsTFSRC7+qSmsy7B07OQ0rl/AdCw8EBatlpr+RO32V9QD8 JeDg== X-Gm-Message-State: AA6/9RkGoIzeFOEbT4OuLgGE5zzPqbsJE9MwF2VhUv+l1DvmrJRxZPra1fZnTu/Lx8umGpiJcYDiRLnETlh3OUsv MIME-Version: 1.0 X-Received: by 10.31.108.92 with SMTP id h89mr1513398vkc.18.1476354520508; Thu, 13 Oct 2016 03:28:40 -0700 (PDT) Date: Thu, 13 Oct 2016 10:28:31 +0000 (UTC) X-Notifications: XEAAAAI4xMT2JtaqWnXh4iCkL2BI X-Account-Notification-Type: 2-RECOVERY-anexp:ire-control Feedback-ID: 2-RECOVERY-anexp:ire-control:account-notifier Message-ID: Subject: Your recovery email address changed From: Google To: net@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Oct 2016 10:28:42 -0000 WW91ciByZWNvdmVyeSBlbWFpbCBhZGRyZXNzIGNoYW5nZWQNCg0KDQoNCkhpIFZOU+WoseS5kOWf jjg3NjUwMi5jb23ms6jlhozpgIE4OOWFgyznvZHkuIrmnIDngavniIbnmoTmuLjmiI/lubPlj7As 6LaF5aW96LWi6ZKx5ri45oiPLA0KVGhlIHJlY292ZXJ5IGVtYWlsIGZvciB5b3VyIEdvb2dsZSBB Y2NvdW50IGRlaXJkcmVzaW1wc29uNzU5QGdtYWlsLmNvbSB3YXMNCnJlY2VudGx5IGNoYW5nZWQu DQoNCipEb24ndCByZWNvZ25pemUgdGhpcyBhY3Rpdml0eT8qDQpSZXZpZXcgeW91ciByZWNlbnRs eSB1c2VkIGRldmljZXMNCjxodHRwczovL2FjY291bnRzLmdvb2dsZS5jb20vQWNjb3VudENob29z ZXI/RW1haWw9ZGVpcmRyZXNpbXBzb243NTlAZ21haWwuY29tJmNvbnRpbnVlPWh0dHBzOi8vc2Vj dXJpdHkuZ29vZ2xlLmNvbS9zZXR0aW5ncy9zZWN1cml0eS9hY3Rpdml0eS9udC8xNDc2MzU0NTEx NTk5P3JmbiUzRDIlMjZyZm5jJTNEMSUyNmV0JTNENCUyNmFzYWUlM0QyJTI2YW5leHAlM0RpcmUt Y29udHJvbD4NCm5vdy4NCg0KQmVzdCwNClRoZSBHb29nbGUgQWNjb3VudHMgdGVhbQ0KDQoNCg0K VGhpcyBlbWFpbCBjYW4ndCByZWNlaXZlIHJlcGxpZXMuIEZvciBtb3JlIGluZm9ybWF0aW9uLCB2 aXNpdCB0aGUgR29vZ2xlDQpBY2NvdW50cyBIZWxwIENlbnRlciA8aHR0cHM6Ly9zdXBwb3J0Lmdv b2dsZS5jb20vYWNjb3VudHMvYW5zd2VyLzI0NTAyMzY+Lg0KDQoNCg0KWW91IHJlY2VpdmVkIHRo aXMgbWFuZGF0b3J5IGVtYWlsIHNlcnZpY2UgYW5ub3VuY2VtZW50IHRvIHVwZGF0ZSB5b3UgYWJv dXQNCmltcG9ydGFudCBjaGFuZ2VzIHRvIHlvdXIgR29vZ2xlIHByb2R1Y3Qgb3IgYWNjb3VudC4N CsKpIDIwMTYgR29vZ2xlIEluYy4sIDE2MDAgQW1waGl0aGVhdHJlIFBhcmt3YXksIE1vdW50YWlu IFZpZXcsIENBIDk0MDQzLCBVU0ENCg== From owner-freebsd-net@freebsd.org Thu Oct 13 11:46:32 2016 Return-Path: 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 54997C0EEF3 for ; Thu, 13 Oct 2016 11:46:32 +0000 (UTC) (envelope-from srtsteel@163.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3CA35A95 for ; Thu, 13 Oct 2016 11:46:32 +0000 (UTC) (envelope-from srtsteel@163.com) Received: by mailman.ysv.freebsd.org (Postfix) id 3BE32C0EEF2; Thu, 13 Oct 2016 11:46:32 +0000 (UTC) Delivered-To: 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 2158FC0EEF1 for ; Thu, 13 Oct 2016 11:46:32 +0000 (UTC) (envelope-from srtsteel@163.com) Received: from m13-224.163.com (m13-224.163.com [220.181.13.224]) by mx1.freebsd.org (Postfix) with ESMTP id 6EFB7A91 for ; Thu, 13 Oct 2016 11:46:31 +0000 (UTC) (envelope-from srtsteel@163.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Date:From:Message-ID:Subject:MIME-Version; bh=urmok Kk0Iz/eFNDc1hTTLYn4eX2XrCl93i5RdHQ/ZZ0=; b=RxtEyXCQoxmomjjhXpqYF uMt5CdbAG1VtZ6iVchnualF4o9dFtavnw9fTbQbBIJjD7wCWlS0IL+AQXsl2B42b IpC9QpH9pkChGQ3dsdWcsvFNoMXLOqfdM2RdF1UNexXa2Pw7GE9Ng0vDC4wthGSS DniGx6r9kgL/6ZqQOVLX7w= Received: from srtsteel$163.com ( [113.247.235.106] ) by ajax-webmail-sdy25 (Coremail) ; Thu, 13 Oct 2016 19:36:43 +0800 (GMT+08:00) Date: Thu, 13 Oct 2016 19:36:56 +0800 From: "srtsteel" To: "net" Message-ID: <62bd6af2.373a60.157bdd484c5.Coremail.srtsteel@163.com> Subject: Re: Seamless steel pipe stockist--Threeway Steel Co.,Ltd in China MIME-Version: 1.0 X-Mailer: NetEase Flash Mail 2.4.1.30 X-Priority: 3 (Normal) X-Originating-IP: [113.247.235.106] X-CM-TRANSID: UceowAC3nZrMcf9XBiMyAA--.62026W X-CM-SenderInfo: pvuw23xhhoqiywtou0bp/xtbBEBECglUL+u0bVgABsE X-Coremail-Antispam: 1U5529EdanIXcx71UUUUU7vcSsGvfC2KfnxnUU== Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Oct 2016 11:46:32 -0000 RGVhciBNYW5hZ2VyLA0KDQoNCkdvb2QgZGF5ISBUaGlzIGlzIFZpbGxhIGZyb20gSHVuYW4gVGhy ZWV3YXkgU3RlZWwgQ28uLEx0ZCAuDQpXZSBhcmUgb25lIG9mIHRoZSBsZWFkaW5nIHN0ZWVsIHBp cGUgbWFudWZhY3R1cmVyIHdoaWNoIGNhbiBtZWV0IGNsaWVudHMgcmVxdWlyZW1lbnQgZm9yIHBp cGVzIHdpdGggQVBJLCBBU1RNLCBFTiwgQlMsIERJTiBzdGFuZGFyZC4gYWxsIG9mIG91ciBwaXBl cyBjYW4gYmUgc3RyaWN0bHkgdGVzdGVkIGJ5IFNHUywgQlYsIEROViwgVFVWLCBMTE9ZRCdTIHRo aXJkIHBhcnR5IGluc3BlY3Rpb24uIGFsc28gd2l0aCBjb21wZXRpdGl2ZSBwcmljZSBpbiB0aGlz IG1hcmtldCB3aXRoIHNob3J0IGRlbGl2ZXJ5IHRpbWUgYW5kIGZsZXhhYmxlIHBheW1lbnQgdGVy bXMoTC9DLFQvVCxPL0EpLg0KV2UgaGF2ZSBzdXBwbGllZCB0aGUgcGlwZXMgdG8gUEVNRVggKE1l eGljbyksIElCRVJEUk9MQShTcGFpbiksIFBEU1ZBIChWZW5lenVlbGEpLCBQRVRST0JSQVMoQnJh emlsKSwgU0FVREkgQVJBTUNPLCBTV0NDLCBFSUVEL05JT0MgKElyYW4pIGluIHJlY2VudCB5ZWFy cy4NClBsZWFzZSBzZWUgdGhlIG1haW4gcHJvZHVjdCBsaWtlIGJlbG93Og0KDQpTRUFNTEVTUyBT VEVFTCBQSVBFDQogICDigIvigIsNClNpemU6IE9EOiAxMy43MiBtbSAtIDkxNC40IG1tOyAgIFdU OiAxLjY1IG1tIC0gMjIgbW07ICBMZW5ndGg6IDAuNSBtIC0gMjAgbQ0KU3RhbmRhcmQ6IEFQSSA1 TCwgQVNUTSBBMTA2L0E1MywgRElOMjM5MSwgRElOMTYyOSwgQVNUTSBBMTc5L0ExOTIsIEVOMTAy MTAsIEVOMTAyMTYsIEVOMTAyMDgNCk1hdGVyaWFsOiBHUi5CLCBYNDIsIFg0NiwgWDUyLCBTMzU1 Sk9ILCBTMzU1SjJILCBTdCA0NC4wLCBQMjY1R0gsIFAyMzVHSCwgUDI2NVRSMQ0KVXNhZ2U6IENo aWxsZWQgV2F0ZXIgUGlwZSwgRHJpbmtpbmcgd2F0ZXIgUGlwZSwgV2FzdGUgV2F0ZXIgUGlwZSwg U3RydWN0dXJhbCBUdWJlLCBGbHVpZCBQaXBlLCBCb2lsZXIgUGlwZSwgT2lsIGFuZCBHYXMgVHJh bnNwb3J0YXRpb24gUGlwZSwgTWVjaGFuaWNhbCBTdHJ1Y3R1cmUgUGlwZSAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgIA0KDQoNClNvLGlmIHlvdSBoYXZlIGFueSBxdWVzdGlv bnMgb3IgaW50ZXJlc3RzIHBscyBmZWVsIGZyZWUgdG8gY29udGFjdCBtZSxsb29raW5nIGZvcndh cmQgdG8geW91ciBraW5kbHkgcmVwbHkuDQoNCg0KVGhhbmtzJkJlc3QgUmVnYXJkcyANCiBWaWxs YSBMaWF3DQoNCg0KIE9mZmljZTogKzg2LTA3MzEtODg2Nzg1MTAgIHwgIEZheDogKzg2LTA3MzEt ODg2Nzg1NzgNCiBNb2I6ICs4Ni0xMzYgNjczOSA0MDMzIChXaGF0cyBVcCkgIHwgIFNreXBlOiBz YWxlczMwQHNydHN0ZWVscGlwZS5jb20NCiBFbWFpbDogc2FsZXMzMEBzcnRzdGVlbHBpcGUuY29t ICB8ICBzcnRzdGVlbEAxNjMuY29tICANCiBXZWJzaXRlOiBodHRwOi8vd3d3LnRocmVld2F5c3Rl ZWwuY29tIA0KIEFkZHJlc3M6IDIybmQgRmxvb3IsUm95YWwgV2luZyBUb3dlcixMb25nIENoYW1w IEludGVybmF0aW9uYWwgQnVpbGRpbmcsTm8uOSBYaWFuZ2Z1IFJvYWQsQ2hhbmdzaGEgLEh1bmFu LENoaW5hDQogU1RFRUwgUElQRSBNQU5VRkFDVFVSRSAmIEVYUE9SVCBFWFBFUklFTkNFIEZPUiAy NSBZRUFSUw0KIFAgUGxlYXNlIGNvbnNpZGVyIHRoZSBlbnZpcm9ubWVudCBiZWZvcmUgcHJpbnRp bmcgdGhpcyBlLW1haWw= From owner-freebsd-net@freebsd.org Thu Oct 13 15:24:16 2016 Return-Path: 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 EB37AC0C7B0 for ; Thu, 13 Oct 2016 15:24:16 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id C625EE45 for ; Thu, 13 Oct 2016 15:24:16 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id C580CC0C7AF; Thu, 13 Oct 2016 15:24:16 +0000 (UTC) Delivered-To: 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 C516DC0C7AE for ; Thu, 13 Oct 2016 15:24:16 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (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 7BD1EE40 for ; Thu, 13 Oct 2016 15:24:16 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mail-qk0-x231.google.com with SMTP id z190so96460932qkc.2 for ; Thu, 13 Oct 2016 08:24:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ayYx2JVZLsSnVItPPmrXYW/8NoVa3OKY8fl9Gr/eLpE=; b=H7hxDNdSH8CHeYyLNbTLcwgc+g+2PHSnfGC4GW8PQsQOFN356PZvFQohXr378n4NLP xaSOjTWVNsO4idGY6xUF9+6EbF8vYBzKhM195LDJ0XvaGmhLlWtTasSTBrKtUJ67cYTP KH1+uHuZeI85hEX7y8wM1QJjA0YFP3G4lj8mLbXV9OLYj77Axh53wQ431asMA57gzFNV 9lcXlYZk3Mam+6uvecERvmVThsSeau7Isp/vCEXCb71s3vx/vgVrQSZ7WWKhWOnefi3/ kNNMqzogP+nCKs4w2chH8h2UfZWjl0Iin+Wm2UXvsXk/hl0f9l0XFk5RLqf8pjSIy+/A ibtQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ayYx2JVZLsSnVItPPmrXYW/8NoVa3OKY8fl9Gr/eLpE=; b=YahG+lJ/D9tsDEaksh4xSh10Vn2ICJNd6+HB3a5OyvUYRlywrQQnmYhqkfSQKnZGPz ElQnBHhui2eH8UUi8n4LUavj1hztYb34OW/q+TanLk96NAVyeKQapdITjcvlYLDqyIZ1 ejB1wDIdF0e2XFsIgTl07ABkx2TgeiZjJtY96WscTcDA650iZvl8zyxGFy6+DshaUQWA dTftKSp+0DRA56rR8p7SMVv7l8mcz4rrKvnYSdkWBseosjLmZ5g643pdRvLaj44eBZG9 dvMiRp/oMMhXonmEEflwUbyxYSqeQNrb3VPgmPK6puU2rZfMxaI4SqivHLOC0BM3nG8e szzg== X-Gm-Message-State: AA6/9RmOmbeUTZlbM37gJeUJR0y9jotn2Xgtl4X06Fj5fUv3dYCAVemcOy9KzVgH6BtmDDnowgDdhmTYii0mtQ== X-Received: by 10.55.15.167 with SMTP id 39mr7916540qkp.234.1476372255425; Thu, 13 Oct 2016 08:24:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.166.26 with HTTP; Thu, 13 Oct 2016 08:24:14 -0700 (PDT) In-Reply-To: <958e01c2-8459-9614-ddd6-d0953fc86c02@yahoo.com> References: <57FC859F.5000200@grosbein.net> <2033449965.65391.1476244568309@mail.yahoo.com> <86183ea5-5855-5fb3-22f6-d25454859186@yahoo.com> <958e01c2-8459-9614-ddd6-d0953fc86c02@yahoo.com> From: Cassiano Peixoto Date: Thu, 13 Oct 2016 12:24:14 -0300 Message-ID: Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. To: Donald Baud Cc: "net@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Oct 2016 15:24:17 -0000 Hi guys, First of all, thanks to share your thoughts about this issue. I think it=E2= =80=99s really important to find out a solution for this issue together. I can see two behaviors related, but for me the root cause is the same: 1- mpd5 process stuck with umtxn flag 2- system crash I=E2=80=99ve tested recently on FreeBSD 10.3 and FreeBSD-11-RC3. I=E2=80=99= ve tried all suggested tunings with no success. My environment is: - About 430 clients connected (but i can add more) - Using ZFS - igb NICs. - Generic kernel Two days ago i updated my system to FreeBSD 11-RELEASE-p1 and after this my system seems stable for almost 3 days. No crashes anymore. I need more days to feel confident if something has changed. But anyway, my crashes before happened every day. If it crashs again i=E2=80=99ll apply Donald recommendation and let you guy= s know. Let=E2=80=99s keep in touch, to try to at last fix it. Thanks. On Wed, Oct 12, 2016 at 8:24 PM, Donald Baud via freebsd-net < freebsd-net@freebsd.org> wrote: > On 10/12/16 3:24 PM, Zaphod Beeblebrox wrote: > > While my mp5 servers are possibly less busy (I havn't had common crashes)= , >> I have noticed a "group" of problems. >> >> 1. The carrier dropping communication (ie: fiber cut or l2 switch >> breakage) of the L2TP streams can leave mpd5 in a state where it will no= t >> die and will not destroy interfaces (requires reboot to clear). >> > I've encountered that once on 10.3 and I had tweaked some sysctl values > while monitoring : > > vmstat -z | head -1; vmstat -z | grep -i netgraph > > you might want to search other people's experience with the following > values: > # net.graph.maxdgram #this is set in /etc/sysctl.conf > # net.graph.recvspace #this is set in /etc/sysctl.conf > # net.graph.maxdata #this is set in /boot/loader.conf > # net.graph.maxalloc #this is set in /boot/loader.conf > > I'll leave others to comment on what's best to set as values with their > experience on FreeBSD10.3. > In my case, as I had explained, one of the recipes that worked for me is > to comment out and leave those kernel values to their default. > > I've read in mpd5 mailing list some saying that FreeBSD-11 have had > upgrades on the netgraph modules. > I am now using FreeBSD-11 and It looks like I don't need any of the kerne= l > tweaks that I've described. > > Also, may I suggest you troubleshoot the fiber-cut or L2 switch breakage > by playing with some ipfw values to simulate a fiber-cut.: > ex: ipfw add 100 deny ip from 10.10.10.10 to me > >> 2. There are race conditions between quagga and mpd5 for adding/dropping >> routes. >> > While troubleshooting the crashes of the mpd5, I have removed net/quagga > and installed net/bird instead. > I am now using net/bird I've written a little howto to get you started > with net/bird > see: https://forums.freebsd.org/threads/56988/ > > 3. if A is a pppoe client and B is the mpd5 server, A cannot access TCP >> services on B. It can access tcp services _beyond_ B, but not on B. (th= ere >> is a ticket open for this). >> >> On Wed, Oct 12, 2016 at 10:51 AM, Donald Baud via freebsd-net < >> freebsd-net@freebsd.org > wrote: >> >> >> On 10/12/16 1:13 AM, Julian Elischer wrote: >> >> On 11/10/2016 8:56 PM, Donald Baud via freebsd-net wrote: >> >> I've been plagued with these =3Ddaily=3D panics until I trie= d >> the following recipes and the server has been up for 30 >> days so far: >> >> Normally I should expermient more to see which one of the >> receipes is really the fix, but I'm just glad that the >> server is stable for now. >> >> >> this is really great information. >> It makes debugging a lot more possible. >> I know it is a hard question, but do you have a way to >> simulate this workload? >> >> I have no real way to simulate this kind of workload >> >> >> Sadly, I don't have a way to simulate the workload but I am very >> interested to help fix these crashes since as Cassiano said, this >> makes mpd5/freebsd useless for pppoe/l2tp termination. >> >> At this point, I would suggest that Cassiano and =D0=90=D0=BD=D0=B4= =D1=80=D0=B5=D0=B9 confirm >> that they don't get panics when they apply the recipes that I am >> using. >> >> I am still running many other cisco-vpdn gateways that I would >> convert into mpd5/freebsd but my plan was stalled with the daily >> crashes. >> I'll wait a couple of weeks to be sure that my recipes are a valid >> workaround before converting my remaining cisco gateways to mpd5. >> >> -Dbaud >> >> >> >> recipe-1: Don't let mpd5 start automatically when server >> boots: >> i.e. in: /etc/rc.conf >> mpd5_enable=3D"NO" >> and wait about 5 minutes after server boots then issue: >> /usr/local/etc/rc.d/mpd5 onestart >> >> >> recipe-2: recompile the kernel with the NETGRAPH_DEBUG optio= n: >> options NETGRAPH >> options NETGRAPH_DEBUG >> options NETGRAPH_KSOCKET >> options NETGRAPH_L2TP >> options NETGRAPH_SOCKET >> options NETGRAPH_TEE >> options NETGRAPH_VJC >> options NETGRAPH_PPP >> options NETGRAPH_IFACE >> options NETGRAPH_MPPC_COMPRESSION >> options NETGRAPH_MPPC_ENCRYPTION >> options NETGRAPH_TCPMSS >> options IPFIREWALL >> >> recipe-3: recompile the kernel and disable the IPv6 and >> SCTP options: >> nooptions INET6 >> nooptions SCTP >> >> recipe-4: Don't use any of the sysctl optimizations >> in other words I commented out all values in sysctl.conf: >> # net.graph.maxdgram=3D20480 (this is the default) >> # net.graph.recvspace=3D20480 (this is the default) >> >> recipe-5: Don't use any of the loader.conf optimizations >> in other words I commented out all values in loader.conf >> # net.graph.maxdata=3D4096 (this is the default) >> # net.graph.maxalloc=3D4096 (this is the default) >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> In my case, I had the panics with 10.3 and 11-PRERELEASE >> 11.0-PRERELEASE FreeBSD 11.0-PRERELEASE #2 r305587 >> >> With those recipes, I have been running without any crash >> for a month and counting. Thats' 300 l2tp tunnels and >> 1400 l2tp sessions generating 700Mbit/s. >> >> >> -DBaud >> >> >> On Tuesday, October 11, 2016 7:30 AM, Cassiano Peixoto >> > > wrote: >> Hi, >> >> There are many users complaining about this: >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114 >> >> >> I've been dealing with this issue for one year with no >> solution. mpd5 as >> pppoe server on FreeBSD is useless with this bug. >> >> I really would like to see it working again, i think it's >> quite important >> to both project and many users. >> >> Thanks. >> >> On Tue, Oct 11, 2016 at 3:24 AM, Eugene Grosbein >> > wrote: >> >> 11.10.2016 11:02, =D0=90=D0=BD=D0=B4=D1=80=D0=B5=D0=B9 = =D0=9B=D0=B5=D1=83=D1=88=D0=BA=D0=B8=D0=BD =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> >> Hello. I have problem with "FreeBSD nas >> 10.3-RELEASE FreeBSD 10.3-RELEASE >> #0: Fri Oct 7 21:12:56 YEKT 2016 >> nas@nas:/usr/obj/usr/src/sys/nasv3 >> amd64" >> >> Kernel panic is repeated at intervals of 2-3 days. >> At first I thought that >> the problem is in the hardware, but the problem >> did not go away after >> replacing the server platform. >> >> Coredumps and more info on link >> https://drive.google.com/open? >> id=3D0BxciMy2q7ZjTTkIxem9wTE1tM2M >> > ?id=3D0BxciMy2q7ZjTTkIxem9wTE1tM2M> >> >> Sorry for my english. >> I'll wait for an answer. >> >> This is known and long-stanging problem in the FreeBSD >> network stack. >> It shows up when you have lots of network interfaced >> created/removed >> frequently >> like in your case of Network Access Server (PPtP, >> PPPoE etc). >> >> Generally, people run into this problem using mpd5 >> network daemon. >> mpd5 uses NETGRAPH kernel subsystem to process traffic a= nd >> if an interface disappears (f.e., ,user disconnected) >> while kernel still processes traffic obtained from >> this interface, it >> panices. >> >> There were lots of reports of this problem. Noone >> seems to be working on >> it at the moment. >> You should fill a PR using Bugzilla and attach your >> logs to it. >> >> Eugene Grosbein >> >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://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 Oct 13 16:31:03 2016 Return-Path: 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 2051CC105F6 for ; Thu, 13 Oct 2016 16:31:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 0FB73F50 for ; Thu, 13 Oct 2016 16:31:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DGV2IL051204 for ; Thu, 13 Oct 2016 16:31:02 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213232] [tcp] [panic] tcp_output() Panic String: tcp_output: len > IP_MAXPACKET on -head and stable/11 Date: Thu, 13 Oct 2016 16:31:03 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Oct 2016 16:31:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213232 Hiren Panchasara changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[tcp] [panic] tcp_output() |[tcp] [panic] tcp_output() |Panic String: tcp_output: |Panic String: tcp_output: |len > IP_MAXPACKET (at |len > IP_MAXPACKET on -head |r306658) |and stable/11 --- Comment #4 from Hiren Panchasara --- Just hit this on uptodate stable/11 system. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 13 16:40:42 2016 Return-Path: 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 0F4C7C10977 for ; Thu, 13 Oct 2016 16:40:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 F203C680 for ; Thu, 13 Oct 2016 16:40:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DGecQT076627 for ; Thu, 13 Oct 2016 16:40:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT) Date: Thu, 13 Oct 2016 16:40:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: crash, needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Oct 2016 16:40:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D148807 --- Comment #34 from Hiren Panchasara --- (In reply to slw from comment #33) Thanks but I am little confused. which value of 'm' should I trust? is it null in frame #22 or not? it seems like null in the frames above it also. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 13 17:55:41 2016 Return-Path: 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 7CA71C10F18 for ; Thu, 13 Oct 2016 17:55:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 6B2CA668 for ; Thu, 13 Oct 2016 17:55:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DHteN4009476 for ; Thu, 13 Oct 2016 17:55:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT) Date: Thu, 13 Oct 2016 17:55:40 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.1-STABLE X-Bugzilla-Keywords: crash, needs-qa, patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: slw@zxy.spb.ru X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Oct 2016 17:55:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D148807 --- Comment #35 from slw@zxy.spb.ru --- (In reply to Hiren Panchasara from comment #34) > which value of 'm' should I trust? is it null in frame #22 or not? it see= ms like null in the frames above it also. =D0=97artially. ether_input call with m set to 0xfffff8014eee7600 (and this= is first m for next invocation of further functions), do one (or more, w/ different = m, need access to vmcore by kgdb and analyse 0xfffff8014eee7600 for answer) iteration w/ and call netisr_dispatch with passed m as second argument (in %rsi register). All next invocation can don't preserve %rsi (or %rdx in cas= e of m passed as 3'th argument) and backtrace can incorrectly decode arguments c= all. Just realyty check: frame #19, ether_input_internal (ifp=3D, m=3D0x0), line 483: if (m->m_len < ETHER_HDR_LEN) { MUST occur kernel panic if m realy NULL. This is just incorrect decoding of arguments. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 13 19:07:35 2016 Return-Path: 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 A6DFCC10202 for ; Thu, 13 Oct 2016 19:07:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 9659C1ECE for ; Thu, 13 Oct 2016 19:07:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9DJ7Zr9065535 for ; Thu, 13 Oct 2016 19:07:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213232] [tcp] [panic] tcp_output() Panic String: tcp_output: len > IP_MAXPACKET on -head and stable/11 Date: Thu, 13 Oct 2016 19:07:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hiren@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 13 Oct 2016 19:07:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213232 --- Comment #5 from Hiren Panchasara --- r306769 | jtl | 2016-10-06 09:28:34 -0700 (Thu, 06 Oct 2016) | 8 lines Remove "long" variables from the TCP stack (not including the modular congestion control framework). may help. Updating my box and trying again if I get the same crash. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 14 05:41:07 2016 Return-Path: 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 72451C0FF54 for ; Fri, 14 Oct 2016 05:41:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 60D37A9F for ; Fri, 14 Oct 2016 05:41:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9E5f4rv027580 for ; Fri, 14 Oct 2016 05:41:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212018] Enable IPSEC_NAT_T in GENERIC kernel configuration Date: Fri, 14 Oct 2016 05:41:04 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: feature, needs-patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: see_also priority dependson bug_severity Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Oct 2016 05:41:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212018 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- See Also|https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D1280 | |30 | Priority|--- |Normal Depends on| |128030 Severity|Affects Some People |Affects Many People --- Comment #2 from Kubilay Kocak --- This actually depends on bug 128030 (IPSec in GENERIC *at all*) first Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D128030 [Bug 128030] [ipsec] Enable IPSec in GENERIC kernel configuration --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 14 05:41:12 2016 Return-Path: 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 01781C0FF67 for ; Fri, 14 Oct 2016 05:41:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 E49ECB0B for ; Fri, 14 Oct 2016 05:41:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9E5f4sT027580 for ; Fri, 14 Oct 2016 05:41:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 128030] [ipsec] Enable IPSec in GENERIC kernel configuration Date: Fri, 14 Oct 2016 05:41:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: conf X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: feature, patch X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: gnn@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: blocked Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Oct 2016 05:41:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D128030 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |212018 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212018 [Bug 212018] Enable IPSEC_NAT_T in GENERIC kernel configuration --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 14 09:00:40 2016 Return-Path: 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 ED26DC112F5; Fri, 14 Oct 2016 09:00:40 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9ACFEF82; Fri, 14 Oct 2016 09:00:40 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id u9E90aqQ076254; Fri, 14 Oct 2016 11:00:37 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id A3008E9B; Fri, 14 Oct 2016 11:00:36 +0200 (CEST) Message-ID: <58009EB4.30708@omnilan.de> Date: Fri, 14 Oct 2016 11:00:36 +0200 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: FreeBSD Net , FreeBSD Stable Subject: vale-ctl(-8), ifconfig(8), SIOCAIFADDR: Invalid argument [utilizing netmap(4) providing virtual switches+interfaces to BHyVe] Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Fri, 14 Oct 2016 11:00:37 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Oct 2016 09:00:41 -0000 Dear all, I found great papers about netmap(4)s desigen and implementation details, and I'm sure it's one other masterpeace of rizzo-quality :-) Thanks to all participants for that great code! To be honest, I haven't read all of that, because I'm short in time and my first mission is to see if FreeBSD 11 will replace some of my ESXi machines. One key element seems netmap(4). It's quiet hard to find userland documentation. So far, I've discovered that there are three essential tools waiting in _usr/src/tools/tools/netmap_ to be compiled (resulting in *./vale-ctl*, *./bridge*, *./pkt-gen*) While the latter is often referenced in netmap(4) documentation, it's not of interest for me, because I'll be doing real-world performance tests and I'm convinced that all the impressive numbers presented in the netmap documentation are valid :-) So *vale-ctl(-8)* seems to be of interest (I'm using (-8) becaus currently there is no man8 part (I guess that's the reason for these tools not beeing integrated into base binaries)) Accidentally I found out that 'vale-ctl -n testif0' creates a artificial interface, which is reported by ifconfig(8): testif0: flags=8801 metric 0 mtu 1500 options=80000 ether 00:be:eb:8d:f8:00 nd6 options=21 But I can't assign a IP address: 'ifconfig testif0 203.0.113.1/24' ifconfig: ioctl (SIOCAIFADDR): Invalid argument I guess couldn't geti the picture of the netmap(4) world yet. Probably, testif0 is available only in netmap(4) world, not in "host world". I'm assuming, because I found vale-ctl(-8)s "-h" switch. So another very little peace I'm aware of the netmap(4) world, is how to attach physical interfaces to virtual switches: '/usr/src/tools/tools/netmap/vale-ctl -a vale0:em1' Now vale-ctl(-8) shows: bdg_ctl [149] bridge:0 port:0 vale0:em1 /* To share my experience: One cannot use any other than vale[[:digit:]] for defining the on-demand to be created virtual switch instance, so e.g. "vale-ctl -a vale-test:em1" doesn't work, although found in netmap(4) man page in FreeBSD-11: »valeXXX:YYY (arbitrary XXX and YYY) the file descriptor is bound to port YYY of a VALE switch called XXX, both dynamically created if necessary. The string cannot exceed IFNAMSIZ characters, and YYY cannot be the name of any existing OS network interface« I was about to give up on netmap(4) investigations because I thought it isn't production ready yet (in FreeBSD), since even andding the first physical interface fails: '/usr/src/tools/tools/netmap/vale-ctl -a vale-test:em1' vale-test:em1: Invalid argument Probably accidentally I used vale[[:digit:]] instead and wondered whay it suddenly works… To get back to vale-ctl(-8)s "-h" switch: */ If I add a physical interface with -h instead of -a, the host's IP stack doesn't get disconnected from the interface, so it's still usable by host applications and vale-ctl(-8) lists one line more: bdg_ctl [149] bridge:0 port:0 vale0:em1 bdg_ctl [149] bridge:0 port:1 vale0:em1^ So my assumption that netmap(4) lives decapsuled from the well known FreeBSD IP world. Now my question: How can I plug a jail's or vmm's artificial interface to a VALE virtual switch, bridging frames to real-world via physical interfaces? (the latter part should work with vale-ctl -h vale0:em1, but what interface to use for jail(8) vnet.interface and how to create/attach?) Thanks, -harry From owner-freebsd-net@freebsd.org Fri Oct 14 10:59:33 2016 Return-Path: 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 D068EC11A89 for ; Fri, 14 Oct 2016 10:59:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 BA900A02 for ; Fri, 14 Oct 2016 10:59:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9EAxW6n018210 for ; Fri, 14 Oct 2016 10:59:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212283] oversized IP datagrams on raw socket with IP_RAWOUTPUT hang network interface drivers Date: Fri, 14 Oct 2016 10:59:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RC1 X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: mat@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Oct 2016 10:59:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212283 --- Comment #16 from Mathieu Arnold --- This is still a problem on 11.0-RELEASE-p1 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 14 11:14:40 2016 Return-Path: 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 58C44C11ED6 for ; Fri, 14 Oct 2016 11:14:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 47C2C259 for ; Fri, 14 Oct 2016 11:14:40 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9EBEdim096688 for ; Fri, 14 Oct 2016 11:14:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212283] oversized IP datagrams on raw socket with IP_RAWOUTPUT hang network interface drivers Date: Fri, 14 Oct 2016 11:14:40 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? X-Bugzilla-Changed-Fields: flagtypes.name version bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Oct 2016 11:14:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212283 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |mfc-stable11? Version|11.0-RC1 |11.0-STABLE Status|New |Open --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 14 12:01:45 2016 Return-Path: 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 06EFBC10344 for ; Fri, 14 Oct 2016 12:01:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 A03DC83F for ; Fri, 14 Oct 2016 12:01:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9EC1hje043268 for ; Fri, 14 Oct 2016 12:01:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 212283] oversized IP datagrams on raw socket with IP_RAWOUTPUT hang network interface drivers Date: Fri, 14 Oct 2016 12:01:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: tuexen@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: mfc-stable11? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Oct 2016 12:01:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212283 Michael Tuexen changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tuexen@freebsd.org --- Comment #17 from Michael Tuexen --- (In reply to Gleb Smirnoff from comment #12) Normally the kernel does fragmentation for raw IP packets. So I would prefe= r to keep that. But can't we check that the length provided in the send call mat= ches the length in the IP header. If there is a mismatch, return an error to the user (indicating EINVAL)? That way the user gets an indication that some information was inconsistent. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 14 13:08:56 2016 Return-Path: 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 E50C5C11728; Fri, 14 Oct 2016 13:08:56 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-oi0-x241.google.com (mail-oi0-x241.google.com [IPv6:2607:f8b0:4003:c06::241]) (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 A8BE3391; Fri, 14 Oct 2016 13:08:56 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-oi0-x241.google.com with SMTP id d132so7502769oib.2; Fri, 14 Oct 2016 06:08:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DzbAULD0FK8r0nJDWyxtYJQ0zBLG9Erw+7jm9OkOCPI=; b=pNb3r3tP4i14GiQbQkKCAkg1k//VU0L0+ub47TseVSAQ9K3Cct8Y+3CQYP2a7gzKH/ a6F029BJIqyAZYsSvJuUljsuznJT/TF5c4BdwL/OkvyeoNhEqPIkg/Rls8r+oYk9+5Q3 Hl+5kHqzvbAJDObtL0cyK1QYTvhNCHRAnHK60pL7Eta2ytbYi6G3xwQHo7zqVbeuz9Pu VygcnnACANnJvFKQRFHZn/Y/OO+swr9Wto94aDgOydeYZN7DDnaq79M9Pqhz/FTo+MPz CvKtW6sIoTVg7ji+Bm9nkoOZfa6OnBaL2NTuxi5PpwIFiB30iHxaTilu7C6eJsxBjsW6 PP4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DzbAULD0FK8r0nJDWyxtYJQ0zBLG9Erw+7jm9OkOCPI=; b=lDuhyaIKhys0KT6AigvXF5CSewSLCi+0wv5S7WuE1J2FMLUmfds+ZuR7sSEsy9bwge 3ZLuFpudzzJAaRuF2hOmFenSUab6Vs0kg5+4R0KAr7GG3C6mk4tgZ9JSWv8tJ72qT8qC 8QtBsCQCh+NHnja3zMKxhtVrgSU65yssXDI23BLPR+StdR2BVhiGOp9Dv7Zqnd626w0O /suOzo9yy6+6uKVqHBDUGsqidsXGyNypfVIvdv04CEjobtEoRIbqiJBTZ3lmQdpwH17N kUqnhpQYSitaCBT7aocIS+dQIuWjLdCklfkLb/IPHM9Rs/pO25dgZ0ga+NHHSEJ5qDRs DxSg== X-Gm-Message-State: AA6/9RkIhejN+qx6sydDXtsmC6LgTl0WRJsvOxc7F3jV0PyUNaTv4D/VYq4fET1Sm1bHDi3bmF/LTu3o0n/wpQ== X-Received: by 10.157.42.167 with SMTP id e36mr5549928otb.232.1476450536015; Fri, 14 Oct 2016 06:08:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.61.52 with HTTP; Fri, 14 Oct 2016 06:08:55 -0700 (PDT) In-Reply-To: <58009EB4.30708@omnilan.de> References: <58009EB4.30708@omnilan.de> From: Vincenzo Maffione Date: Fri, 14 Oct 2016 15:08:55 +0200 Message-ID: Subject: Re: vale-ctl(-8), ifconfig(8), SIOCAIFADDR: Invalid argument [utilizing netmap(4) providing virtual switches+interfaces to BHyVe] To: Harry Schmalzbauer Cc: FreeBSD Net , FreeBSD Stable , Luigi Rizzo Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Oct 2016 13:08:57 -0000 Hi, Thanks for your feedback. 2016-10-14 11:00 GMT+02:00 Harry Schmalzbauer : > Dear all, > > I found great papers about netmap(4)s desigen and implementation > details, and I'm sure it's one other masterpeace of rizzo-quality :-) > Thanks to all participants for that great code! > > To be honest, I haven't read all of that, because I'm short in time and > my first mission is to see if FreeBSD 11 will replace some of my ESXi > machines. > > One key element seems netmap(4). > It's quiet hard to find userland documentation. > > So far, I've discovered that there are three essential tools waiting in > _usr/src/tools/tools/netmap_ to be compiled > (resulting in *./vale-ctl*, *./bridge*, *./pkt-gen*) > > While the latter is often referenced in netmap(4) documentation, it's > not of interest for me, because I'll be doing real-world performance > tests and I'm convinced that all the impressive numbers presented in the > netmap documentation are valid :-) > > So *vale-ctl(-8)* seems to be of interest (I'm using (-8) becaus > currently there is no man8 part (I guess that's the reason for these > tools not beeing integrated into base binaries)) > > Accidentally I found out that 'vale-ctl -n testif0' creates a artificial > interface, which is reported by ifconfig(8): > testif0: flags=3D8801 metric 0 mtu 1500 > options=3D80000 > ether 00:be:eb:8d:f8:00 > nd6 options=3D21 > > But I can't assign a IP address: 'ifconfig testif0 203.0.113.1/24' > ifconfig: ioctl (SIOCAIFADDR): Invalid argument > > I guess couldn't geti the picture of the netmap(4) world yet. > Probably, testif0 is available only in netmap(4) world, not in "host > world". > I'm assuming, because I found vale-ctl(-8)s "-h" switch. > Yes, those are the "persistent" VALE ports. They are a recent feature, and probably you don't need to use them if you are going to play with Virtual Machines and jails (see below). > > So another very little peace I'm aware of the netmap(4) world, is how to > attach physical interfaces to virtual switches: > '/usr/src/tools/tools/netmap/vale-ctl -a vale0:em1' > Now vale-ctl(-8) shows: > bdg_ctl [149] bridge:0 port:0 vale0:em1 > > /* > To share my experience: One cannot use any other than vale[[:digit:]] > for defining the on-demand to be created virtual switch instance, so > e.g. "vale-ctl -a vale-test:em1" doesn't work, although found in > netmap(4) man page in FreeBSD-11: > =C2=BBvaleXXX:YYY (arbitrary XXX and YYY) > the file descriptor is bound to port YYY of a VALE switch called > XXX, both dynamically created if necessary. The string cannot > exceed IFNAMSIZ characters, and YYY cannot be the name of any > existing OS network interface=C2=AB > > I was about to give up on netmap(4) investigations because I thought it > isn't production ready yet (in FreeBSD), since even andding the first > physical interface fails: '/usr/src/tools/tools/netmap/vale-ctl -a > vale-test:em1' > vale-test:em1: Invalid argument > > Probably accidentally I used vale[[:digit:]] instead and wondered whay > it suddenly works=E2=80=A6 > Correct, this seems to be an inconsistency between the manual and the implementation, we will fix the manual. > > To get back to vale-ctl(-8)s "-h" switch: > */ > > If I add a physical interface with -h instead of -a, the host's IP stack > doesn't get disconnected from the interface, so it's still usable by > host applications and vale-ctl(-8) lists one line more: > bdg_ctl [149] bridge:0 port:0 vale0:em1 > bdg_ctl [149] bridge:0 port:1 vale0:em1^ > So my assumption that netmap(4) lives decapsuled from the well known > FreeBSD IP world. > > > Now my question: > > How can I plug a jail's or vmm's artificial interface to a VALE virtual > switch, bridging frames to real-world via physical interfaces? > (the latter part should work with vale-ctl -h vale0:em1, but what > interface to use for jail(8) vnet.interface and how to create/attach?) > If you use bhyve/vmm, you can attach the VM TAP interface to the VALE switch, as you would do for "em1". Regarding jails, I don't know exactly how networking works there, but I guess epair(4) interface (or similar) are used. If this is the case, then you would have one end of the epair only visible in the jail, and the other end only visible in the "host"; then you could attach the host end to a VALE switch again with "vale-ctl -a". Unfortunately, the performance you would get in any case is not great, because TAP and epair interface do not have netmap "native support". Moreover, when using bhyve, you have to pay the cost of the emulation of the vtnet device, since each packet passes through this device (other than passing across netmap). However, consider the following: a consistent netmap update is going to happen in FreeBSD-CURRENT, in short. This is going to align the netmap code which is now in FreeBSD to the code on the official github repository ( https://github.com/luigirizzo/netmap). Among the new features, there is a new solution for bhyve networking, which will let you attach your bhyve VMs directly to a VALE switch, without paying additional overheads related to TAPs, epairs, and vtnet emulation. You can find additional information, code and performance numbers here: https://wiki.freebsd.org/SummerOfCode2016/PtnetDriverAndDeviceModel. Cheers, Vincenzo > > Thanks, > > -harry > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" --=20 Vincenzo Maffione From owner-freebsd-net@freebsd.org Fri Oct 14 13:38:05 2016 Return-Path: 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 8CD98C108FA; Fri, 14 Oct 2016 13:38:05 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1A3BF24A; Fri, 14 Oct 2016 13:38:04 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id u9EDc2oO078823; Fri, 14 Oct 2016 15:38:02 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 3322AF08; Fri, 14 Oct 2016 15:38:02 +0200 (CEST) Message-ID: <5800DFB9.5030102@omnilan.de> Date: Fri, 14 Oct 2016 15:38:01 +0200 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Vincenzo Maffione CC: FreeBSD Net , FreeBSD Stable , Luigi Rizzo Subject: Re: vale-ctl(-8), ifconfig(8), SIOCAIFADDR: Invalid argument [utilizing netmap(4) providing virtual switches+interfaces to BHyVe] References: <58009EB4.30708@omnilan.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Fri, 14 Oct 2016 15:38:03 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 14 Oct 2016 13:38:05 -0000 Bezüglich Vincenzo Maffione's Nachricht vom 14.10.2016 15:08 (localtime): > Hi, > > Thanks for your feedback. > … >> Accidentally I found out that 'vale-ctl -n testif0' creates a artificial >> interface, which is reported by ifconfig(8): >> testif0: flags=8801 metric 0 mtu 1500 >> options=80000 >> ether 00:be:eb:8d:f8:00 >> nd6 options=21 >> >> But I can't assign a IP address: 'ifconfig testif0 203.0.113.1/24' >> ifconfig: ioctl (SIOCAIFADDR): Invalid argument >> >> I guess couldn't geti the picture of the netmap(4) world yet. >> Probably, testif0 is available only in netmap(4) world, not in "host >> world". >> I'm assuming, because I found vale-ctl(-8)s "-h" switch. >> > > Yes, those are the "persistent" VALE ports. They are a recent feature, and > probably you don't need to use them if you are going to play with Virtual > Machines and jails (see below). Hello Vincenzo, thank you very much for your help!!! … >> Now my question: >> >> How can I plug a jail's or vmm's artificial interface to a VALE virtual >> switch, bridging frames to real-world via physical interfaces? >> (the latter part should work with vale-ctl -h vale0:em1, but what >> interface to use for jail(8) vnet.interface and how to create/attach?) >> > > If you use bhyve/vmm, you can attach the VM TAP interface to the VALE > switch, as you would do for "em1". Regarding jails, I don't know exactly > how networking works there, but I guess epair(4) interface (or similar) are > used. If this is the case, then you would have one end of the epair only > visible in the jail, and the other end only visible in the "host"; then you I'm familar with epair(4), but not with tap(4). I don't understand the man page for tap, perhaps I should read pty(4)… But I guess I don't have to know the details of tap(4), since you confirmed that it can be connected to VALE. So one could summarize: VALE (as part of netmap(4)) can act as a if_bridge(4) replacement in FreeBSD-10/11, keeping everything else involved untouched. Please correct me if I'm wrong. > could attach the host end to a VALE switch again with "vale-ctl -a". > Unfortunately, the performance you would get in any case is not great, > because TAP and epair interface do not have netmap "native support". > Moreover, when using bhyve, you have to pay the cost of the emulation of > the vtnet device, since each packet passes through this device (other than > passing across netmap). I understand, thanks. In fact, I expected that at first hand, but have had some oddities with if_bridge(4) some years ago, so I thought I'd better try something new ;-) Can I expect any resource savings over if_bridge(4)? I guess if so, the ammount isn't relevant considering the whole bhyve scenarium. > However, consider the following: a consistent netmap update is going to > happen in FreeBSD-CURRENT, in short. This is going to align the netmap code > which is now in FreeBSD to the code on the official github repository ( > https://github.com/luigirizzo/netmap). Among the new features, there is a > new solution for bhyve networking, which will let you attach your bhyve VMs > directly to a VALE switch, without paying additional overheads related to > TAPs, epairs, and vtnet emulation. You can find additional information, > code and performance numbers here: > https://wiki.freebsd.org/SummerOfCode2016/PtnetDriverAndDeviceModel. Thanks for that hint! I guess it's about ptnetmap(4)? I read papers but haven't considered it could be production-ready for FreeBSD in the near future. It's extremely interesting and I'd love to be eraly adopter, but my (ESXi) setups are currently doing well and I don't have spare time or any business project to try out… :-( Is it likely that there will a MFC happen? Or will it be a exclusive 12.0 feature? If ptnetmap will be MFCd I'll definitely give it a try next summer and stay with 11.0 for my replacement machines for now. Otherwise I'm unsure… best, -Harry From owner-freebsd-net@freebsd.org Sat Oct 15 07:32:05 2016 Return-Path: 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 D43B1C125F2; Sat, 15 Oct 2016 07:32:05 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 986F8928; Sat, 15 Oct 2016 07:32:05 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-oi0-x22b.google.com with SMTP id y2so161956221oie.0; Sat, 15 Oct 2016 00:32:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=75ToIbowHPkVtbCDF6Fe5mSLlbDBvtVurs9POYokY34=; b=yI257TKxuK8hKhI71LR3jZc5MzOITSkrKOWV43GVJinsrLdRkzNGwvmNuQhm+GxyTw a3qtMtCdA4eIzmTxfcQqTcp0JiufmRCI1S7o24HwlfzVGVOu0l+JbPc3F9/nub0JJEE+ AmpIjqrN0dR/wvkZ1wXGOG1EhyMVy1bp4nkoWonsdQkx/2anK6ARUzWk07EFo/MB9qdc AzfNK9RFr0VIC1g3XH5vy6xjULe7NYfOjW5gzNlRX5RE+ZEg+6eW46qvWf1EfsBTkJw/ 4nem0QOrmPgSnXXUJCAZ0bQ5ilRXssQ8zCeXiZMharu1s/2qSbI3MPYZ3x76RMQ4wEPD hmQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=75ToIbowHPkVtbCDF6Fe5mSLlbDBvtVurs9POYokY34=; b=MarY9jWA6eC02WUDZNssrQzKfxenUTD8UeTtbG/Q76uaPdZypX4eudXXjqQlLT1Z+d wwxmxK72TzcajDizhGtaC6FJ+jnSv+S13KCpx2GVxTW4Paun/MF8Vl5IYT8b72RNmWSK IPDTco8tvrJws+KyuKn+Bsuduc7C1UizSeDci6+X8cMh7y4gp9kJPjX6lOK9AleK4ZeA jrWGDQWjHI5t+NWD+fjJvjINW+zXX5RiLr2H++Hfx9dstZZFF1HYaTxTCsZGmhDGhgON hqu33l+dUfMWhiHXSht3cWWlxuPXjkX0d88p8o3APro0M+UClq2OydgLdajIG8MypJKd vhCA== X-Gm-Message-State: AA6/9RkEo8zjtff9osfDR88Z3tWashqJSdxjDFs919f8opQ0AjvjM6I5Cg8aU1LcNZo2Tdry+NEMoqQMv5zJfg== X-Received: by 10.157.47.232 with SMTP id b37mr8503831otd.67.1476516724794; Sat, 15 Oct 2016 00:32:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.61.52 with HTTP; Sat, 15 Oct 2016 00:32:04 -0700 (PDT) In-Reply-To: <5800DFB9.5030102@omnilan.de> References: <58009EB4.30708@omnilan.de> <5800DFB9.5030102@omnilan.de> From: Vincenzo Maffione Date: Sat, 15 Oct 2016 09:32:04 +0200 Message-ID: Subject: Re: vale-ctl(-8), ifconfig(8), SIOCAIFADDR: Invalid argument [utilizing netmap(4) providing virtual switches+interfaces to BHyVe] To: Harry Schmalzbauer Cc: FreeBSD Net , FreeBSD Stable , Luigi Rizzo Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Oct 2016 07:32:05 -0000 2016-10-14 15:38 GMT+02:00 Harry Schmalzbauer : > Bez=C3=BCglich Vincenzo Maffione's Nachricht vom 14.10.2016 15:08 (localt= ime): > > Hi, > > > > Thanks for your feedback. > > > =E2=80=A6 > >> Accidentally I found out that 'vale-ctl -n testif0' creates a artifici= al > >> interface, which is reported by ifconfig(8): > >> testif0: flags=3D8801 metric 0 mtu 1500 > >> options=3D80000 > >> ether 00:be:eb:8d:f8:00 > >> nd6 options=3D21 > >> > >> But I can't assign a IP address: 'ifconfig testif0 203.0.113.1/24' > >> ifconfig: ioctl (SIOCAIFADDR): Invalid argument > >> > >> I guess couldn't geti the picture of the netmap(4) world yet. > >> Probably, testif0 is available only in netmap(4) world, not in "host > >> world". > >> I'm assuming, because I found vale-ctl(-8)s "-h" switch. > >> > > > > Yes, those are the "persistent" VALE ports. They are a recent feature, > and > > probably you don't need to use them if you are going to play with Virtu= al > > Machines and jails (see below). > > Hello Vincenzo, > > thank you very much for your help!!! > > > =E2=80=A6 > >> Now my question: > >> > >> How can I plug a jail's or vmm's artificial interface to a VALE virtua= l > >> switch, bridging frames to real-world via physical interfaces? > >> (the latter part should work with vale-ctl -h vale0:em1, but what > >> interface to use for jail(8) vnet.interface and how to create/attach?) > >> > > > > If you use bhyve/vmm, you can attach the VM TAP interface to the VALE > > switch, as you would do for "em1". Regarding jails, I don't know exactl= y > > how networking works there, but I guess epair(4) interface (or similar) > are > > used. If this is the case, then you would have one end of the epair onl= y > > visible in the jail, and the other end only visible in the "host"; then > you > > I'm familar with epair(4), but not with tap(4). > I don't understand the man page for tap, perhaps I should read pty(4)=E2= =80=A6 > But I guess I don't have to know the details of tap(4), since you > confirmed that it can be connected to VALE. > It's not necessary to understand the details. However, a TAP device is conceptually similar to the two ends of an epair, with the difference that in the TAP a network interface (e.g. tap0) is conecptually "connected" back-to-back to a file descriptor. The file descriptor is written/read by the hypervisor (to inject/intercept packets to/from the network stack), while the tap0 interface can be attached to if_bridge. > > So one could summarize: > VALE (as part of netmap(4)) can act as a if_bridge(4) replacement in > FreeBSD-10/11, keeping everything else involved untouched. > Please correct me if I'm wrong. > For simple cases yes. if_bridge may have features that are not supported by netmap (i.e. configure ports as VLAN access ports). Moreover, if_bridge has a interface (br0), whereas VALE bridges doesn't. > > > > could attach the host end to a VALE switch again with "vale-ctl -a". > > Unfortunately, the performance you would get in any case is not great, > > because TAP and epair interface do not have netmap "native support". > > Moreover, when using bhyve, you have to pay the cost of the emulation o= f > > the vtnet device, since each packet passes through this device (other > than > > passing across netmap). > > I understand, thanks. > In fact, I expected that at first hand, but have had some oddities with > if_bridge(4) some years ago, so I thought I'd better try something new ;-= ) > Can I expect any resource savings over if_bridge(4)? I guess if so, the > ammount isn't relevant considering the whole bhyve scenarium. > I don't think you can expect resource savings in terms of memory, since netmap is trading off memory for performance, using pre-allocation rather than dynamic allocation (of each packet). I don't know what happens in terms of CPU saving, but using TAPs, epair and vtnet makes the system as a whole not really efficient (as if_bridge), so you may end up with nothing. > > > > However, consider the following: a consistent netmap update is going to > > happen in FreeBSD-CURRENT, in short. This is going to align the netmap > code > > which is now in FreeBSD to the code on the official github repository ( > > https://github.com/luigirizzo/netmap). Among the new features, there is > a > > new solution for bhyve networking, which will let you attach your bhyve > VMs > > directly to a VALE switch, without paying additional overheads related = to > > TAPs, epairs, and vtnet emulation. You can find additional information, > > code and performance numbers here: > > https://wiki.freebsd.org/SummerOfCode2016/PtnetDriverAndDeviceModel. > > Thanks for that hint! > I guess it's about ptnetmap(4)? I read papers but haven't considered it > could be production-ready for FreeBSD in the near future. > It's extremely interesting and I'd love to be eraly adopter, but my > (ESXi) setups are currently doing well and I don't have spare time or > any business project to try out=E2=80=A6 :-( > Yes, it's ptnetmap. However, bhyve is going to have support for VALE ports anyway (even without ptnetmap), as QEMU already does, so at least you will be able to replace TAPs with VALE ports (while still using vtnet devices for the VM). > > Is it likely that there will a MFC happen? Or will it be a exclusive > 12.0 feature? If ptnetmap will be MFCd I'll definitely give it a try > next summer and stay with 11.0 for my replacement machines for now. > Otherwise I'm unsure=E2=80=A6 > No idea, I guess this is up to the committers. First step, however, is to merge in CURRENT :) Cheers, Vincenzo > > best, > > -Harry > --=20 Vincenzo Maffione From owner-freebsd-net@freebsd.org Sat Oct 15 09:42:10 2016 Return-Path: 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 D212CC12D61; Sat, 15 Oct 2016 09:42:10 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 82FFF78F; Sat, 15 Oct 2016 09:42:09 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id u9F9g7jn092749; Sat, 15 Oct 2016 11:42:07 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 94F7C197; Sat, 15 Oct 2016 11:42:06 +0200 (CEST) Message-ID: <5801F9EE.1000407@omnilan.de> Date: Sat, 15 Oct 2016 11:42:06 +0200 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Vincenzo Maffione CC: FreeBSD Net , FreeBSD Stable , Luigi Rizzo Subject: Re: vale-ctl(-8), ifconfig(8), SIOCAIFADDR: Invalid argument [utilizing netmap(4) providing virtual switches+interfaces to BHyVe] References: <58009EB4.30708@omnilan.de> <5800DFB9.5030102@omnilan.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Sat, 15 Oct 2016 11:42:07 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 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, 15 Oct 2016 09:42:10 -0000 Bezüglich Vincenzo Maffione's Nachricht vom 15.10.2016 09:32 (localtime): > 2016-10-14 15:38 GMT+02:00 Harry Schmalzbauer : … >> I'm familar with epair(4), but not with tap(4). >> I don't understand the man page for tap, perhaps I should read pty(4)… >> But I guess I don't have to know the details of tap(4), since you >> confirmed that it can be connected to VALE. >> > > It's not necessary to understand the details. However, a TAP device is > conceptually similar to the two ends of an epair, with the difference that > in the TAP a network interface (e.g. tap0) is conecptually "connected" > back-to-back to a file descriptor. The file descriptor is written/read by > the hypervisor (to inject/intercept packets to/from the network stack), > while the tap0 interface can be attached to if_bridge. Hi Vincenzo, thanks for your explanation! >> >> So one could summarize: >> VALE (as part of netmap(4)) can act as a if_bridge(4) replacement in >> FreeBSD-10/11, keeping everything else involved untouched. >> Please correct me if I'm wrong. >> > > For simple cases yes. if_bridge may have features that are not supported by > netmap (i.e. configure ports as VLAN access ports). Moreover, if_bridge has > a interface (br0), whereas VALE bridges doesn't. Again, thank you for your time! (R)STP comes to my mind (which I don't need any more). And I'm not sure if VALE really lacks that, but I guess it wouldn't match VALEs philosophy/design at all… … >>> https://github.com/luigirizzo/netmap). Among the new features, there is >> a >>> new solution for bhyve networking, which will let you attach your bhyve >> VMs >>> directly to a VALE switch, without paying additional overheads related to >>> TAPs, epairs, and vtnet emulation. You can find additional information, >>> code and performance numbers here: >>> https://wiki.freebsd.org/SummerOfCode2016/PtnetDriverAndDeviceModel. >> >> Thanks for that hint! >> I guess it's about ptnetmap(4)? I read papers but haven't considered it >> could be production-ready for FreeBSD in the near future. >> It's extremely interesting and I'd love to be eraly adopter, but my >> (ESXi) setups are currently doing well and I don't have spare time or >> any business project to try out… :-( >> > > Yes, it's ptnetmap. However, bhyve is going to have support for VALE ports > anyway (even without ptnetmap), as QEMU already does, so at least you will > be able to replace TAPs with VALE ports (while still using vtnet devices > for the VM). Oic, I wasn't aware that there will be a VALE-vtnet direct path! That is really great news :-) And a big achievment for guests preferring "standard" drivers, ptnetmap could limit the guest OS choice I guess. For now, I'm happy having been in touch with netmap(4) – at least with a very little fraction of natmap – but I'll stay the legacy way utilizing if_bridge(4) and see if there are still oddities and try to find some time to track them down (involving LACP, VLANs, Jumbo-Frames and IPv6 – that was the problematic constellation) Since I have extra PHYs, I can do PCIe-passthrough like before (with ESXi) for some special guests. I'm looking forward to find out how this works with bhyve! Best, -Harry