From owner-freebsd-net@freebsd.org Sun Oct 16 06:16:51 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 7452CC143A1 for ; Sun, 16 Oct 2016 06:16:51 +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 638163D1 for ; Sun, 16 Oct 2016 06:16:51 +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 u9G6Go0W059757 for ; Sun, 16 Oct 2016 06:16:51 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: Sun, 16 Oct 2016 06:16:51 +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: 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: Sun, 16 Oct 2016 06:16:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213232 Hiren Panchasara changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |glebius@FreeBSD.org --- Comment #6 from Hiren Panchasara --- Now with r306769, len is int32_t so it can actually have -ve value, I am se= eing panic at /* * This KASSERT is here to catch edge cases at a well defined place. * Before, those had triggered (random) panic conditions further do= wn. */ KASSERT(len >=3D 0, ("[%s:%d]: len < 0", __func__, __LINE__)); Now, putting a bit of debugs above that I figured that at following path in 'else' case the len becomes -ve if (tso) { } else { len =3D tp->t_maxseg - optlen - ipoptlen; sendalot =3D 1; } I found that tp-t_maxseg =3D 2, optlen =3D 12, ipoptlen =3D 0 resulting in = len =3D -10. Clearly, t_maxseg which is supposed to be representing MSS at '2' looks wro= ng. I wonder if the changes in https://svnweb.freebsd.org/base?view=3Drevision&revision=3D293284 somewhere= caused this. Still investigating. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Sun Oct 16 09:29:04 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 8CF4DC12FC4; Sun, 16 Oct 2016 09:29:04 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::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 4F09F3D6; Sun, 16 Oct 2016 09:29:04 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-oi0-x231.google.com with SMTP id d132so182801939oib.2; Sun, 16 Oct 2016 02:29:04 -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=1mzgs/x2ybum58ghVWHFPJD2QjKo7A2h1u3IUBSovDo=; b=pB2iBQ8ZDeGn7VNIE4ETQ6WWkqO8ALECyl3M5h1BFrg0hD3JcPMdB6O7S8Z9mkJGlR 5bXuF8UbGxHkbIZoABUk6ZiU2IvDsqS9tHaRRDyFpWa7TDDd+UwgHyx23rH8ADfRn4bC HJfLA5FyPcw1MZ/smsZMT5jeEkRNwCXFDNMREyJIr4a7M2Yxjiv28LlgxBh7sYG5jetj pj1O7NFs9SQL0wXWwe9ixyfte5th5hfoEVwz/M+wWyG3n9+em9L8nIaSV8N62lYxU2Gw j5wufg9myvU//59WP0rEhJWp8XLzP0HuSKmmQCuTWEhTcuwaEh4wmpALFJyabwAKLOAj Auqg== 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=1mzgs/x2ybum58ghVWHFPJD2QjKo7A2h1u3IUBSovDo=; b=mo8eYKXyySivzsiSSW+gsnBBn2cTC2Q5gbKMJWzIWNgtUIQJVsqsRQ9Oy3a3D8rMvc to/iyjUr2UhRzcQJNKyCulMZrAiPf6Hf+nU5OMfyyafX+qS7tpQoIi39dZpG5st30vYr 2ji3l9S0dFGYdByFTXVAXhM7uPEhF4gB06kRU1fiWBJZz+ZCUOwn+uHyYqQbw61mVf1+ amfpU6Ln4FqZAVOqgFEwD3R1J1X9Z3FLjl8XfkbT9pId6HbmXg8++q8ZbQ+6POLr4OnX xtv8cxb/pBOl1cPIzst64AArxN1ouRmQaY8RTR+8OLiKbrLpLRfxnfMCuA8/XQ3Rm4rz oKxw== X-Gm-Message-State: AA6/9RmvlhKd/NZmVM2EU4jqGO8A6UQd1lVXf5KPK24UAb8RpBKrO8iE7amoaGe7g1tOIs1kPqo9+SpMVmzOmQ== X-Received: by 10.202.74.79 with SMTP id x76mr13574558oia.77.1476610143656; Sun, 16 Oct 2016 02:29:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.61.52 with HTTP; Sun, 16 Oct 2016 02:29:03 -0700 (PDT) In-Reply-To: <5801F9EE.1000407@omnilan.de> References: <58009EB4.30708@omnilan.de> <5800DFB9.5030102@omnilan.de> <5801F9EE.1000407@omnilan.de> From: Vincenzo Maffione Date: Sun, 16 Oct 2016 11:29:03 +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: Sun, 16 Oct 2016 09:29:04 -0000 2016-10-15 11:42 GMT+02:00 Harry Schmalzbauer : > Bez=C3=BCglich Vincenzo Maffione's Nachricht vom 15.10.2016 09:32 (localt= ime): > > 2016-10-14 15:38 GMT+02:00 Harry Schmalzbauer : > > =E2=80=A6 > >> 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. > > 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 supporte= d > 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=E2=80=A6 > Well, VALE is a programmable switch, meaning that you can plug in a custom forwarding function (which is just a C function). The default forwarding function implements an L2 learning bridge without STP, because it is thought to be used as the preferred hypervisor virtual switch, so no L2 connectivity loops, and the STP comes with an overhead. If you really wish to have VALE with STP, you could define your own custom forwarding function that implements it. > > =E2=80=A6 > >>> https://github.com/luigirizzo/netmap). Among the new features, there > is > >> a > >>> new solution for bhyve networking, which will let you attach your bhy= ve > >> VMs > >>> directly to a VALE switch, without paying additional overheads relate= d > to > >>> TAPs, epairs, and vtnet emulation. You can find additional informatio= n, > >>> 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 i= t > >> 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 device= s > > 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. > Yes ptnetmap is supported on QEMU and bhyve, and as a gues you can use only FreeBSD and Linux, at the moment. > > For now, I'm happy having been in touch with netmap(4) =E2=80=93 at least= with a > very little fraction of natmap =E2=80=93 but I'll stay the legacy way uti= lizing > 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 =E2= =80=93 > 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! > > No idea, but also ptnetmap is able to do that: not only you can pass-through a VALE port, but also you can pass-through a physical interface. Cheers, Vincenzo > Best, > > -Harry > --=20 Vincenzo Maffione From owner-freebsd-net@freebsd.org Sun Oct 16 18:17:20 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 25A2CC149BD for ; Sun, 16 Oct 2016 18:17:20 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (unknown [IPv6:2001:6a0:10f:1::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "plan-b.pwste.edu.pl", Issuer "plan-b.pwste.edu.pl" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 97E6D1EFE for ; Sun, 16 Oct 2016 18:17:18 +0000 (UTC) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: from plan-b.pwste.edu.pl (zarychtam@localhost [127.0.0.1]) by plan-b.pwste.edu.pl (8.15.2/8.15.2) with ESMTPS id u9GIHD9N095444 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 16 Oct 2016 20:17:13 +0200 (CEST) (envelope-from zarychtam@plan-b.pwste.edu.pl) Received: (from zarychtam@localhost) by plan-b.pwste.edu.pl (8.15.2/8.15.2/Submit) id u9GIHDgj095443 for freebsd-net@freebsd.org; Sun, 16 Oct 2016 20:17:13 +0200 (CEST) (envelope-from zarychtam) Date: Sun, 16 Oct 2016 20:17:13 +0200 From: Marek Zarychta To: freebsd-net@freebsd.org Subject: pfr_update_stats: assertion failed. Message-ID: <20161016181713.GA95110@plan-b.pwste.edu.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline User-Agent: Mutt/1.7.0 (2016-08-17) 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, 16 Oct 2016 18:17:20 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable The issue occurred first two years ago, after upgrade from 8 to 9 branch. Now this i386 machine is running 11.0-STABLE and despite it was compiled with "WITHOUT_ASSERT_DEBUG=3Dyes", still from time to time message buffer is fed with: pfr_update_stats: assertion failed. pfr_update_stats: assertion failed. pfr_update_stats: assertion failed. pfr_update_stats: assertion failed. pfr_update_stats: assertion failed. pfr_update_stats: assertion failed. pfr_update_stats: assertion failed. PF rules here are a bit complex, machine acts as a gateway for RFC-1918 networks and just does the job. pfctl -sr | wc -l 498 Any advice how to debug this or find triggering PF rule? =20 Why setting "WITHOUT_ASSERT_DEBUG=3Dyes" is ignored by PF code? --=20 Marek Zarychta --FCuugMFkClbJLl1L Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJYA8QlAAoJEHWf7P/9Uo0swawH/13xmfxh4S9NRtD7REdlWbR6 23x00UW0SjBshBG6Ex/Ly78yG5BDctVhxyOTnI6DZJDeczz14oUZrJGe/L0hoOWa orJrrZzekxTc15j4CGyjRFqX1SUVlrnc2FBL2z20gJ2bTl4RiJ35Y4E9lZvaZF6G oEgN5+fBHzaHIaCXje0XloLHXu9+AdnAExKxDjzF+OLivH10MmC7KuzOPnzp9FUf ZzRshy5+gTGB17qgabd5dcofQiG17x2j0icYEaXbe2TZ8twOSXGZ6I5Pu2hZCeoh b0e1gcTovydkQpj2je86Is4XEjj1oo/CcENEQ2QUJ7BZx6s4KdC7t1SGem3yyN0= =N0tI -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- From owner-freebsd-net@freebsd.org Sun Oct 16 21: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 997ECC14C7E for ; Sun, 16 Oct 2016 21:00: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 8C36A188F for ; Sun, 16 Oct 2016 21:00: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 u9GL01dC044653 for ; Sun, 16 Oct 2016 21:00:40 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201610162100.u9GL01dC044653@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, 16 Oct 2016 21:00:40 +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, 16 Oct 2016 21:00:40 -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 Mon Oct 17 16:53: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 7D4F9C15FA1 for ; Mon, 17 Oct 2016 16:53:54 +0000 (UTC) (envelope-from jjasen@gmail.com) Received: from mail-yw0-x241.google.com (mail-yw0-x241.google.com [IPv6:2607:f8b0:4002:c05::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 3CA1BEB0 for ; Mon, 17 Oct 2016 16:53:54 +0000 (UTC) (envelope-from jjasen@gmail.com) Received: by mail-yw0-x241.google.com with SMTP id e5so7089612ywc.3 for ; Mon, 17 Oct 2016 09:53:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=Id3eGIbvSwZL+7P3U+e918K364vzzlxkFkKZW6Ga09I=; b=WM2Xo/fXbRlkq20t2MEo5VZhTukglPlQ8Nd/as47BChGXGNxjEOPN8wJUUkmUUeNjo Urn9GAIjGvezYoU7U1Rs2aBFbTpsgTEYvueBSu+Zi4DMDUEXgsIGH0g5clU7v0qgpNDu tzrHM1GhhsFLvi1a0jZT4pX0ToPbr3YhQ7fmeb2+8wBofKTasEgM7D5m6GpnV88fRWWM ABlpKOzmdNo6zAC9KQ0YnzP+JEcq2wEw2N4vpPnvE27LBnBT/2jjUw/sF9zfSrx+gbxX wgOKUxelnnTPlUVrQkYlrmO5GMoCtLE+7KPFNIgEjjUVuLTU5Huhbcfuaoc8dJl0wzTu yarw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=Id3eGIbvSwZL+7P3U+e918K364vzzlxkFkKZW6Ga09I=; b=Ny+00GMQ+O+bjtfXupeVNCMgEDoq8q/X2KmvpCFeQ7/m6V6F4L5EefFKxphbKoTS5n OLSfBoZZgJ6jLK5snWi2yusr7K2uEDvURbhU7GX0BjPKVDq1enaOb2532wddCN7Rju9l ociLtSpwFv8L1q937IB6LzuEpSBoLffU3W/KvrT2iZdQWnKO9Kyqrc015OIRcqbZqpXT jVgtt099ax3AjR2DLRehpwL2IGf9wOQ/GX/qPVSn3hMQeQSopHA8UhbjKkd0mLidxeyG G16Emvz4qm+nLWTeK4gJ5I0A8NmiXuGscmWcmcQbTC2XO9z/VHgi7H2NlbYRPN/4o/Fl jAxQ== X-Gm-Message-State: AA6/9RkGkWdEgJvUTFSCwx5G5JDd4SftYIf48ZCngzV/q39Vbo8Zz3tDxoMuPzx8Ds7kSA== X-Received: by 10.13.234.66 with SMTP id t63mr26843992ywe.170.1476723233485; Mon, 17 Oct 2016 09:53:53 -0700 (PDT) Received: from [10.1.29.108] ([198.119.59.10]) by smtp.googlemail.com with ESMTPSA id b188sm12137175ywc.16.2016.10.17.09.53.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 17 Oct 2016 09:53:52 -0700 (PDT) To: FreeBSD Net From: John Jasen Subject: quick question on carp(4) Message-ID: Date: Mon, 17 Oct 2016 12:53:50 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 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: Mon, 17 Oct 2016 16:53:54 -0000 I was reading on OpenBSD carp, where it has load-balancing capabilities versus failover. =46rom a cursory inspection, in the FreeBSD handbook, carp(4), or ifconfig(8) -- I didn't immediately see similar capabilities. Does FreeBSD carp support active/active load-balanced configurations? From owner-freebsd-net@freebsd.org Mon Oct 17 19:57:39 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 A9B9AAF46F5 for ; Mon, 17 Oct 2016 19:57:39 +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 98D2E5F4 for ; Mon, 17 Oct 2016 19:57:39 +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 u9HJvdFw095546 for ; Mon, 17 Oct 2016 19:57:39 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: Mon, 17 Oct 2016 19:57:39 +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: geezabiscuit2@hotmail.com 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: 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: Mon, 17 Oct 2016 19:57:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212018 --- Comment #3 from Darryn Nicol --- (In reply to Kubilay Kocak from comment #2) I'm not sure why that hasn't been closed off yet but IPSEC made it into GEN= ERIC in 11.0. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Mon Oct 17 22:41: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 1F449C15B7A for ; Mon, 17 Oct 2016 22:41: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 0EAFECCC for ; Mon, 17 Oct 2016 22:41: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 u9HMfePM061091 for ; Mon, 17 Oct 2016 22:41:40 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: Mon, 17 Oct 2016 22:41:40 +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: woodsb02@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: 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: Mon, 17 Oct 2016 22:41:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212018 Ben Woods changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |woodsb02@freebsd.org --- Comment #4 from Ben Woods --- (In reply to Darryn Nicol from comment #3) I believe PR128030 is still open as it is awaiting someone to decide whethe= r it should be merged into the stable 9/10 branches. For the clarity of anyone reading this bug report in the future, Darryn's comment was regarding why PR128030 had not been closed. Note that this PR21= 2018 still had not been committed in FreeBSD 11 (IPSEC_NAT_T is still not in the GENERIC kernel configuration). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Oct 18 02:40:49 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 71428C16677 for ; Tue, 18 Oct 2016 02:40:49 +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 60C8C2B6 for ; Tue, 18 Oct 2016 02:40:49 +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 u9I2emke074513 for ; Tue, 18 Oct 2016 02:40:49 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: Tue, 18 Oct 2016 02:40:48 +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: commit-hook@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: Tue, 18 Oct 2016 02:40:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213232 --- Comment #7 from commit-hook@freebsd.org --- A commit references this bug: Author: hiren Date: Tue Oct 18 02:40:25 UTC 2016 New revision: 307545 URL: https://svnweb.freebsd.org/changeset/base/307545 Log: Make sure tcp_mss() has the same check as tcp_mss_update() to have t_maxs= eg set to at least 64. This is still just a coverup to avoid kernel panic and not an actual fix. PR: 213232 Reviewed by: glebius MFC after: 1 week Sponsored by: Limelight Networks Differential Revision: https://reviews.freebsd.org/D8272 Changes: head/sys/netinet/tcp_input.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Tue Oct 18 11:43:30 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 78263C1739A for ; Tue, 18 Oct 2016 11:43:30 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: from relay.ibs.dn.ua (relay.ibs.dn.ua [148.251.53.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.new-ukraine.org", Issuer "smtp.new-ukraine.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1AF8D140 for ; Tue, 18 Oct 2016 11:43:29 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: on behalf of honored client by relay.ibs.dn.ua with ESMTP id u9IBhJUT045828 for on Tue, 18 Oct 2016 14:43:20 +0300 (EEST) Message-ID: <20161018144313.45827@relay.ibs.dn.ua> Date: Tue, 18 Oct 2016 14:43:13 +0300 From: "Zeus Panchenko" To: cc: Subject: is lagg (re+wlan) working on 11.0-RELEASE? Organization: I.B.S. LLC Reply-To: "Zeus Panchenko" X-Attribution: zeus Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw 15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5 lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M 1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6 7tXQAAAAASUVORK5CYII= X-Mailer: MH-E 8.3.1; nil; GNU Emacs 24.3.1 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-NewUkraine-Agent: mailfromd (7.99.92) X-NewUkraine-URL: https://mail.prozora-kraina.org/smtp.html X-NewUkraine-VirStat: NO X-NewUkraine-VirScan: ScanPE, ScanELF, ScanOLE2, ScanMail, PhishingSignatures, ScanHTML, ScanPDF X-NewUkraine-SpamStat: NO X-NewUkraine-SpamScore: -1.900 of 3.500 X-NewUkraine-SpamKeys: AWL,BAYES_00,NO_RECEIVED,NO_RELAYS 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, 18 Oct 2016 11:43:30 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, please advise after moving to 11.0-RELEASE from 11-CURRENT (which was succefully used more than year) I faced trouble I'm stumbled upon ... I'm using lagg(4) in failover to set up roaming between wired and wireless networks, just as manual describes (last example) and all was working perfectly on 11-CURRENT now on 11.0-RELEASE (with the same configuration) wlan interface is unable to associate and auth against AP, while wired link works as expected worth to mention, both interfaces are working well separately, outside lagg here is my configuration: =2D ---[ /etc/rc.conf quotation start ]------------------------------------= ------- wlans_ath0=3D"wlan0" wlandebug_wlan0=3D"auth+assoc" cloned_interfaces=3D"lagg0" ifconfig_re0=3D"UP" ifconfig_ath0=3D"ether 10:11:12:13:14:15" # it is MAC address of wired inte= rface ifconfig_wlan0=3D"WPA up" ifconfig_lagg0=3D"laggproto failover laggport re0 laggport wlan0 SYNCDHCP" =2D ---[ /etc/rc.conf quotation end ]------------------------------------= ------- here is what ifconfig shows =2D ---[ ifconfig output quotation start ]---------------------------------= ---------- re0: flags=3D8843 metric 0 mtu 1500 options=3D8209b ether 10:11:12:13:14:15 nd6 options=3D29 media: Ethernet autoselect (100baseTX ) status: active wlan0: flags=3D8843 metric 0 mtu 15= 00 ether 10:11:12:13:14:15 nd6 options=3D29 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 7 (2442 MHz 11g ht/20) regdomain 96 indoor ecm authmode WPA1+WPA2/802.11i privacy ON deftxkey UNDEF txpower 20 bmiss 7 scanvalid 60 protmode CTS ampdulimit 8k ampdudensity 8 shortgi -stbctx stbcrx wme burst roaming MANUAL groups: wlan=20 lagg0: flags=3D8843 metric 0 mtu 15= 00 ether 10:11:12:13:14:15 inet 10.0.0.254 netmask 0xfffffe00 broadcast 192.168.137.255=20 nd6 options=3D29 media: Ethernet autoselect status: active groups: lagg=20 laggproto failover lagghash l2,l3,l4 laggport: re0 flags=3D5 laggport: wlan0 flags=3D0<> =2D ---[ ifconfig output quotation end ]---------------------------------= ---------- here is what wlandebug writes to syslog =2D ---[ /var/log/messages quotation start ]-------------------------------= ------------ Oct 18 13:59:06 zeushp wpa_supplicant[373]: wlan0: CTRL-EVENT-SSID-TEMP-DIS= ABLED id=3D2 ssid=3D"ABCDE" auth_failures=3D81 duration=3D300 reason=3DCONN= _FAILED Oct 18 13:59:54 zeushp kernel: ath0: ath_edma_recv_tasklet: sc_inreset_cnt = > 0; skipping Oct 18 14:04:12 zeushp wpa_supplicant[373]: wlan0: CTRL-EVENT-SSID-REENABLE= D id=3D2 ssid=3D"ABCDE" Oct 18 14:04:12 zeushp wpa_supplicant[373]: wlan0: Trying to associate with= aa:bb:cc:dd:ee:ff (SSID=3D'ABCDE' freq=3D2442 MHz) Oct 18 14:04:12 zeushp kernel: wlan0: [aa:bb:cc:dd:ee:ff] station assoc via= MLME Oct 18 14:04:12 zeushp kernel: wlan0: [aa:bb:cc:dd:ee:ff] switch station to= HT20 channel 2442/0x10480 Oct 18 14:04:22 zeushp wpa_supplicant[373]: wlan0: Authentication with aa:b= b:cc:dd:ee:ff timed out. Oct 18 14:04:22 zeushp wpa_supplicant[373]: wlan0: CTRL-EVENT-DISCONNECTED = bssid=3Daa:bb:cc:dd:ee:ff reason=3D3 locally_generated=3D1 Oct 18 14:04:22 zeushp kernel: wlan0: [aa:bb:cc:dd:ee:ff] station deauth vi= a MLME (reason: 3 (sending STA is leaving/has left IBSS or ESS)) =2D ---[ /var/log/messages quotation end ]-------------------------------= ------------ and here is what hostapd on AP (OpenWRT) says: =2D ---[ hostapd log quotation start ]-------------------------------------= ------ AP hostapd debug: STA 10:11:12:13:14:15 IEEE 802.11: did not acknowledge authentication response =2D ---[ hostapd log quotation end ]-------------------------------------= ------ =2D --=20 Zeus V. Panchenko jid:zeus@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlgGCtEACgkQr3jpPg/3oyrPBACgnnXFPAgkOc6d2PLVjQS6ZBdu bBMAn3ybl+5dX2fZZ+X8HTLWdliiMrAN =3D46f5 =2D----END PGP SIGNATURE----- From owner-freebsd-net@freebsd.org Tue Oct 18 12:15:27 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 501F4C14244 for ; Tue, 18 Oct 2016 12:15:27 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from homobox.opal.com (opalcom-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:113d::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "opal.com", Issuer "OpalCA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C703260 for ; Tue, 18 Oct 2016 12:15:26 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from shibato (ANice-654-1-95-204.w86-203.abo.wanadoo.fr [86.203.234.204]) (authenticated bits=0) by homobox.opal.com (8.15.2/8.15.2) with ESMTPSA id u9ICFJHu021990 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Tue, 18 Oct 2016 08:15:21 -0400 (EDT) (envelope-from fbsd@opal.com) Date: Tue, 18 Oct 2016 14:15:13 +0200 From: "J.R. Oldroyd" To: "Zeus Panchenko" Cc: Subject: Re: is lagg (re+wlan) working on 11.0-RELEASE? Message-ID: <20161018141513.4936f1ea@shibato> In-Reply-To: <20161018144313.45827@relay.ibs.dn.ua> References: <20161018144313.45827@relay.ibs.dn.ua> X-Mailer: Claws Mail 3.14.0 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (homobox.opal.com [100.64.0.6]); Tue, 18 Oct 2016 08:15:23 -0400 (EDT) X-Spam-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_00, FSL_HELO_NON_FQDN_1,RCVD_IN_SORBS_DUL,RDNS_DYNAMIC shortcircuit=no autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on homobox.opal.com 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, 18 Oct 2016 12:15:27 -0000 On Tue, 18 Oct 2016 14:43:13 +0300 "Zeus Panchenko" wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I'm using lagg(4) in failover to set up roaming between wired and > wireless networks, just as manual describes (last example) and all > was working perfectly on 11-CURRENT > > now on 11.0-RELEASE (with the same configuration) wlan interface is > unable to associate and auth against AP, while wired link works as > expected > It does not work as you have it configured, see PR#213207. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213207 There is a work-around. Configure the re interface with the MAC address of the wlan instead of the other way around. -jr From owner-freebsd-net@freebsd.org Tue Oct 18 16:23:20 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 9C05BC16C59 for ; Tue, 18 Oct 2016 16:23:20 +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 761EE309 for ; Tue, 18 Oct 2016 16:23:20 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 7262AC16C57; Tue, 18 Oct 2016 16:23:20 +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 71CB2C16C56 for ; Tue, 18 Oct 2016 16:23:20 +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 1F310308 for ; Tue, 18 Oct 2016 16:23:20 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mail-qk0-x22c.google.com with SMTP id n189so301096447qke.0 for ; Tue, 18 Oct 2016 09:23:20 -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=q0rWp310sjm7IqDAc5fubBBvLPIV2GYOrG88es6GEMk=; b=cxrA4CT0lXoPtUPOSCQUpAVV308/9Vsk27oAqKqg1h6aNJVXul7fB8qdgH7fVk5qRn Ge345FwVx32M7yFf9Viw8jcaVmLIYL4OzNMWPdnGxKDvIj//a0ZfWZ7XoQkOSvr+MLrP tizHCTok84ieTLVSX18MrbKpTx2Lthu9VOWB8q8Mip0r/NpYaaI2ER0dTvfzV0JUSozf tTuGvvptTycBjmC/VIjSdOpSO+DYA8ZwZazlnc1imgMcogSGot5wDnMJPYJ8GYYwXO+6 +KsTvFyDlZkez7N0u5B+mTn1aBxY6cjjIIeNmH6PcQpiTNMOcDFtf6pT7l44OlPjcew8 zqdQ== 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=q0rWp310sjm7IqDAc5fubBBvLPIV2GYOrG88es6GEMk=; b=i202rJ9ObizCkTFzu4S+1C90U5UHc77a948Fqm4PsOeQe+OHSHgd/rtQCZxp2yFlua WF6uU60ltvJ5tZWTWsnxrH6DsAlWmPHNiTTNXpdEMTgRTP2w3jQJ0grIE4RRbRVoQ5t2 JZ2lCAt9LaPcHbfdJUznlfv10DAHXEcZxFNCnJT0dVA52ml/3jyU7YE6gAYBCZOFeeDT zlhMtUCHCFYhXHgC/ERnayei0uHNmHD3QQbcM5JMEWiU9MkejOJMoEkXEDm6h+yGA+y0 jy0+kJdKP/z5FXUlZjvyx63jihTKKk9ctTFMw3d4yBkx8RELpub1qeKnpSUNHcyhlaLE j7Vg== X-Gm-Message-State: AA6/9Rmzmo0CHME7lFoc0jdqY5ZMbqucv2AErkhSjV8XF8lbsavOn5wV7vThcU1/amUemps7VSSSr7ob8f2elw== X-Received: by 10.55.25.211 with SMTP id 80mr1321783qkz.230.1476807798855; Tue, 18 Oct 2016 09:23:18 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.166.26 with HTTP; Tue, 18 Oct 2016 09:23:18 -0700 (PDT) In-Reply-To: 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: Tue, 18 Oct 2016 14:23:18 -0200 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: Tue, 18 Oct 2016 16:23:20 -0000 Hi guys, I have some update about this issue. After my last email i had 3 crashes. Two of them had the same message on kernel debug: (kgdb) list *0xffffffff8228c918 0xffffffff8228c918 is in trim_map_seg_compare (/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/trim_map.c:108). 103 trim_map_seg_compare(const void *x1, const void *x2) 104 { 105 const trim_seg_t *s1 =3D x1; 106 const trim_seg_t *s2 =3D x2; 107 108 if (s1->ts_start < s2->ts_start) { 109 if (s1->ts_end > s2->ts_start) 110 return (0); 111 return (-1); 112 } Current language: auto; currently minimal (kgdb) bt #0 doadump (textdump=3D) at pcpu.h:221 #1 0xffffffff80ad8e69 in kern_reboot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0xffffffff80ad941b in vpanic (fmt=3D, ap=3D) at /usr/src/sys/kern/kern_shutdown.c:759 #3 0xffffffff80ad9253 in panic (fmt=3D0x0) at /usr/src/sys/kern/kern_shutdown.c:690 #4 0xffffffff80fa0d31 in trap_fatal (frame=3D0xfffffe02374957f0, eva=3D4294967343) at /usr/src/sys/amd64/amd64/trap.c:841 #5 0xffffffff80fa0f23 in trap_pfault (frame=3D0xfffffe02374957f0, usermode=3D0) at /usr/src/sys/amd64/amd64/trap.c:691 #6 0xffffffff80fa04cc in trap (frame=3D0xfffffe02374957f0) at /usr/src/sys/amd64/amd64/trap.c:442 #7 0xffffffff80f84141 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #8 0xffffffff8228c918 in trim_map_seg_compare (x1=3D0xfffffe0237495920, x2=3D0x100000007) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/trim_map.c:108 #9 0xffffffff821a98e1 in avl_find (tree=3D, value=3D, where=3D0x0) at /usr/src/sys/cddl/contrib/opensolaris/common/avl/avl.c:268 #10 0xffffffff8228ce9e in trim_map_write_start (zio=3D= ) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/trim_map.c:363 #11 0xffffffff822592df in zio_vdev_io_start (zio=3D0xfffff802191ea000) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:2866 #12 0xffffffff82255b26 in zio_execute (zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1556 #13 0xffffffff822551e9 in zio_nowait (zio=3D0xfffff802191ea000) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1610 #14 0xffffffff8223c738 in vdev_queue_io_done (zio=3D) = at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:884 #15 0xffffffff822594a9 in zio_vdev_io_done (zio=3D0xfffff8006daad000) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:2895 #16 0xffffffff82255b26 in zio_execute (zio=3D) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1556 #17 0xffffffff80b363ca in taskqueue_run_locked (queue=3D) at /usr/src/sys/kern/subr_taskqueue.c:449 #18 0xffffffff80b372d8 in taskqueue_thread_loop (arg=3D) at /usr/src/sys/kern/subr_taskqueue.c:703 #19 0xffffffff80a90055 in fork_exit (callout=3D0xffffffff80b371f0 , arg=3D0xfffff8001006b920, frame=3D0xfffffe0237495c= 00) at /usr/src/sys/kern/kern_fork.c:1038 #20 0xffffffff80f8467e in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:611 #21 0x0000000000000000 in ?? () (kgdb) up 8 #8 0xffffffff8228c918 in trim_map_seg_compare (x1=3D0xfffffe0237495920, x2=3D0x100000007) at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/trim_map.c:108 108 if (s1->ts_start < s2->ts_start) { But my last crash had a different message: (kgdb) list *0xffffffff80b3a89c 0xffffffff80b3a89c is in turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837). 832 833 /* 834 * Transfer the blocked list to the pending list. 835 */ 836 mtx_lock_spin(&td_contested_lock); 837 TAILQ_CONCAT(&ts->ts_pending, &ts->ts_blocked[queue], td_lockq); 838 mtx_unlock_spin(&td_contested_lock); 839 840 /* 841 * Give a turnstile to each thread. The last thread gets Current language: auto; currently minimal (kgdb) bt #0 doadump (textdump=3D) at pcpu.h:221 #1 0xffffffff80ad8e69 in kern_reboot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:366 #2 0xffffffff80ad941b in vpanic (fmt=3D, ap=3D) at /usr/src/sys/kern/kern_shutdown.c:759 #3 0xffffffff80ad9253 in panic (fmt=3D0x0) at /usr/src/sys/kern/kern_shutdown.c:690 #4 0xffffffff80fa0d31 in trap_fatal (frame=3D0xfffffe0237384870, eva=3D48)= at /usr/src/sys/amd64/amd64/trap.c:841 #5 0xffffffff80fa0f23 in trap_pfault (frame=3D0xfffffe0237384870, usermode=3D0) at /usr/src/sys/amd64/amd64/trap.c:691 #6 0xffffffff80fa04cc in trap (frame=3D0xfffffe0237384870) at /usr/src/sys/amd64/amd64/trap.c:442 #7 0xffffffff80f84141 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:236 #8 0xffffffff80b3a89c in turnstile_broadcast (ts=3D0x0, queue=3D1) at /usr/src/sys/kern/subr_turnstile.c:837 #9 0xffffffff80ad48cf in __rw_wunlock_hard (c=3D0xfffff8024f3c2960, tid=3D, file=3D, line=3D) at /usr/src/sys/kern/kern_rwlock.c:1027 #10 0xffffffff80e1a75c in vm_map_delete (map=3D, start=3D, end=3D) at /usr/src/sys/vm/vm_map.c:2960 #11 0xffffffff80e1828e in vmspace_exit (td=3D) at /usr/src/sys/vm/vm_map.c:3077 #12 0xffffffff80a88686 in exit1 (td=3D0xfffff80015533a00, rval=3D268849920, signo=3D0) at /usr/src/sys/kern/kern_exit.c:398 #13 0xffffffff80a87e1d in sys_sys_exit (td=3D0x0, uap=3D) at /usr/src/sys/kern/kern_exit.c:178 #14 0xffffffff80fa168e in amd64_syscall (td=3D, traced=3D0) at subr_syscall.c:135 #15 0xffffffff80f8442b in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:396 #16 0x0000000800b661aa in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) up 8 #8 0xffffffff80b3a89c in turnstile_broadcast (ts=3D0x0, queue=3D1) at /usr/src/sys/kern/subr_turnstile.c:837 837 TAILQ_CONCAT(&ts->ts_pending, &ts->ts_blocked[queue], td_lockq); As you can see we are dealing with random crashes. I feel i'm not moving forward here. it's not a hardware problem because i have 3 different servers with same issue. Donald, did you have a chance to try 11-RELEASE? Any other behavior? Anyone have some idea that could help? Thanks. On Thu, Oct 13, 2016 at 12:24 PM, Cassiano Peixoto < peixotocassiano@gmail.com> wrote: > 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= =99ve 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 g= uys 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 n= ot >>> 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/droppin= g >>> 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. (t= here >>> 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 tri= ed >>> 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 >>> 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 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 >>> 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 18 17:10: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 43AAAC17032 for ; Tue, 18 Oct 2016 17:10:50 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: from relay.ibs.dn.ua (relay.ibs.dn.ua [148.251.53.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.new-ukraine.org", Issuer "smtp.new-ukraine.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C6ECAA55 for ; Tue, 18 Oct 2016 17:10:49 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: on behalf of honored client by relay.ibs.dn.ua with ESMTP id u9IHAjqw072697 on Tue, 18 Oct 2016 20:10:46 +0300 (EEST) Message-ID: <20161018201040.72694@relay.ibs.dn.ua> Date: Tue, 18 Oct 2016 20:10:40 +0300 From: "Zeus Panchenko" To: "J.R. Oldroyd" Cc: Subject: Re: is lagg (re+wlan) working on 11.0-RELEASE? In-reply-to: Your message of Tue, 18 Oct 2016 14:15:13 +0200 <20161018141513.4936f1ea@shibato> References: <20161018144313.45827@relay.ibs.dn.ua> <20161018141513.4936f1ea@shibato> Organization: I.B.S. LLC Reply-To: "Zeus Panchenko" X-Attribution: zeus Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw 15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5 lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M 1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6 7tXQAAAAASUVORK5CYII= X-Mailer: MH-E 8.3.1; nil; GNU Emacs 24.3.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-NewUkraine-Agent: mailfromd (7.99.92) X-NewUkraine-URL: https://mail.prozora-kraina.org/smtp.html X-NewUkraine-VirStat: NO X-NewUkraine-VirScan: ScanPE, ScanELF, ScanOLE2, ScanMail, PhishingSignatures, ScanHTML, ScanPDF X-NewUkraine-SpamStat: NO X-NewUkraine-SpamScore: -1.900 of 3.500 X-NewUkraine-SpamKeys: AWL,BAYES_00,NO_RECEIVED,NO_RELAYS 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, 18 Oct 2016 17:10:50 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable thanks for quick reply J.R. Oldroyd wrote: > There is a work-around. Configure the re interface with the MAC > address of the wlan instead of the other way around. I done it and here is what happens: 1. I boot notebook with wire *not* plugged in wlan is up, associated and authed, network is OK 2. I plug wire and network becomes stale 3. I run `tcpdump -ni lagg0' to see what's going on and oh, wonder, network comes back lo life! so ... either to not to use lagg or run tcpdump constantly ... it is rather weird :( =2D-=20 Zeus V. Panchenko jid:zeus@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlgGV48ACgkQr3jpPg/3oyrUfQCfVcQAFdepbqWSHyeMRNctxvi0 +dUAoKEAcjKGGVKUnSmGpoypNduij7j8 =Y/PB -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-net@freebsd.org Wed Oct 19 08:46: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 63CFCC18F03 for ; Wed, 19 Oct 2016 08:46:16 +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 537BEC20 for ; Wed, 19 Oct 2016 08:46:16 +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 u9J8kGFG084804 for ; Wed, 19 Oct 2016 08:46:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 200420] [igb] igb0: Watchdog timeout -- resetting Date: Wed, 19 Oct 2016 08:46:16 +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-RELEASE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: arcadiy@ivanovy.net 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: Wed, 19 Oct 2016 08:46:16 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200420 --- Comment #7 from Arcadiy Ivanov --- There appears to be some indication that the X11SBA series has a hardware b= ug in a PCI-E controller supplying igb1-4 (not affecting igb1).=20 See https://sourceforge.net/p/e1000/bugs/502/ --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 19 08:47:04 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 656C8C18FAB for ; Wed, 19 Oct 2016 08:47:04 +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 554DBD11 for ; Wed, 19 Oct 2016 08:47:04 +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 u9J8l3UJ086289 for ; Wed, 19 Oct 2016 08:47:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 200420] [igb] igb0: Watchdog timeout -- resetting Date: Wed, 19 Oct 2016 08:47:04 +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-RELEASE X-Bugzilla-Keywords: IntelNetworking X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: arcadiy@ivanovy.net 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: Wed, 19 Oct 2016 08:47:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200420 --- Comment #8 from Arcadiy Ivanov --- *not affecting igb0 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 19 15:01:31 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 F297CC18F87 for ; Wed, 19 Oct 2016 15:01:31 +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 DE1ED36C for ; Wed, 19 Oct 2016 15:01:31 +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 u9JF1V1X089649 for ; Wed, 19 Oct 2016 15:01:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213606] LACP not working with qlogic BCM57800 Date: Wed, 19 Oct 2016 15:01:31 +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 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: keywords 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, 19 Oct 2016 15:01:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213606 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression 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 19 15:07:21 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 DBFE1C18210 for ; Wed, 19 Oct 2016 15:07:21 +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 CBDFF9DC for ; Wed, 19 Oct 2016 15:07: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 u9JF7Llw036812 for ; Wed, 19 Oct 2016 15:07:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213606] LACP not working with qlogic BCM57800 Date: Wed, 19 Oct 2016 15:07:22 +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 Only Me X-Bugzilla-Who: smh@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: 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, 19 Oct 2016 15:07:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213606 Steven Hartland changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |smh@FreeBSD.org --- Comment #1 from Steven Hartland --- what does ifconfig lagg0 report? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 19 15:26:39 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 2E9CDC18A66 for ; Wed, 19 Oct 2016 15:26:39 +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 1E8DCC3F for ; Wed, 19 Oct 2016 15:26:39 +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 u9JFQcrb067861 for ; Wed, 19 Oct 2016 15:26:38 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213606] LACP not working with qlogic BCM57800 Date: Wed, 19 Oct 2016 15:26: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: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eentsalu@gmail.com 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: Wed, 19 Oct 2016 15:26:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213606 --- Comment #2 from Kristjan --- lagg0: flags=3D8843 metric 0 mtu 15= 00 ether b0:83:fe:e5:fa:82 inet 172.21.50.2 netmask 0xffffff00 broadcast 172.21.50.255 nd6 options=3D29 media: Ethernet autoselect status: active groups: lagg laggproto lacp lagghash l2,l3,l4 laggport: bxe0 flags=3D0<> laggport: bxe1 flags=3D0<> --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 19 15:35: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 71595C18E67 for ; Wed, 19 Oct 2016 15:35: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 6130B697 for ; Wed, 19 Oct 2016 15:35: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 u9JFZsJP087548 for ; Wed, 19 Oct 2016 15:35:54 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213606] LACP not working with qlogic BCM57800 Date: Wed, 19 Oct 2016 15:35: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: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: smh@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: Wed, 19 Oct 2016 15:35:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213606 --- Comment #3 from Steven Hartland --- and for bxe0 / bxe1? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 19 15:45:51 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 0387EC181D8 for ; Wed, 19 Oct 2016 15:45:51 +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 E789FD48 for ; Wed, 19 Oct 2016 15:45:50 +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 u9JFjoPA009298 for ; Wed, 19 Oct 2016 15:45:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213606] LACP not working with qlogic BCM57800 Date: Wed, 19 Oct 2016 15:45:51 +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 Only Me X-Bugzilla-Who: eentsalu@gmail.com 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: Wed, 19 Oct 2016 15:45:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213606 --- Comment #4 from Kristjan --- bxe0: flags=3D8843 metric 0 mtu 1500 ether b0:83:fe:e5:fa:82 nd6 options=3D29 media: Ethernet autoselect (10Gbase-SR ) status: active bxe1: flags=3D8843 metric 0 mtu 1500 ether b0:83:fe:e5:fa:82 nd6 options=3D29 media: Ethernet autoselect (10Gbase-SR ) status: active --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 19 16:20:24 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 7ADBFC1800B for ; Wed, 19 Oct 2016 16:20:24 +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 6AE2CB1E for ; Wed, 19 Oct 2016 16:20:24 +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 u9JGKOJX019385 for ; Wed, 19 Oct 2016 16:20:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213606] LACP not working with qlogic BCM57800 Date: Wed, 19 Oct 2016 16:20: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: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: smh@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: Wed, 19 Oct 2016 16:20:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213606 --- Comment #5 from Steven Hartland --- That looks odd, no options=3D for the nic's. Can you try something silly, assign a private IP to the bxe0 and see if that changes things? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 19 16:25: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 BB968C183FA for ; Wed, 19 Oct 2016 16:25:56 +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 AA536299 for ; Wed, 19 Oct 2016 16:25:56 +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 u9JGPtqG033245 for ; Wed, 19 Oct 2016 16:25:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 211962] bxe driver queue soft hangs and flooding tx_soft_errors Date: Wed, 19 Oct 2016 16:25:55 +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: needs-qa, patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: matt.joras@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- 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: Wed, 19 Oct 2016 16:25:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211962 --- Comment #5 from Matt Joras --- The changeset I authored for Isilon has been committed by davidcs. Hopefully this will alleviate the issues in the PR. https://svnweb.freebsd.org/base?view=3Drevision&revision=3D307578 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 19 16:26:01 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 A4265C18420 for ; Wed, 19 Oct 2016 16:26:01 +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 93B2A324 for ; Wed, 19 Oct 2016 16:26:01 +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 u9JGQ1hv033373 for ; Wed, 19 Oct 2016 16:26:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213606] LACP not working with qlogic BCM57800 Date: Wed, 19 Oct 2016 16:26:01 +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 Only Me X-Bugzilla-Who: smh@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: Wed, 19 Oct 2016 16:26:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213606 --- Comment #6 from Steven Hartland --- Looks like it may be an old issues see: https://forums.freenas.org/index.php?threads/lacp-lagg-issues-with-9-3.2622= 7/ --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 19 17:19: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 EFA45C19A9F for ; Wed, 19 Oct 2016 17:19: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 DF7BBDF9 for ; Wed, 19 Oct 2016 17:19: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 u9JHJtg4091675 for ; Wed, 19 Oct 2016 17:19:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213606] LACP not working with qlogic BCM57800 Date: Wed, 19 Oct 2016 17:19:56 +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 Only Me X-Bugzilla-Who: eentsalu@gmail.com 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: Wed, 19 Oct 2016 17:19:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213606 --- Comment #7 from Kristjan --- Nothing changes and it seems to be the same problem yes. laggproto loadbala= nce is working fine. LACP was also working in 10.3 so something between 10.3 and 11.0 changed th= at. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Wed Oct 19 18:07: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 26AF7C1983B for ; Wed, 19 Oct 2016 18:07:07 +0000 (UTC) (envelope-from david@aogsquid.ucsd.edu) Received: from iport-acv6-out.ucsd.edu (iport-acv6-out.ucsd.edu [132.239.0.13]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "iport-acv1.ucsd.edu", Issuer "InCommon RSA Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 06037F21 for ; Wed, 19 Oct 2016 18:07:06 +0000 (UTC) (envelope-from david@aogsquid.ucsd.edu) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2ApDQD7tQdY/4j574RcHAEBBAEBCgEBgz4BAQEBAR2BSY0/qX+BOIIIARaICj8UAQIBAQEBAQEBYiiFDBVANgIFFgsCCwMCAQIBWAgBAYhOpwiPbYljBoNZgQeLR4YPglsFjz2KUJBxjxKMfoQAHjZHBgiDAhAPgXOGYAaCKQEBAQ X-IPAS-Result: A2ApDQD7tQdY/4j574RcHAEBBAEBCgEBgz4BAQEBAR2BSY0/qX+BOIIIARaICj8UAQIBAQEBAQEBYiiFDBVANgIFFgsCCwMCAQIBWAgBAYhOpwiPbYljBoNZgQeLR4YPglsFjz2KUJBxjxKMfoQAHjZHBgiDAhAPgXOGYAaCKQEBAQ X-IronPort-AV: E=Sophos;i="5.31,367,1473145200"; d="scan'208";a="179582153" X-Spam-Status: No X-Spam-Level: Received: from act-bufferout-b1.ucsd.edu ([132.239.249.136]) by iport-acv6-out.ucsd.edu with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Oct 2016 11:06:42 -0700 Received: from Davids-MacBook-Pro.local (unknown [137.110.201.97]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by act-bufferout-b1.ucsd.edu (Postfix) with ESMTPS id CA8AB144106; Wed, 19 Oct 2016 11:06:41 -0700 (PDT) Message-ID: <5807B630.1060806@aogsquid.ucsd.edu> Date: Wed, 19 Oct 2016 11:06:40 -0700 From: David Horwitt User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Adding RTL8153 support to rue(4) USB to Ethernet driver Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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, 19 Oct 2016 18:07:07 -0000 Reviving a thread from June,2015... My brand-spanking new XPS 13 has a dongle for the Thunderbolt port that implements a RTL8153, which is recognized by my system (FreeBSD 11.0-RELEASE-p1 #8: Tue Oct 18 22:57:49 PDT 2016): Oct 19 07:11:01 TWE6 kernel: ugen1.3: at usbus1 Oct 19 07:11:02 TWE6 kernel: ugen1.4: at usbus1 Oct 19 07:11:02 TWE6 kernel: uhub3: on usbus1 Oct 19 07:11:02 TWE6 kernel: uhub3: 4 ports with 3 removable, self powered Oct 19 07:11:03 TWE6 kernel: ugen1.5: at usbus1 Oct 19 07:11:03 TWE6 kernel: cdce0: on usbus1 Oct 19 07:11:03 TWE6 kernel: ue0: on cdce0 Oct 19 07:11:03 TWE6 kernel: ue0: Ethernet address: 00:24:9b:1d:90:e5 NB: the MAC address matches that inscribed on the dongle. usbconfig info: ugen1.5: at usbus1, cfg=1 md=HOST spd=SUPER (5.0Gbps) pwr=ON (64mA) NB: cfg=1 which should be correct for if_cdce and RTL8153. This was verified by 'usbconfig -d 1.5 dump_curr_config_desc" (complete configs dumped below). I manually set the IP address: ue0: flags=8843 metric 0 mtu 1500 ether 00:24:9b:1d:90:e5 inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=29 The problem is, "it doesn't work'. Using wireshark on a ping target machine, I can see that the XPS outputs packets (which look correct), but it doesn't seem to be receiving the replies. When I set 'sysctl -a hw.usb.cdce.debug=1' I get a constant (~ 5Hz) stream of "cdce_intr_read_callback: Received 24 bytes" whether there is network traffic or not; when I ping the XPS this message doesn't change. The hardware/cable works OK under Windows. Any guidance is appreciated; TIA David usbconfig -d 1.5 dump_all_config_desc ugen1.5: at usbus1, cfg=1 md=HOST spd=SUPER (5.0Gbps) pwr=ON (64mA) Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0039 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 bmAttributes = 0x00a0 bMaxPower = 0x0020 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0003 bInterfaceClass = 0x00ff bInterfaceSubClass = 0x00ff bInterfaceProtocol = 0x0000 iInterface = 0x0000 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0002 wMaxPacketSize = 0x0400 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Additional Descriptor bLength = 0x06 bDescriptorType = 0x30 bDescriptorSubType = 0x03 RAW dump: 0x00 | 0x06, 0x30, 0x03, 0x00, 0x00, 0x00 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 bmAttributes = 0x0002 wMaxPacketSize = 0x0400 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Additional Descriptor bLength = 0x06 bDescriptorType = 0x30 bDescriptorSubType = 0x03 RAW dump: 0x00 | 0x06, 0x30, 0x03, 0x00, 0x00, 0x00 Endpoint 2 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0003 wMaxPacketSize = 0x0002 bInterval = 0x0008 bRefresh = 0x0000 bSynchAddress = 0x0000 Additional Descriptor bLength = 0x06 bDescriptorType = 0x30 bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x06, 0x30, 0x00, 0x00, 0x02, 0x00 Configuration index 1 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0062 bNumInterfaces = 0x0002 bConfigurationValue = 0x0002 iConfiguration = 0x0000 bmAttributes = 0x00a0 bMaxPower = 0x0020 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0002 bInterfaceSubClass = 0x0006 bInterfaceProtocol = 0x0000 iInterface = 0x0005 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x05, 0x24, 0x00, 0x10, 0x01 Additional Descriptor bLength = 0x05 bDescriptorType = 0x24 bDescriptorSubType = 0x06 RAW dump: 0x00 | 0x05, 0x24, 0x06, 0x00, 0x01 Additional Descriptor bLength = 0x0d bDescriptorType = 0x24 bDescriptorSubType = 0x0f RAW dump: 0x00 | 0x0d, 0x24, 0x0f, 0x03, 0x00, 0x00, 0x00, 0x00, 0x08 | 0xea, 0x05, 0x00, 0x00, 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0083 bmAttributes = 0x0003 wMaxPacketSize = 0x0010 bInterval = 0x0008 bRefresh = 0x0000 bSynchAddress = 0x0000 Additional Descriptor bLength = 0x06 bDescriptorType = 0x30 bDescriptorSubType = 0x00 RAW dump: 0x00 | 0x06, 0x30, 0x00, 0x00, 0x08, 0x00 Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x0000 bNumEndpoints = 0x0000 bInterfaceClass = 0x000a bInterfaceSubClass = 0x0000 bInterfaceProtocol = 0x0000 iInterface = 0x0000 Interface 1 Alt 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x0001 bNumEndpoints = 0x0002 bInterfaceClass = 0x000a bInterfaceSubClass = 0x0000 bInterfaceProtocol = 0x0000 iInterface = 0x0004 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0002 wMaxPacketSize = 0x0400 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Additional Descriptor bLength = 0x06 bDescriptorType = 0x30 bDescriptorSubType = 0x03 RAW dump: 0x00 | 0x06, 0x30, 0x03, 0x00, 0x00, 0x00 Endpoint 1 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0002 bmAttributes = 0x0002 wMaxPacketSize = 0x0400 bInterval = 0x0000 bRefresh = 0x0000 bSynchAddress = 0x0000 Additional Descriptor bLength = 0x06 bDescriptorType = 0x30 bDescriptorSubType = 0x03 RAW dump: 0x00 | 0x06, 0x30, 0x03, 0x00, 0x00, 0x00 From owner-freebsd-net@freebsd.org Wed Oct 19 18:20:51 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 CF5DBC19E01 for ; Wed, 19 Oct 2016 18:20:51 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 98239C1F for ; Wed, 19 Oct 2016 18:20:51 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 2F8AD1FE022; Wed, 19 Oct 2016 20:20:43 +0200 (CEST) Subject: Re: Adding RTL8153 support to rue(4) USB to Ethernet driver To: David Horwitt , freebsd-net@freebsd.org References: <5807B630.1060806@aogsquid.ucsd.edu> From: Hans Petter Selasky Message-ID: <3622755d-b0cd-60bf-0f81-469d06e65595@selasky.org> Date: Wed, 19 Oct 2016 20:25:43 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <5807B630.1060806@aogsquid.ucsd.edu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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, 19 Oct 2016 18:20:51 -0000 On 10/19/16 20:06, David Horwitt wrote: > Reviving a thread from June,2015... > > My brand-spanking new XPS 13 has a dongle for the Thunderbolt port that > implements a RTL8153, which > is recognized by my system (FreeBSD 11.0-RELEASE-p1 #8: Tue Oct 18 > 22:57:49 PDT 2016): > Oct 19 07:11:01 TWE6 kernel: ugen1.3: at usbus1 > Oct 19 07:11:02 TWE6 kernel: ugen1.4: at usbus1 > Oct 19 07:11:02 TWE6 kernel: uhub3: on usbus1 > Oct 19 07:11:02 TWE6 kernel: uhub3: 4 ports with 3 removable, self powered > Oct 19 07:11:03 TWE6 kernel: ugen1.5: at usbus1 > Oct 19 07:11:03 TWE6 kernel: cdce0: on usbus1 > Oct 19 07:11:03 TWE6 kernel: ue0: on cdce0 > Oct 19 07:11:03 TWE6 kernel: ue0: Ethernet address: 00:24:9b:1d:90:e5 > NB: the MAC address matches that inscribed on the dongle. > > usbconfig info: > ugen1.5: at usbus1, cfg=1 md=HOST spd=SUPER > (5.0Gbps) pwr=ON (64mA) > NB: cfg=1 which should be correct for if_cdce and RTL8153. This was > verified by > 'usbconfig -d 1.5 dump_curr_config_desc" (complete configs dumped below). > > I manually set the IP address: > ue0: flags=8843 metric 0 mtu 1500 > ether 00:24:9b:1d:90:e5 > inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 > nd6 options=29 > > The problem is, "it doesn't work'. > > Using wireshark on a ping target machine, I can see that the XPS outputs > packets (which look correct), but it > doesn't seem to be receiving the replies. When I set 'sysctl -a > hw.usb.cdce.debug=1' I get a constant (~ 5Hz) stream > of "cdce_intr_read_callback: Received 24 bytes" whether there is network > traffic or not; when I ping the XPS > this message doesn't change. > Hi, Search the idVendor and idProduct values in the Linux kernel. I think you need to implement some propritary miibus to get it working. CDC ethernet does not define any miibus. --HPS From owner-freebsd-net@freebsd.org Wed Oct 19 21:29: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 585EDC19549 for ; Wed, 19 Oct 2016 21:29:25 +0000 (UTC) (envelope-from glebius@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 450E8DF8 for ; Wed, 19 Oct 2016 21:29:25 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 41881C19548; Wed, 19 Oct 2016 21:29:25 +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 41224C19547 for ; Wed, 19 Oct 2016 21:29:25 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (glebi.us [96.95.210.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1CCC5DF3; Wed, 19 Oct 2016 21:29:21 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id u9JLTEkT030893 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 19 Oct 2016 14:29:14 -0700 (PDT) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id u9JLTEq7030892; Wed, 19 Oct 2016 14:29:14 -0700 (PDT) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 19 Oct 2016 14:29:14 -0700 From: Gleb Smirnoff To: Mike Karels , George Neville-Neil Cc: net@FreeBSD.org Subject: TCP route caching panic Message-ID: <20161019212914.GJ27748@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.7.0 (2016-08-17) 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, 19 Oct 2016 21:29:25 -0000 Hi! I got this panic in a bhyve VM, which was just compiling stuff and had two ssh sessions open. It has static network configuration, one interfaces, one IP address, IPv4 only and it sees only hardware address of the host. So it is minimal possible configuration. It runs with INVARIANTS. As you can see, cached route points to freed lle. Unread portion of the kernel message buffer: Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xffffffff805fff3a stack pointer = 0x0:0xfffffe011c2c1bf0 frame pointer = 0x0:0xfffffe011c2c1de0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 12 (swi4: clock (0 doadump (textdump=250000) at /usr/src/head/sys/kern/kern_shutdown.c:298 298 dumptid = curthread->td_tid; (kgdb) bt #0 doadump (textdump=250000) at /usr/src/head/sys/kern/kern_shutdown.c:298 #1 0xffffffff80348265 in db_fncall_generic (addr=-2141161552, rv=0xfffffe011c2c1330, nargs=0, args=0xfffffe011c2c1340) at /usr/src/head/sys/ddb/db_command.c:581 #2 0xffffffff80347914 in db_fncall (dummy1=-2194255637392, dummy2=false, dummy3=1, dummy4=0xfffffe011c2c1470 "\n") at /usr/src/head/sys/ddb/db_command.c:629 #3 0xffffffff8034727e in db_command (last_cmdp=0xffffffff80e561b0 , cmd_table=0x0, dopager=1) at /usr/src/head/sys/ddb/db_command.c:453 #4 0xffffffff80346e19 in db_command_loop () at /usr/src/head/sys/ddb/db_command.c:506 #5 0xffffffff8034bfda in db_trap (type=9, code=0) at /usr/src/head/sys/ddb/db_main.c:248 #6 0xffffffff8066ad1f in kdb_trap (type=9, code=0, tf=0xfffffe011c2c1b30) at /usr/src/head/sys/kern/subr_kdb.c:654 #7 0xffffffff80a6d06d in trap_fatal (frame=0xfffffe011c2c1b30, eva=0) at /usr/src/head/sys/amd64/amd64/trap.c:832 #8 0xffffffff80a6c710 in trap (frame=0xfffffe011c2c1b30) at /usr/src/head/sys/amd64/amd64/trap.c:585 #9 0xffffffff80a6d78a in trap_check (frame=0xfffffe011c2c1b30) at /usr/src/head/sys/amd64/amd64/trap.c:638 #10 #11 0xffffffff805fff3a in __rw_wlock_hard (c=0xfffff800b1319d10, tid=18446735277663502336, file=0xffffffff80b713d5 "/usr/src/head/sys/net/if_ethersubr.c", line=304) at /usr/src/head/sys/kern/kern_rwlock.c:831 #12 0xffffffff805ff9db in _rw_wlock_cookie (c=0xfffff800b1319d10, file=0xffffffff80b713d5 "/usr/src/head/sys/net/if_ethersubr.c", line=304) at /usr/src/head/sys/kern/kern_rwlock.c:296 #13 0xffffffff807844a3 in ether_output (ifp=0xfffff80002d8f000, m=0xfffff800192aa500, dst=0xfffff8004894eac0, ro=0xfffff8004894eaa0) at /usr/src/head/sys/net/if_ethersubr.c:304 #14 0xffffffff807ded62 in ip_output (m=0xfffff800192aa500, opt=0x0, ro=0xfffff8004894eaa0, flags=0, imo=0x0, inp=0xfffff8004894e910) at /usr/src/head/sys/netinet/ip_output.c:661 #15 0xffffffff808c6bac in tcp_output (tp=0xfffff800b117d3d8) at /usr/src/head/sys/netinet/tcp_output.c:1432 #16 0xffffffff808d925a in tcp_timer_rexmt (xtp=0xfffff800b117d3d8) at /usr/src/head/sys/netinet/tcp_timer.c:856 #17 0xffffffff8062e0c4 in softclock_call_cc (c=0xfffff800b117d640, cc=0xffffffff8107f200 , direct=0) at /usr/src/head/sys/kern/kern_timeout.c:729 #18 0xffffffff8062e78c in softclock (arg=0xffffffff8107f200 ) at /usr/src/head/sys/kern/kern_timeout.c:867 #19 0xffffffff805b49e8 in intr_event_execute_handlers (p=0xfffff80002ca9a50, ie=0xfffff80002c94200) at /usr/src/head/sys/kern/kern_intr.c:1262 #20 0xffffffff805b56a7 in ithread_execute_handlers (p=0xfffff80002ca9a50, ie=0xfffff80002c94200) at /usr/src/head/sys/kern/kern_intr.c:1275 #21 0xffffffff805b54ec in ithread_loop (arg=0xfffff80002ca6f20) at /usr/src/head/sys/kern/kern_intr.c:1356 #22 0xffffffff805b056b in fork_exit (callout=0xffffffff805b53f0 , arg=0xfffff80002ca6f20, frame=0xfffffe011c2c2ac0) at /usr/src/head/sys/kern/kern_fork.c:1038 #23 (kgdb) fr 13 #13 0xffffffff807844a3 in ether_output (ifp=0xfffff80002d8f000, m=0xfffff800192aa500, dst=0xfffff8004894eac0, ro=0xfffff8004894eaa0) at /usr/src/head/sys/net/if_ethersubr.c:304 304 LLE_FREE(lle); (kgdb) p lle $1 = (struct llentry *) 0xfffff800b1319c00 (kgdb) fr 15 #15 0xffffffff808c6bac in tcp_output (tp=0xfffff800b117d3d8) at /usr/src/head/sys/netinet/tcp_output.c:1432 1432 error = ip_output(m, tp->t_inpcb->inp_options, &tp->t_inpcb->inp_route, (kgdb) p tp->t_inpcb->inp_route There is no member named inp_route. (kgdb) p tp->t_inpcb->inp_rtu.inpu_route $4 = {ro_rt = 0xfffff80003df95b0, ro_lle = 0xfffff800b1319c00, ro_prepend = 0x0, ro_plen = 0, ro_flags = 258, ro_mtu = 0, spare = 0, ro_dst = { sa_len = 16 '\020', sa_family = 2 '\002', sa_data = "\000\000\n\006\006\b\000\000\000\000\000\000\000"}} (kgdb) p tp->t_inpcb->inp_rtu.inpu_route->ro_lle $5 = (struct llentry *) 0xfffff800b1319c00 (kgdb) p *tp->t_inpcb->inp_rtu.inpu_route->ro_lle $6 = {lle_next = {le_next = 0xfffff8000388ea00, le_prev = 0xfffff8001706e600}, r_l3addr = {addr4 = {s_addr = 54176312}, addr6 = {__u6_addr = { __u6_addr8 = "8\252:\003\000\370\377\377\001\001\200\000\336\300\255\336", __u6_addr16 = {43576, 826, 63488, 65535, 257, 128, 49374, 57005}, __u6_addr32 = {54176312, 4294965248, 8388865, 3735929054}}}}, r_linkdata = "\000\000\000\000\000\000\000\000\350]d\002\000\376\377\377\336\300\255\336\336\300\255\336", r_hdrlen = 222 '\336', spare0 = "\300\255\336", r_flags = 49374, r_skip_req = 57005, lle_tbl = 0xfffff800033ee000, lle_head = 0xffff0000002d6bbd, lle_free = 0xdeadc0dedeadc0de, la_hold = 0xdeadc0dedeadc0de, la_numheld = 393712128, la_expire = 0, la_flags = 21632, la_asked = 45489, la_preempt = 63488, ln_state = -1, ln_router = 21664, ln_ntick = -1, lle_remtime = -1, lle_hittime = 0, lle_refcnt = 0, ll_addr = 0x0, lle_chain = {le_next = 0x0, le_prev = 0xfffff8001960b300}, lle_timer = {c_links = {le = {le_next = 0xfffff8001715f378, le_prev = 0x0}, sle = { sle_next = 0xfffff8001715f378}, tqe = {tqe_next = 0xfffff8001715f378, tqe_prev = 0x0}}, c_time = -8793120203584, c_precision = 0, c_arg = 0xfffff800b1319cd0, c_func = 0x0, c_lock = 0xfffff800b1319ce0, c_flags = 0, c_iflags = 0, c_cpu = 0}, lle_lock = {lock_object = { lo_name = 0xfffff800b1319cf0 "", lo_flags = 0, lo_data = 0, lo_witness = 0xdeadc0dedeadc0de}, rw_lock = 16045693110842147038}, req_mtx = { lock_object = {lo_name = 0xdeadc0dedeadc0de , lo_flags = 3735929054, lo_data = 3735929054, lo_witness = 0xdeadc0dedeadc0de}, mtx_lock = 16045693110842147038}} (kgdb) -- Totus tuus, Glebius. From owner-freebsd-net@freebsd.org Wed Oct 19 23:36:43 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 20474C19512 for ; Wed, 19 Oct 2016 23:36:43 +0000 (UTC) (envelope-from glebius@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 0C68F140 for ; Wed, 19 Oct 2016 23:36:43 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0BBC0C19511; Wed, 19 Oct 2016 23:36:43 +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 0B65DC19510 for ; Wed, 19 Oct 2016 23:36:43 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (glebi.us [96.95.210.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EA9D213F; Wed, 19 Oct 2016 23:36:42 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id u9JNafkK031554 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 19 Oct 2016 16:36:41 -0700 (PDT) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id u9JNaeog031553; Wed, 19 Oct 2016 16:36:40 -0700 (PDT) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 19 Oct 2016 16:36:40 -0700 From: Gleb Smirnoff To: Mike Karels , George Neville-Neil Cc: net@FreeBSD.org Subject: Re: TCP route caching panic Message-ID: <20161019233640.GN27748@FreeBSD.org> References: <20161019212914.GJ27748@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161019212914.GJ27748@FreeBSD.org> User-Agent: Mutt/1.7.0 (2016-08-17) 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, 19 Oct 2016 23:36:43 -0000 On Wed, Oct 19, 2016 at 02:29:14PM -0700, Gleb Smirnoff wrote: T> Hi! T> T> I got this panic in a bhyve VM, which was just compiling stuff T> and had two ssh sessions open. It has static network configuration, T> one interfaces, one IP address, IPv4 only and it sees only hardware T> address of the host. So it is minimal possible configuration. It T> runs with INVARIANTS. Important note that kernel has FLOWTABLE option. And recently I refined the original fix of FLOWTABLE+inpcb_route_cache. This might be related, but I don't see how. The inp code explicitly nulls the ro_lle when it frees it. -- Totus tuus, Glebius. From owner-freebsd-net@freebsd.org Thu Oct 20 00:27: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 2A6FFC183D6 for ; Thu, 20 Oct 2016 00:27:42 +0000 (UTC) (envelope-from mike@karels.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 1BADCC8F for ; Thu, 20 Oct 2016 00:27:42 +0000 (UTC) (envelope-from mike@karels.net) Received: by mailman.ysv.freebsd.org (Postfix) id 17FA8C183D5; Thu, 20 Oct 2016 00:27:42 +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 17962C183D4 for ; Thu, 20 Oct 2016 00:27:42 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail.karels.net (mail.karels.net [63.231.190.5]) by mx1.freebsd.org (Postfix) with ESMTP id 96729C8E; Thu, 20 Oct 2016 00:27:40 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail.karels.net (localhost [127.0.0.1]) by mail.karels.net (8.15.2/8.15.2) with ESMTP id u9K0Qibx017899; Wed, 19 Oct 2016 19:26:45 -0500 (CDT) (envelope-from mike@karels.net) Message-Id: <201610200026.u9K0Qibx017899@mail.karels.net> To: Gleb Smirnoff cc: George Neville-Neil , net@FreeBSD.org From: Mike Karels Reply-to: mike@karels.net Subject: Re: TCP route caching panic In-reply-to: Your message of Wed, 19 Oct 2016 16:36:40 -0700. <20161019233640.GN27748@FreeBSD.org> Date: Wed, 19 Oct 2016 19:26:44 -0500 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, 20 Oct 2016 00:27:42 -0000 > On Wed, Oct 19, 2016 at 02:29:14PM -0700, Gleb Smirnoff wrote: > T> Hi! > T> > T> I got this panic in a bhyve VM, which was just compiling stuff > T> and had two ssh sessions open. It has static network configuration, > T> one interfaces, one IP address, IPv4 only and it sees only hardware > T> address of the host. So it is minimal possible configuration. It > T> runs with INVARIANTS. > Important note that kernel has FLOWTABLE option. And recently I refined > the original fix of FLOWTABLE+inpcb_route_cache. This might be related, > but I don't see how. The inp code explicitly nulls the ro_lle when > it frees it. Hmm, I run a similar configuration, but may not run as many compiles. I'm running a recent head GENERIC system, so has INVARIANTS. I've tested with FLOWTABLE in the past; I'll try it again now. But if I understand correctly, you have modifications? Could we see them (assuming they are not in the tree, I haven't been watching closely)? Mike From owner-freebsd-net@freebsd.org Thu Oct 20 02:21:09 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 901AFC19BCF for ; Thu, 20 Oct 2016 02:21:09 +0000 (UTC) (envelope-from glebius@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 7B995995 for ; Thu, 20 Oct 2016 02:21:09 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7AF40C19BCE; Thu, 20 Oct 2016 02:21:09 +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 7A9D8C19BCD for ; Thu, 20 Oct 2016 02:21:09 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (glebi.us [96.95.210.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 633CD994; Thu, 20 Oct 2016 02:21:08 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id u9K2L7pH032472 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 19 Oct 2016 19:21:07 -0700 (PDT) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id u9K2L7n2032471; Wed, 19 Oct 2016 19:21:07 -0700 (PDT) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 19 Oct 2016 19:21:07 -0700 From: Gleb Smirnoff To: Mike Karels Cc: George Neville-Neil , net@FreeBSD.org Subject: Re: TCP route caching panic Message-ID: <20161020022107.GO27748@FreeBSD.org> References: <20161019233640.GN27748@FreeBSD.org> <201610200026.u9K0Qibx017899@mail.karels.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201610200026.u9K0Qibx017899@mail.karels.net> User-Agent: Mutt/1.7.0 (2016-08-17) 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, 20 Oct 2016 02:21:09 -0000 On Wed, Oct 19, 2016 at 07:26:44PM -0500, Mike Karels wrote: M> > On Wed, Oct 19, 2016 at 02:29:14PM -0700, Gleb Smirnoff wrote: M> > T> Hi! M> > T> M> > T> I got this panic in a bhyve VM, which was just compiling stuff M> > T> and had two ssh sessions open. It has static network configuration, M> > T> one interfaces, one IP address, IPv4 only and it sees only hardware M> > T> address of the host. So it is minimal possible configuration. It M> > T> runs with INVARIANTS. M> M> > Important note that kernel has FLOWTABLE option. And recently I refined M> > the original fix of FLOWTABLE+inpcb_route_cache. This might be related, M> > but I don't see how. The inp code explicitly nulls the ro_lle when M> > it frees it. M> M> Hmm, I run a similar configuration, but may not run as many compiles. M> I'm running a recent head GENERIC system, so has INVARIANTS. I've M> tested with FLOWTABLE in the past; I'll try it again now. M> M> But if I understand correctly, you have modifications? Could we see M> them (assuming they are not in the tree, I haven't been watching closely)? No, I don't have modifications. -- Totus tuus, Glebius. From owner-freebsd-net@freebsd.org Thu Oct 20 03:34: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 D09A8C185AF for ; Thu, 20 Oct 2016 03:34: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 BFB251F2D for ; Thu, 20 Oct 2016 03:34: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 u9K3Y1X6051807 for ; Thu, 20 Oct 2016 03:34:03 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 186114] net/mpd5 hangs after a certain number of users connect Date: Thu, 20 Oct 2016 03:34:01 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: eri@freebsd.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: keywords bug_file_loc 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, 20 Oct 2016 03:34:03 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |crash URL| |https://lists.freebsd.org/p | |ipermail/freebsd-net/2016-O | |ctober/046279.html CC| |freebsd-net@FreeBSD.org --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 20 04:23:39 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 59C3EC19459 for ; Thu, 20 Oct 2016 04:23:39 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2F10A9C1 for ; Thu, 20 Oct 2016 04:23:39 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 2E670C19458; Thu, 20 Oct 2016 04:23:39 +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 2DF6BC19457 for ; Thu, 20 Oct 2016 04:23:39 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pf0-x22b.google.com (mail-pf0-x22b.google.com [IPv6:2607:f8b0:400e:c00::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 F363B9C0 for ; Thu, 20 Oct 2016 04:23:38 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pf0-x22b.google.com with SMTP id 128so28216828pfz.0 for ; Wed, 19 Oct 2016 21:23:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:reply-to:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=HHH2nSivanSbX5nBR19eoEX9+u2JKzQueCM4/5XirEg=; b=EuTvVTO7FtgZkfbSHFQ/HNojDy+z4sSnx2BU8v9D2+cV1niLcGGXrA3doHhL5XzMtC 8x6bskqaX1XnRfEkQIwBoTKsAL5eA3tivA0uMaw+WbhYVqbV74P+12QpuwXR6jYRZvdK BNYRcXYGjzFapfjtQ4DxYLg4UJTzpGbTemQrWGPbn4ke4D4Jt7hNvFJRub3eToHjGQr/ qGHmOdqhAkR1nHivzFs0TS4c6oplfGnRADjyKTFb5kzfYY1X1JHtY+qY5P8WZLUtlyNa O4iRm9rRker6jGxqb8U0IZEp1oN/O6SO0jDuHOSu/DPG4SmrI2tZxRSPjg7atmgn/jID 2fgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:reply-to:subject:to:cc:references:from :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=HHH2nSivanSbX5nBR19eoEX9+u2JKzQueCM4/5XirEg=; b=e1Igjn4mp3MHvtLVHLkrewOOvGXUe5Jrw8+SsXNpgcTgqpmtT/Oj1qTjyK3JZZjeFu rcxow4BqQf8pdWln6GYdP3SiX449o4J6STp9QGEu3fXGnpInDpheBTNZdG40sC+u7VY2 GURHgWOAroOIIIE8VNPDOHmTb+f8VMmaRdZFVTDgviI9sou+0QLmIFRbW30OJOa9werD ByA6tZspWvIqZmw71M5rK/Gs6tQgtVSUQImHlTCX4tumi1DE2yfEBn1KNlV65ISZThOV g2+MtqetnhZMPVh607Wk73DJJMQSuJURysk0CgoshiCqFFLgL18oa+IE0GZ09XXliUyW /HjA== X-Gm-Message-State: AA6/9RkBg6hS2IT8SKAPpct/lxqyTi01N35fmAwUY/3R5I36/a4YeUouCGx+nuYbokem3Q== X-Received: by 10.98.75.152 with SMTP id d24mr17315570pfj.97.1476937418162; Wed, 19 Oct 2016 21:23:38 -0700 (PDT) Received: from ?IPv6:2001:44b8:31ae:7b01:1c1a:5103:265d:bfaf? (2001-44b8-31ae-7b01-1c1a-5103-265d-bfaf.static.ipv6.internode.on.net. [2001:44b8:31ae:7b01:1c1a:5103:265d:bfaf]) by smtp.gmail.com with ESMTPSA id c127sm4736904pfc.28.2016.10.19.21.23.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Oct 2016 21:23:37 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. To: Cassiano Peixoto , Donald Baud Cc: "net@freebsd.org" 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: Kubilay Kocak Message-ID: <16994026-ae44-4a39-822b-c4a218a71ce7@FreeBSD.org> Date: Thu, 20 Oct 2016 15:22:31 +1100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Thunderbird/51.0a2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-AU 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: Thu, 20 Oct 2016 04:23:39 -0000 On 19/10/2016 3:23 AM, Cassiano Peixoto wrote: > Hi guys, > > I have some update about this issue. After my last email i had 3 crashes. > Two of them had the same message on kernel debug: > > (kgdb) list *0xffffffff8228c918 > 0xffffffff8228c918 is in trim_map_seg_compare > (/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/trim_map.c:108). > 103 trim_map_seg_compare(const void *x1, const void *x2) > 104 { > 105 const trim_seg_t *s1 = x1; > 106 const trim_seg_t *s2 = x2; > 107 > 108 if (s1->ts_start < s2->ts_start) { > 109 if (s1->ts_end > s2->ts_start) > 110 return (0); > 111 return (-1); > 112 } > Current language: auto; currently minimal > (kgdb) bt > #0 doadump (textdump=) at pcpu.h:221 > #1 0xffffffff80ad8e69 in kern_reboot (howto=260) at > /usr/src/sys/kern/kern_shutdown.c:366 > #2 0xffffffff80ad941b in vpanic (fmt=, ap= optimized out>) at /usr/src/sys/kern/kern_shutdown.c:759 > #3 0xffffffff80ad9253 in panic (fmt=0x0) at > /usr/src/sys/kern/kern_shutdown.c:690 > #4 0xffffffff80fa0d31 in trap_fatal (frame=0xfffffe02374957f0, > eva=4294967343) at /usr/src/sys/amd64/amd64/trap.c:841 > #5 0xffffffff80fa0f23 in trap_pfault (frame=0xfffffe02374957f0, > usermode=0) at /usr/src/sys/amd64/amd64/trap.c:691 > #6 0xffffffff80fa04cc in trap (frame=0xfffffe02374957f0) at > /usr/src/sys/amd64/amd64/trap.c:442 > #7 0xffffffff80f84141 in calltrap () at > /usr/src/sys/amd64/amd64/exception.S:236 > #8 0xffffffff8228c918 in trim_map_seg_compare (x1=0xfffffe0237495920, > x2=0x100000007) at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/trim_map.c:108 > #9 0xffffffff821a98e1 in avl_find (tree=, > value=, where=0x0) at > /usr/src/sys/cddl/contrib/opensolaris/common/avl/avl.c:268 > #10 0xffffffff8228ce9e in trim_map_write_start (zio=) > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/trim_map.c:363 > #11 0xffffffff822592df in zio_vdev_io_start (zio=0xfffff802191ea000) at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:2866 > #12 0xffffffff82255b26 in zio_execute (zio=) at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1556 > #13 0xffffffff822551e9 in zio_nowait (zio=0xfffff802191ea000) at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1610 > #14 0xffffffff8223c738 in vdev_queue_io_done (zio=) at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:884 > #15 0xffffffff822594a9 in zio_vdev_io_done (zio=0xfffff8006daad000) at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:2895 > #16 0xffffffff82255b26 in zio_execute (zio=) at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1556 > #17 0xffffffff80b363ca in taskqueue_run_locked (queue= out>) at /usr/src/sys/kern/subr_taskqueue.c:449 > #18 0xffffffff80b372d8 in taskqueue_thread_loop (arg=) > at /usr/src/sys/kern/subr_taskqueue.c:703 > #19 0xffffffff80a90055 in fork_exit (callout=0xffffffff80b371f0 > , arg=0xfffff8001006b920, frame=0xfffffe0237495c00) > at /usr/src/sys/kern/kern_fork.c:1038 > #20 0xffffffff80f8467e in fork_trampoline () at > /usr/src/sys/amd64/amd64/exception.S:611 > #21 0x0000000000000000 in ?? () > (kgdb) up 8 > #8 0xffffffff8228c918 in trim_map_seg_compare (x1=0xfffffe0237495920, > x2=0x100000007) at > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/trim_map.c:108 > 108 if (s1->ts_start < s2->ts_start) { > > But my last crash had a different message: > > (kgdb) list *0xffffffff80b3a89c > 0xffffffff80b3a89c is in turnstile_broadcast > (/usr/src/sys/kern/subr_turnstile.c:837). > 832 > 833 /* > 834 * Transfer the blocked list to the pending list. > 835 */ > 836 mtx_lock_spin(&td_contested_lock); > 837 TAILQ_CONCAT(&ts->ts_pending, &ts->ts_blocked[queue], td_lockq); > 838 mtx_unlock_spin(&td_contested_lock); > 839 > 840 /* > 841 * Give a turnstile to each thread. The last thread gets > Current language: auto; currently minimal > (kgdb) bt > #0 doadump (textdump=) at pcpu.h:221 > #1 0xffffffff80ad8e69 in kern_reboot (howto=260) at > /usr/src/sys/kern/kern_shutdown.c:366 > #2 0xffffffff80ad941b in vpanic (fmt=, ap= optimized out>) at /usr/src/sys/kern/kern_shutdown.c:759 > #3 0xffffffff80ad9253 in panic (fmt=0x0) at > /usr/src/sys/kern/kern_shutdown.c:690 > #4 0xffffffff80fa0d31 in trap_fatal (frame=0xfffffe0237384870, eva=48) at > /usr/src/sys/amd64/amd64/trap.c:841 > #5 0xffffffff80fa0f23 in trap_pfault (frame=0xfffffe0237384870, > usermode=0) at /usr/src/sys/amd64/amd64/trap.c:691 > #6 0xffffffff80fa04cc in trap (frame=0xfffffe0237384870) at > /usr/src/sys/amd64/amd64/trap.c:442 > #7 0xffffffff80f84141 in calltrap () at > /usr/src/sys/amd64/amd64/exception.S:236 > #8 0xffffffff80b3a89c in turnstile_broadcast (ts=0x0, queue=1) at > /usr/src/sys/kern/subr_turnstile.c:837 > #9 0xffffffff80ad48cf in __rw_wunlock_hard (c=0xfffff8024f3c2960, > tid=, file=, line= optimized out>) > at /usr/src/sys/kern/kern_rwlock.c:1027 > #10 0xffffffff80e1a75c in vm_map_delete (map=, > start=, end=) at > /usr/src/sys/vm/vm_map.c:2960 > #11 0xffffffff80e1828e in vmspace_exit (td=) at > /usr/src/sys/vm/vm_map.c:3077 > #12 0xffffffff80a88686 in exit1 (td=0xfffff80015533a00, rval=268849920, > signo=0) at /usr/src/sys/kern/kern_exit.c:398 > #13 0xffffffff80a87e1d in sys_sys_exit (td=0x0, uap=) > at /usr/src/sys/kern/kern_exit.c:178 > #14 0xffffffff80fa168e in amd64_syscall (td=, > traced=0) at subr_syscall.c:135 > #15 0xffffffff80f8442b in Xfast_syscall () at > /usr/src/sys/amd64/amd64/exception.S:396 > #16 0x0000000800b661aa in ?? () > Previous frame inner to this frame (corrupt stack?) > (kgdb) up 8 > #8 0xffffffff80b3a89c in turnstile_broadcast (ts=0x0, queue=1) at > /usr/src/sys/kern/subr_turnstile.c:837 > 837 TAILQ_CONCAT(&ts->ts_pending, &ts->ts_blocked[queue], td_lockq); > > As you can see we are dealing with random crashes. I feel i'm not moving > forward here. it's not a hardware problem because i have 3 different > servers with same issue. > > Donald, did you have a chance to try 11-RELEASE? Any other behavior? > > Anyone have some idea that could help? > > Thanks. > > > On Thu, Oct 13, 2016 at 12:24 PM, Cassiano Peixoto < > peixotocassiano@gmail.com> wrote: > >> Hi guys, >> >> First of all, thanks to share your thoughts about this issue. I think it’s >> 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’ve tested recently on FreeBSD 10.3 and FreeBSD-11-RC3. I’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’ll apply Donald recommendation and let you guys know. >> >> Let’s 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 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 < >>>> 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 =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 >>>> >>> ?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" > For anyone experiencing these mpd hangs/crashes, if you believe your issue is the same as that described in Issue 186114 [1], please add your comments there including full system version information and crash backtraces (*as attachments*) if experiencing panics. Resolution of this problem is contingent on a clear test/reproduction cases (ideally as reduced as possible). [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186114 ./koobs From owner-freebsd-net@freebsd.org Thu Oct 20 05:32: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 6DF49C18A45 for ; Thu, 20 Oct 2016 05:32:19 +0000 (UTC) (envelope-from mike@karels.net) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5F970814 for ; Thu, 20 Oct 2016 05:32:19 +0000 (UTC) (envelope-from mike@karels.net) Received: by mailman.ysv.freebsd.org (Postfix) id 5F01DC18A44; Thu, 20 Oct 2016 05:32: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 5EAB2C18A43 for ; Thu, 20 Oct 2016 05:32:19 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail.karels.net (mail.karels.net [63.231.190.5]) by mx1.freebsd.org (Postfix) with ESMTP id F319D80E; Thu, 20 Oct 2016 05:32:18 +0000 (UTC) (envelope-from mike@karels.net) Received: from mail.karels.net (localhost [127.0.0.1]) by mail.karels.net (8.15.2/8.15.2) with ESMTP id u9K5WHH8018605; Thu, 20 Oct 2016 00:32:17 -0500 (CDT) (envelope-from mike@karels.net) Message-Id: <201610200532.u9K5WHH8018605@mail.karels.net> To: Gleb Smirnoff cc: George Neville-Neil , net@FreeBSD.org From: Mike Karels Reply-to: mike@karels.net Subject: Re: TCP route caching panic In-reply-to: Your message of Wed, 19 Oct 2016 19:21:07 -0700. <20161020022107.GO27748@FreeBSD.org> Date: Thu, 20 Oct 2016 00:32:17 -0500 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, 20 Oct 2016 05:32:19 -0000 > On Wed, Oct 19, 2016 at 07:26:44PM -0500, Mike Karels wrote: > M> > On Wed, Oct 19, 2016 at 02:29:14PM -0700, Gleb Smirnoff wrote: > M> > T> Hi! > M> > T> > M> > T> I got this panic in a bhyve VM, which was just compiling stuff > M> > T> and had two ssh sessions open. It has static network configuration, > M> > T> one interfaces, one IP address, IPv4 only and it sees only hardware > M> > T> address of the host. So it is minimal possible configuration. It > M> > T> runs with INVARIANTS. > M> > M> > Important note that kernel has FLOWTABLE option. And recently I refined > M> > the original fix of FLOWTABLE+inpcb_route_cache. This might be related, > M> > but I don't see how. The inp code explicitly nulls the ro_lle when > M> > it frees it. > M> > M> Hmm, I run a similar configuration, but may not run as many compiles. > M> I'm running a recent head GENERIC system, so has INVARIANTS. I've > M> tested with FLOWTABLE in the past; I'll try it again now. > M> > M> But if I understand correctly, you have modifications? Could we see > M> them (assuming they are not in the tree, I haven't been watching closely)? > No, I don't have modifications. Sorry then, what did you mean by this: And recently I refined the original fix of FLOWTABLE+inpcb_route_cache. This might be related, I've run one buildworld in s aimilar environment so far today, using NFS to the host for the sources. I'll try another. Mike From owner-freebsd-net@freebsd.org Thu Oct 20 05:42: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 BF39EC18E13 for ; Thu, 20 Oct 2016 05:42:41 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id AB011C2A for ; Thu, 20 Oct 2016 05:42:41 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id AA6F2C18E12; Thu, 20 Oct 2016 05:42: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 AA212C18E11 for ; Thu, 20 Oct 2016 05:42:41 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (glebi.us [96.95.210.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cell.glebi.us", Issuer "cell.glebi.us" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 948EEC29; Thu, 20 Oct 2016 05:42:41 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.glebi.us (localhost [127.0.0.1]) by cell.glebi.us (8.15.2/8.15.2) with ESMTPS id u9K5gelY034219 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 19 Oct 2016 22:42:40 -0700 (PDT) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.glebi.us (8.15.2/8.15.2/Submit) id u9K5gdWx034218; Wed, 19 Oct 2016 22:42:39 -0700 (PDT) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.glebi.us: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 19 Oct 2016 22:42:39 -0700 From: Gleb Smirnoff To: Mike Karels Cc: George Neville-Neil , net@FreeBSD.org Subject: Re: TCP route caching panic Message-ID: <20161020054239.GP27748@FreeBSD.org> References: <20161020022107.GO27748@FreeBSD.org> <201610200532.u9K5WHH8018605@mail.karels.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201610200532.u9K5WHH8018605@mail.karels.net> User-Agent: Mutt/1.7.0 (2016-08-17) 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, 20 Oct 2016 05:42:41 -0000 On Thu, Oct 20, 2016 at 12:32:17AM -0500, Mike Karels wrote: M> > On Wed, Oct 19, 2016 at 07:26:44PM -0500, Mike Karels wrote: M> > M> > On Wed, Oct 19, 2016 at 02:29:14PM -0700, Gleb Smirnoff wrote: M> > M> > T> Hi! M> > M> > T> M> > M> > T> I got this panic in a bhyve VM, which was just compiling stuff M> > M> > T> and had two ssh sessions open. It has static network configuration, M> > M> > T> one interfaces, one IP address, IPv4 only and it sees only hardware M> > M> > T> address of the host. So it is minimal possible configuration. It M> > M> > T> runs with INVARIANTS. M> > M> M> > M> > Important note that kernel has FLOWTABLE option. And recently I refined M> > M> > the original fix of FLOWTABLE+inpcb_route_cache. This might be related, M> > M> > but I don't see how. The inp code explicitly nulls the ro_lle when M> > M> > it frees it. M> > M> M> > M> Hmm, I run a similar configuration, but may not run as many compiles. M> > M> I'm running a recent head GENERIC system, so has INVARIANTS. I've M> > M> tested with FLOWTABLE in the past; I'll try it again now. M> > M> M> > M> But if I understand correctly, you have modifications? Could we see M> > M> them (assuming they are not in the tree, I haven't been watching closely)? M> M> > No, I don't have modifications. M> M> Sorry then, what did you mean by this: M> M> And recently I refined the original fix of FLOWTABLE+inpcb_route_cache. M> This might be related, That is already checked in as r307234. M> I've run one buildworld in s aimilar environment so far today, using NFS M> to the host for the sources. I'll try another. I also failed to reproduce for the last several hours. Will keep you updated, since I use the VM daily. -- Totus tuus, Glebius. From owner-freebsd-net@freebsd.org Thu Oct 20 06:50: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 7BE68C1A83A for ; Thu, 20 Oct 2016 06:50:57 +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 6B519387 for ; Thu, 20 Oct 2016 06:50:57 +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 u9K6orPp092945 for ; Thu, 20 Oct 2016 06:50:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 186114] net/mpd5 hangs after a certain number of users connect Date: Thu, 20 Oct 2016 06:50:53 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: eri@freebsd.org X-Bugzilla-Flags: maintainer-feedback? 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, 20 Oct 2016 06:50:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114 --- Comment #17 from Kubilay Kocak --- (In reply to Eugene Grosbein from comment #14) The initial report is fine to be classified against the port. Once the root cause(s) is confirmed, implicated or identified, a dependent (Depends On) s= ub task can be created for the base change. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 20 08:20:24 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 C8BFEC1A63F for ; Thu, 20 Oct 2016 08:20:24 +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 AD9F38B for ; Thu, 20 Oct 2016 08:20:24 +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 u9K8KOJP086696 for ; Thu, 20 Oct 2016 08:20:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213606] LACP not working with qlogic BCM57800 Date: Thu, 20 Oct 2016 08:20: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: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: borjam@sarenet.es 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: 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, 20 Oct 2016 08:20:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213606 Borja Marcos changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |borjam@sarenet.es --- Comment #8 from Borja Marcos --- Deja vu with https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D150249 The main symptom was lagg refusing to work in LACP mode.=20 In this case, the reason was that the driver didn't detect media properly, = and the "paperwork" with the kernel failed: the interface wasn't marked as full duplex. As a result, LACP (which checks the full-duplex flag for the interf= ace) refused to use it. Remember that full-duplex is a prerequisite for LACP. This seems to be a case of incomplete paperwork as well, although the neces= sary bits seem to be in place. In my case this was the problem with LACP (ieee8023ad_lacp.c): --------- /* * If the port is not an active full duplex Ethernet link then it c= an * not be aggregated. */ if (IFM_TYPE(media) !=3D IFM_ETHER || (media & IFM_FDX) =3D=3D 0 || ifp->if_link_state !=3D LINK_STATE_UP) { lacp_port_disable(lp); } else { lacp_port_enable(lp); } --------- But according to ifconfig the interface is marked as full duplex and media seems to be Ethernet. I would add some printf's here to check if this is re= ally the case and some other check is failing. What does ifconfig -m say of the interfaces? But that lack of options looks like a driver bug. And it would help to see its capabilities as reported by ifconfig. This is an example with an "em" interface. --------- % ifconfig -m -v -v em0 em0: flags=3D8943 metric 0 = mtu 1500 =20=20=20=20=20=20=20 options=3D4219b =20=20=20=20=20=20=20 capabilities=3D15399b ether 68:05:ca:XX:YY:ZZ inet 192.168.1.202 netmask 0xffffff00 broadcast 192.168.1.255=20 inet 192.168.1.203 netmask 0xffffffff broadcast 192.168.1.203=20 nd6 options=3D23 media: Ethernet autoselect (1000baseT ) status: active supported media: media autoselect media 1000baseT media 1000baseT mediaopt full-duplex media 100baseTX mediaopt full-duplex media 100baseTX media 10baseT/UTP mediaopt full-duplex media 10baseT/UTP --------- --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 20 13:20:37 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 55E8AC194D8 for ; Thu, 20 Oct 2016 13:20:37 +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 45CCB34A for ; Thu, 20 Oct 2016 13:20:37 +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 u9KDKbEC044024 for ; Thu, 20 Oct 2016 13:20:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213606] LACP not working with qlogic BCM57800 Date: Thu, 20 Oct 2016 13:20:37 +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 Only Me X-Bugzilla-Who: eentsalu@gmail.com 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, 20 Oct 2016 13:20:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213606 --- Comment #9 from Kristjan --- ifconfig -m bxe0 bxe0: flags=3D8843 metric 0 mtu 1500 =20=20=20=20=20=20=20 capabilities=3D527bb ether b0:83:fe:e5:fa:82 nd6 options=3D29 media: Ethernet autoselect (10Gbase-SR ) status: active supported media: media autoselect media 10Gbase-SR mediaopt full-duplex --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 20 13:30:37 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 F3EE9C196BA for ; Thu, 20 Oct 2016 13:30:36 +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 E39FEA0E for ; Thu, 20 Oct 2016 13:30:36 +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 u9KDUaha068305 for ; Thu, 20 Oct 2016 13:30:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213606] LACP not working with qlogic BCM57800 Date: Thu, 20 Oct 2016 13:30:37 +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 Only Me X-Bugzilla-Who: borjam@sarenet.es 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, 20 Oct 2016 13:30:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213606 --- Comment #10 from Borja Marcos --- And what if you try to mess with the options?=20 Try this: ifconfig bxe0 -rxcsum ifconfig bxe1 -rxcsum I'm just wondering, maybe by doing that you can coerce the driver to comple= te the paperwork properly. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 20 14:15: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 E878BC1A72D for ; Thu, 20 Oct 2016 14:15: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 D823D989 for ; Thu, 20 Oct 2016 14:15: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 u9KEFOpF006099 for ; Thu, 20 Oct 2016 14:15:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 208343] [em] wake on lan not working with Intel I219 V2 Date: Thu, 20 Oct 2016 14:15:25 +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: IntelNetworking X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: wblock@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: 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, 20 Oct 2016 14:15:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208343 Warren Block changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wblock@FreeBSD.org --- Comment #7 from Warren Block --- Seeing the same symptoms with I217-LM (class=3D0x020000 card=3D0x153a15d9 chip=3D0x153a8086 rev=3D0x05 hdr=3D0x00) and I210 (card=3D0x153315d9 chip= =3D0x15338086 rev=3D0x03 hdr=3D0x00) interfaces on Supermicro X10SLL-F boards. The WOL capabilities do not appear in the list, and the system does not wake.=20 Supermicro support says that WOL is enabled on these boards. There are no = WOL options in the UEFI settings. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 20 19:05: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 CBCAAC1A4BC for ; Thu, 20 Oct 2016 19:05:52 +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 A55061FE7 for ; Thu, 20 Oct 2016 19:05:52 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id A497CC1A4BB; Thu, 20 Oct 2016 19:05: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 A40B4C1A4BA for ; Thu, 20 Oct 2016 19:05:52 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::236]) (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 520BF1FE6; Thu, 20 Oct 2016 19:05:52 +0000 (UTC) (envelope-from peixotocassiano@gmail.com) Received: by mail-qk0-x236.google.com with SMTP id z190so112279413qkc.2; Thu, 20 Oct 2016 12:05:52 -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=zDN0sOXjU7QUaAuBFbGebgo3z2xGR+U5l501CNx9F8M=; b=h7wR7vgyok6UCaTuLw8wUnWfIV9fvXf78mqRUEZvTYaicv9z6qUTU5eXbzi8IRz8Iq lQVjFSw7RvQKEwWVB6OhKeHPSPZDezkk9rRzFWzvwGDCJF+a8VNj0R+D14MMEjjCPS0s sFvHjM0zxrOzswRFYoALX5Bi7uxAYdll6HzHbA4rGxMZVrBTDHGuaV9A9qzej32/NU47 rq/04YH2Izz6UTexT7hA8s9QooNhHSXxoi68Xat5XfApC3W5pOWJ9CbR8z52GDl/deF8 juuz0YTM5wL/YVhWoyMscx6o15hLnCvxonuJeSPRBHKqOaLtFrOGqGwjYTOXMJeIH9Ce QoNw== 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=zDN0sOXjU7QUaAuBFbGebgo3z2xGR+U5l501CNx9F8M=; b=c0Jh0uQ6j6LEJM/ytgtenT8WZQKJ8Lmva01slu1C3Y3bf/PVfKaVtW6XKBC2ELj5D2 zA/05+bavgiqrHrfWsEfljYYwZXHtCH0C6zOi9edgKXtoz9jcAPLAP6EZYMVeY6xE97g 2jV1yH4MSpZrlX3eH1fLYEC4P+HnC32q85FFIBsgrcJe8gEauau3Pf/4UO4Hwa5oN6A7 Pgs8LIL36HjN46zsJqCw+oczpnVAv6U66N8y3a6aWtJvVrezEaj/kczMJlSC36CN1DNc 9r164NwcGZFaijR5nUJSKca52zDLYOVySL7wlZmZyhzbDP0OpdWR2i70uWw/ZadcV0AG U9KA== X-Gm-Message-State: ABUngvcLsObZqP/Kg5z7WW0IBKLWT8m0DdgNmYZyAL6wDoFaHXpUlPx7uY8xCS1Xbud5adU37UhwnV6jOsaEmA== X-Received: by 10.55.73.21 with SMTP id w21mr1797829qka.13.1476990351282; Thu, 20 Oct 2016 12:05:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.166.26 with HTTP; Thu, 20 Oct 2016 12:05:50 -0700 (PDT) In-Reply-To: <16994026-ae44-4a39-822b-c4a218a71ce7@FreeBSD.org> 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> <16994026-ae44-4a39-822b-c4a218a71ce7@FreeBSD.org> From: Cassiano Peixoto Date: Thu, 20 Oct 2016 17:05:50 -0200 Message-ID: Subject: Re: FreeBSD10.3-RELEASE. Kernel panic. To: koobs@freebsd.org Cc: Donald Baud , "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, 20 Oct 2016 19:05:52 -0000 Hi Kubilay, Yes, i think all issues are related with this one. I already attached many info about these crashes there, but looks like nobody cares about it. This PR is assigned to Ermal, but he's not working on it because his last PR change was in January. If you or someone else is interested to help to fix it, please take this PR. I can provide any information that you need. Thanks. On Thu, Oct 20, 2016 at 2:22 AM, Kubilay Kocak wrote: > On 19/10/2016 3:23 AM, Cassiano Peixoto wrote: > > Hi guys, > > > > I have some update about this issue. After my last email i had 3 crashe= s. > > Two of them had the same message on kernel debug: > > > > (kgdb) list *0xffffffff8228c918 > > 0xffffffff8228c918 is in trim_map_seg_compare > > (/usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/ > trim_map.c:108). > > 103 trim_map_seg_compare(const void *x1, const void *x2) > > 104 { > > 105 const trim_seg_t *s1 =3D x1; > > 106 const trim_seg_t *s2 =3D x2; > > 107 > > 108 if (s1->ts_start < s2->ts_start) { > > 109 if (s1->ts_end > s2->ts_start) > > 110 return (0); > > 111 return (-1); > > 112 } > > Current language: auto; currently minimal > > (kgdb) bt > > #0 doadump (textdump=3D) at pcpu.h:221 > > #1 0xffffffff80ad8e69 in kern_reboot (howto=3D260) at > > /usr/src/sys/kern/kern_shutdown.c:366 > > #2 0xffffffff80ad941b in vpanic (fmt=3D, ap=3D > optimized out>) at /usr/src/sys/kern/kern_shutdown.c:759 > > #3 0xffffffff80ad9253 in panic (fmt=3D0x0) at > > /usr/src/sys/kern/kern_shutdown.c:690 > > #4 0xffffffff80fa0d31 in trap_fatal (frame=3D0xfffffe02374957f0, > > eva=3D4294967343) at /usr/src/sys/amd64/amd64/trap.c:841 > > #5 0xffffffff80fa0f23 in trap_pfault (frame=3D0xfffffe02374957f0, > > usermode=3D0) at /usr/src/sys/amd64/amd64/trap.c:691 > > #6 0xffffffff80fa04cc in trap (frame=3D0xfffffe02374957f0) at > > /usr/src/sys/amd64/amd64/trap.c:442 > > #7 0xffffffff80f84141 in calltrap () at > > /usr/src/sys/amd64/amd64/exception.S:236 > > #8 0xffffffff8228c918 in trim_map_seg_compare (x1=3D0xfffffe0237495920= , > > x2=3D0x100000007) at > > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/trim_map.c:108 > > #9 0xffffffff821a98e1 in avl_find (tree=3D, > > value=3D, where=3D0x0) at > > /usr/src/sys/cddl/contrib/opensolaris/common/avl/avl.c:268 > > #10 0xffffffff8228ce9e in trim_map_write_start (zio=3D out>) > > at /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/ > trim_map.c:363 > > #11 0xffffffff822592df in zio_vdev_io_start (zio=3D0xfffff802191ea000) = at > > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:2866 > > #12 0xffffffff82255b26 in zio_execute (zio=3D) at > > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1556 > > #13 0xffffffff822551e9 in zio_nowait (zio=3D0xfffff802191ea000) at > > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1610 > > #14 0xffffffff8223c738 in vdev_queue_io_done (zio=3D) > at > > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/vdev_queue.c:88= 4 > > #15 0xffffffff822594a9 in zio_vdev_io_done (zio=3D0xfffff8006daad000) a= t > > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:2895 > > #16 0xffffffff82255b26 in zio_execute (zio=3D) at > > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zio.c:1556 > > #17 0xffffffff80b363ca in taskqueue_run_locked (queue=3D > out>) at /usr/src/sys/kern/subr_taskqueue.c:449 > > #18 0xffffffff80b372d8 in taskqueue_thread_loop (arg=3D out>) > > at /usr/src/sys/kern/subr_taskqueue.c:703 > > #19 0xffffffff80a90055 in fork_exit (callout=3D0xffffffff80b371f0 > > , arg=3D0xfffff8001006b920, > frame=3D0xfffffe0237495c00) > > at /usr/src/sys/kern/kern_fork.c:1038 > > #20 0xffffffff80f8467e in fork_trampoline () at > > /usr/src/sys/amd64/amd64/exception.S:611 > > #21 0x0000000000000000 in ?? () > > (kgdb) up 8 > > #8 0xffffffff8228c918 in trim_map_seg_compare (x1=3D0xfffffe0237495920= , > > x2=3D0x100000007) at > > /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/trim_map.c:108 > > 108 if (s1->ts_start < s2->ts_start) { > > > > But my last crash had a different message: > > > > (kgdb) list *0xffffffff80b3a89c > > 0xffffffff80b3a89c is in turnstile_broadcast > > (/usr/src/sys/kern/subr_turnstile.c:837). > > 832 > > 833 /* > > 834 * Transfer the blocked list to the pending list. > > 835 */ > > 836 mtx_lock_spin(&td_contested_lock); > > 837 TAILQ_CONCAT(&ts->ts_pending, &ts->ts_blocked[queue], > td_lockq); > > 838 mtx_unlock_spin(&td_contested_lock); > > 839 > > 840 /* > > 841 * Give a turnstile to each thread. The last thread gets > > Current language: auto; currently minimal > > (kgdb) bt > > #0 doadump (textdump=3D) at pcpu.h:221 > > #1 0xffffffff80ad8e69 in kern_reboot (howto=3D260) at > > /usr/src/sys/kern/kern_shutdown.c:366 > > #2 0xffffffff80ad941b in vpanic (fmt=3D, ap=3D > optimized out>) at /usr/src/sys/kern/kern_shutdown.c:759 > > #3 0xffffffff80ad9253 in panic (fmt=3D0x0) at > > /usr/src/sys/kern/kern_shutdown.c:690 > > #4 0xffffffff80fa0d31 in trap_fatal (frame=3D0xfffffe0237384870, eva= =3D48) > at > > /usr/src/sys/amd64/amd64/trap.c:841 > > #5 0xffffffff80fa0f23 in trap_pfault (frame=3D0xfffffe0237384870, > > usermode=3D0) at /usr/src/sys/amd64/amd64/trap.c:691 > > #6 0xffffffff80fa04cc in trap (frame=3D0xfffffe0237384870) at > > /usr/src/sys/amd64/amd64/trap.c:442 > > #7 0xffffffff80f84141 in calltrap () at > > /usr/src/sys/amd64/amd64/exception.S:236 > > #8 0xffffffff80b3a89c in turnstile_broadcast (ts=3D0x0, queue=3D1) at > > /usr/src/sys/kern/subr_turnstile.c:837 > > #9 0xffffffff80ad48cf in __rw_wunlock_hard (c=3D0xfffff8024f3c2960, > > tid=3D, file=3D, line=3D > optimized out>) > > at /usr/src/sys/kern/kern_rwlock.c:1027 > > #10 0xffffffff80e1a75c in vm_map_delete (map=3D, > > start=3D, end=3D) at > > /usr/src/sys/vm/vm_map.c:2960 > > #11 0xffffffff80e1828e in vmspace_exit (td=3D) at > > /usr/src/sys/vm/vm_map.c:3077 > > #12 0xffffffff80a88686 in exit1 (td=3D0xfffff80015533a00, rval=3D268849= 920, > > signo=3D0) at /usr/src/sys/kern/kern_exit.c:398 > > #13 0xffffffff80a87e1d in sys_sys_exit (td=3D0x0, uap=3D out>) > > at /usr/src/sys/kern/kern_exit.c:178 > > #14 0xffffffff80fa168e in amd64_syscall (td=3D, > > traced=3D0) at subr_syscall.c:135 > > #15 0xffffffff80f8442b in Xfast_syscall () at > > /usr/src/sys/amd64/amd64/exception.S:396 > > #16 0x0000000800b661aa in ?? () > > Previous frame inner to this frame (corrupt stack?) > > (kgdb) up 8 > > #8 0xffffffff80b3a89c in turnstile_broadcast (ts=3D0x0, queue=3D1) at > > /usr/src/sys/kern/subr_turnstile.c:837 > > 837 TAILQ_CONCAT(&ts->ts_pending, &ts->ts_blocked[queue], > td_lockq); > > > > As you can see we are dealing with random crashes. I feel i'm not movin= g > > forward here. it's not a hardware problem because i have 3 different > > servers with same issue. > > > > Donald, did you have a chance to try 11-RELEASE? Any other behavior? > > > > Anyone have some idea that could help? > > > > Thanks. > > > > > > On Thu, Oct 13, 2016 at 12:24 PM, Cassiano Peixoto < > > peixotocassiano@gmail.com> wrote: > > > >> 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=99ve 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 th= is > >> 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 crashe= s > >> before happened every day. > >> > >> If it crashs again i=E2=80=99ll apply Donald recommendation and let yo= u guys > 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 wil= l > 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 valu= es > >>> 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 the= ir > >>> 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 starte= d > >>> 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 T= CP > >>>> 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 following recipes and the server has been up for 30 > >>>> days so far: > >>>> > >>>> Normally I should expermient more to see which one of th= e > >>>> 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, thi= s > >>>> 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 val= id > >>>> 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 cras= h > >>>> 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=3D1861= 14 > >>>> > > >>>> > >>>> 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 day= s. > >>>> 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 FreeB= SD > >>>> 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 traff= ic > >>>> 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" > > > > For anyone experiencing these mpd hangs/crashes, if you believe your > issue is the same as that described in Issue 186114 [1], please add your > comments there including full system version information and crash > backtraces (*as attachments*) if experiencing panics. > > Resolution of this problem is contingent on a clear test/reproduction > cases (ideally as reduced as possible). > > [1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114 > > ./koobs > From owner-freebsd-net@freebsd.org Thu Oct 20 19:19:27 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 51125C1AA3F for ; Thu, 20 Oct 2016 19:19:27 +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 34437A68 for ; Thu, 20 Oct 2016 19:19:27 +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 u9KJJPkt063029 for ; Thu, 20 Oct 2016 19:19:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 186114] net/mpd5 hangs after a certain number of users connect Date: Thu, 20 Oct 2016 19:19:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: peixoto.cassiano@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: eri@freebsd.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc attachments.created 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, 20 Oct 2016 19:19:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114 Cassiano Peixoto changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peixoto.cassiano@gmail.com --- Comment #18 from Cassiano Peixoto --- Created attachment 175989 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D175989&action= =3Dedit crash-bt --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 20 19:20:31 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 C128CC1AAD1 for ; Thu, 20 Oct 2016 19:20:31 +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 AFFD7B4F for ; Thu, 20 Oct 2016 19:20:31 +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 u9KJKUU9064467 for ; Thu, 20 Oct 2016 19:20:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 186114] net/mpd5 hangs after a certain number of users connect Date: Thu, 20 Oct 2016 19:20:30 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: peixoto.cassiano@gmail.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: eri@freebsd.org X-Bugzilla-Flags: maintainer-feedback? 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, 20 Oct 2016 19:20:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D186114 --- Comment #19 from Cassiano Peixoto --- Comment on attachment 175989 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D175989 crash-bt I'm having random crashes. BT attached. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-net@freebsd.org Thu Oct 20 20:43:29 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 CCED8C1B98B for ; Thu, 20 Oct 2016 20:43:29 +0000 (UTC) (envelope-from david@aogsquid.ucsd.edu) Received: from fed1rmfepo202.cox.net (fed1rmfepo202.cox.net [68.230.241.147]) by mx1.freebsd.org (Postfix) with ESMTP id AB1A7FB4 for ; Thu, 20 Oct 2016 20:43:29 +0000 (UTC) (envelope-from david@aogsquid.ucsd.edu) Received: from fed1rmimpo110.cox.net ([68.230.241.159]) by fed1rmfepo202.cox.net (InterMail vM.8.01.05.28 201-2260-151-171-20160122) with ESMTP id <20161020204323.HJCA3827.fed1rmfepo202.cox.net@fed1rmimpo110.cox.net> for ; Thu, 20 Oct 2016 16:43:23 -0400 Received: from [192.168.25.200] ([174.65.112.147]) by fed1rmimpo110.cox.net with cox id xwjN1t0093ArtDJ01wjNAM; Thu, 20 Oct 2016 16:43:23 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A090205.58092C6B.002F, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.1 cv=SdJXDqlu c=1 sm=1 tr=0 a=kEcOQgfb31AP6aoOu6fJYg==:117 a=kEcOQgfb31AP6aoOu6fJYg==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=N659UExz7-8A:10 a=KL6-4wenZDBwHSelpQgA:9 a=pILNOxqGKmIA:10 X-CM-Score: 0.00 Authentication-Results: cox.net; auth=pass (PLAIN) smtp.auth=dhorwitt@cox.net Subject: Re: Adding RTL8153 support to rue(4) USB to Ethernet driver To: freebsd-net@freebsd.org References: <5807B630.1060806@aogsquid.ucsd.edu> <3622755d-b0cd-60bf-0f81-469d06e65595@selasky.org> From: David Horwitt Message-ID: <58092C6D.8080105@aogsquid.ucsd.edu> Date: Thu, 20 Oct 2016 13:43:25 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <3622755d-b0cd-60bf-0f81-469d06e65595@selasky.org> Content-Type: text/plain; charset=windows-1252 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: Thu, 20 Oct 2016 20:43:29 -0000 On 10/19/16 11:25, Hans Petter Selasky wrote: > > Hi, > > Search the idVendor and idProduct values in the Linux kernel. I think you need to implement some propritary miibus to > get it working. CDC ethernet does not define any miibus. > > --HPS > Thank you for the quick response. Do you mean that I need to implement a small driver at VID:PID (0bda:8153 for this device) using cfg 0 to initialize the built-in MII (using the Linux RTL8152/8153 driver as a model), and then switch to cfg 1 to use the CDC device for actual operation? Thanks, DH From owner-freebsd-net@freebsd.org Fri Oct 21 07:13: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 BE9CDC1A027 for ; Fri, 21 Oct 2016 07:13:19 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 8652F8F4 for ; Fri, 21 Oct 2016 07:13:19 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 409671FE022; Fri, 21 Oct 2016 09:13:11 +0200 (CEST) Subject: Re: Adding RTL8153 support to rue(4) USB to Ethernet driver To: David Horwitt , freebsd-net@freebsd.org References: <5807B630.1060806@aogsquid.ucsd.edu> <3622755d-b0cd-60bf-0f81-469d06e65595@selasky.org> <58092C6D.8080105@aogsquid.ucsd.edu> From: Hans Petter Selasky Message-ID: <30de3b9c-98c4-0bbc-dce2-eddc52e98b10@selasky.org> Date: Fri, 21 Oct 2016 09:18:11 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <58092C6D.8080105@aogsquid.ucsd.edu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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, 21 Oct 2016 07:13:19 -0000 On 10/20/16 22:43, David Horwitt wrote: > On 10/19/16 11:25, Hans Petter Selasky wrote: >> >> Hi, >> >> Search the idVendor and idProduct values in the Linux kernel. I think you need to implement some propritary miibus to >> get it working. CDC ethernet does not define any miibus. >> >> --HPS >> > Thank you for the quick response. > > Do you mean that I need to implement a small driver at VID:PID (0bda:8153 for this device) using cfg 0 to initialize the > built-in MII (using the Linux RTL8152/8153 driver as a model), and then switch to cfg 1 to use the CDC device for actual > operation? > No, I think the cfg 1 with CDC has the additional interface. Look at what the Linux driver does or get another ethernet adapter :-) --HPS From owner-freebsd-net@freebsd.org Fri Oct 21 10:22:27 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 6EA24C1AF85 for ; Fri, 21 Oct 2016 10:22:27 +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 5DCCEBFA for ; Fri, 21 Oct 2016 10:22:27 +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 u9LAMR9K067364 for ; Fri, 21 Oct 2016 10:22:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 183407] [rc.d] [patch] Routing restart returns non-zero exitcode in case of no extra routing parameter or missing atm/ipx Date: Fri, 21 Oct 2016 10:22:27 +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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pi@FreeBSD.org 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: 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, 21 Oct 2016 10:22:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D183407 --- Comment #3 from Kurt Jaeger --- problem can still be reproduced. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 21 10:24: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 5795EC1B034 for ; Fri, 21 Oct 2016 10:24: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 469ECCFB for ; Fri, 21 Oct 2016 10:24: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 u9LAOZH9070643 for ; Fri, 21 Oct 2016 10:24:35 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 183407] [rc.d] [patch] Routing restart returns non-zero exitcode in case of no extra routing parameter or missing atm/ipx Date: Fri, 21 Oct 2016 10:24:35 +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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pi@FreeBSD.org 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: 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, 21 Oct 2016 10:24:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D183407 --- Comment #4 from Kurt Jaeger --- the patch fails, needs to be updated: Hunk #1 failed at 21. Hunk #2 failed at 50. Hunk #3 succeeded at 67 (offset 2 lines). Hunk #4 failed at 86. Hunk #5 succeeded at 325 (offset 9 lines). Hunk #6 succeeded at 329 (offset 2 lines). Hunk #7 succeeded at 345 (offset 9 lines). Hunk #8 succeeded at 347 (offset 2 lines). Hunk #9 succeeded at 363 (offset 9 lines). Hunk #10 succeeded at 365 (offset 2 lines). Hunk #11 succeeded at 381 (offset 9 lines). Hunk #12 succeeded at 382 (offset 2 lines). Hunk #13 failed at 399. Hunk #14 succeeded at 409 with fuzz 1 (offset -13 lines). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 21 11:45: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 1C3C3C1BDC4 for ; Fri, 21 Oct 2016 11:45:05 +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 0B56FF78 for ; Fri, 21 Oct 2016 11:45:05 +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 u9LBj4wv087087 for ; Fri, 21 Oct 2016 11:45:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 183407] [rc.d] [patch] Routing restart returns non-zero exitcode in case of no extra routing parameter or missing atm/ipx Date: Fri, 21 Oct 2016 11:45:05 +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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: abhikumar163@gmail.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: 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, 21 Oct 2016 11:45:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D183407 --- Comment #5 from abhikumar163@gmail.com --- this patch was submitted 2years back, somethings must have changed... I'll update and re-submit can I update this patch request itself, please guide --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 21 11:50:24 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 5B43AC1BF61 for ; Fri, 21 Oct 2016 11:50:24 +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 4A5E514A for ; Fri, 21 Oct 2016 11:50:24 +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 u9LBoOZc097886 for ; Fri, 21 Oct 2016 11:50:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 183407] [rc.d] [patch] Routing restart returns non-zero exitcode in case of no extra routing parameter or missing atm/ipx Date: Fri, 21 Oct 2016 11:50:24 +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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pi@FreeBSD.org 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: 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, 21 Oct 2016 11:50:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D183407 --- Comment #6 from Kurt Jaeger --- Yes, you can submit a new patch, using the 'add an attachment' link in bugzilla, and mark the old patch obsolete. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 21 11:50:44 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 97CF0C1BFAD for ; Fri, 21 Oct 2016 11:50:44 +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 86D4A216 for ; Fri, 21 Oct 2016 11:50: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 u9LBoi7d098632 for ; Fri, 21 Oct 2016 11:50:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 183407] [rc.d] [patch] Routing restart returns non-zero exitcode in case of no extra routing parameter or missing atm/ipx Date: Fri, 21 Oct 2016 11:50:44 +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: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: pi@FreeBSD.org 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: 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, 21 Oct 2016 11:50:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D183407 --- Comment #7 from Kurt Jaeger --- Btw, ipx was removed, so that's basically the cause of the patch to fail. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-net@freebsd.org Fri Oct 21 13:32: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 B4486C1B9CF for ; Fri, 21 Oct 2016 13:32: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 A401481 for ; Fri, 21 Oct 2016 13:32: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 u9LDWeIS041807 for ; Fri, 21 Oct 2016 13:32:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213673] VNET + PF: enabling a firewall in a jail leaks memory Date: Fri, 21 Oct 2016 13:32: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: X-Bugzilla-Severity: Affects Some 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: short_desc 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: Fri, 21 Oct 2016 13:32:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213673 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|VNET + PF |VNET + PF: enabling a | |firewall in a jail leaks | |memory 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 Fri Oct 21 15:43: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 B6A1BC1B9D1 for ; Fri, 21 Oct 2016 15:43:57 +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 A5FD46D0 for ; Fri, 21 Oct 2016 15:43:57 +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 u9LFhvBQ009802 for ; Fri, 21 Oct 2016 15:43:57 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213673] VNET + PF: enabling a firewall in a jail leaks memory Date: Fri, 21 Oct 2016 15:43:57 +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: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: alexandre.borrut@aquilenet.fr 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, 21 Oct 2016 15:43:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213673 --- Comment #1 from Sacha --- This problem is with PF out of the jail. --=20 You are receiving this mail because: You are the assignee for the bug.=