Date: Thu, 1 Oct 2015 18:57:57 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Eric Joyner <ricera10@gmail.com> Cc: Sean Bruno <sbruno@freebsd.org>, "Pieper, Jeffrey E" <jeffrey.e.pieper@intel.com>, Hans Petter Selasky <hps@selasky.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: CURRENT: net/igb broken Message-ID: <20151001185757.03aef51e.ohartman@zedat.fu-berlin.de> In-Reply-To: <CA%2Bb0zg-A9sXtm3H07=W4O15eudj9t_qH3L8qR4YkTPDdKO78_Q@mail.gmail.com> References: <20150915125618.0f752596@freyja.zeit4.iv.bundesimmobilien.de> <55F7FCB5.5090809@selasky.org> <2A35EA60C3C77D438915767F458D65688077F87B@ORSMSX111.amr.corp.intel.com> <20150917133509.6c87f5b6@freyja.zeit4.iv.bundesimmobilien.de> <20150917133712.0ffd01ee@freyja.zeit4.iv.bundesimmobilien.de> <55FC40CB.7090504@freebsd.org> <CA%2Bb0zg_GzedJ%2BSv4p_R%2Bra6KqJauMNn1MKTuxhc6tfWHszfzvQ@mail.gmail.com> <55FDA830.7030307@freebsd.org> <20150921105848.386d6ae0@freyja.zeit4.iv.bundesimmobilien.de> <CA%2Bb0zg-EijHbX8doBecx92e7YKdGCZUv0cqMENrzGY5WYOEAJQ@mail.gmail.com> <20150922082323.6f861448@freyja.zeit4.iv.bundesimmobilien.de> <5601B591.6000005@freebsd.org> <CA%2Bb0zg-A9sXtm3H07=W4O15eudj9t_qH3L8qR4YkTPDdKO78_Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/Wrj/nXPNLM7QaPWmxb/ekyk Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Thu, 01 Oct 2015 15:39:11 +0000 Eric Joyner <ricera10@gmail.com> schrieb: > Oliver, >=20 > did you try Sean's suggestion? >=20 > - Eric Hello Eric, no, sorry, not yet. Today was the first day with the igb-equipted servers a= nd tomorrow (Friday) I will start to check whether Sean's suggestion helps or not. In the short time I fiddled arounf with the server, I brought up and down i= n a series the igb0|1 interfaces and pinged the system (with most recent CURRENT as of ~ 1= 5:00 CEST (UTC +2). And while doing that, this flapping the UP and DOWN state made th= e interfaces work for a couple of seconds - but it was hardly to reproduce with a define= d set of UP and DOWNs. I will report. Oliver >=20 > On Tue, Sep 22, 2015 at 1:10 PM Sean Bruno <sbruno@freebsd.org> wrote: >=20 > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA512 > > > > > > > > On 09/21/15 23:23, O. Hartmann wrote: > > > On Mon, 21 Sep 2015 21:13:18 +0000 Eric Joyner <ricera10@gmail.com> > > > wrote: > > > > > >> If you do a diff between r288057 and r287761, there are no > > >> differences between the sys/dev/e1000, sys/modules/em, and > > >> sys/modules/igb directories. Are you sure r287761 actually > > >> works? > > > > > > I'm quite sure r287761 works (and r287762 doesn't), double checked > > > this this morning again. I also checked r288093 and it is still not > > > working. > > > > > > The ensure that I'm not the culprit and stupid here: > > > > > > I use a NanoBSD environment and the only thing that gets exchanged, > > > is the underlying OS/OS revision. The configuration always stays > > > the same. The base system for all of my tests is built from a clean > > > source - (deleted obj/ dir, clean, fresh build into obj/ for every > > > test I ran). > > > > > > I realised a funny thing. Playing around with enabling/disabling > > > TSO (I have been told that could be the culprit in an earlier Email > > > from this list) with the commend sequence: > > > > > > ifconfig igb1 down ifconfig igb1 -tso ifconfig igb1 up ifconfig > > > igb1 down ifconfig igb1 tso ifconfig igb1 up . . . > > > > > > while a ping is pinging in the background a remote host connected > > > to that specific interface, the ping does work for a while and dies > > > then after a round trip of roughly 10 - 20. I can reproduce this. > > > > > > is that observation of any help? > > > > > > Regards, > > > > > > oh > > > > > >> > > >> On Mon, Sep 21, 2015 at 1:58 AM O. Hartmann > > >> <ohartman@zedat.fu-berlin.de> wrote: > > >> > > >>> On Sat, 19 Sep 2015 11:23:44 -0700 Sean Bruno > > >>> <sbruno@freebsd.org> wrote: > > >>> > > > > > > > > > On 09/18/15 10:20, Eric Joyner wrote: > > >>>>>> He has an i210 -- he would want to revert > > >>>>>> e1000_i210.[ch], too. > > >>>>>> > > >>>>>> Sorry for the thrash Sean -- it sounds like it would be a > > >>>>>> good idea for you should revert this patch, and Jeff and > > >>>>>> I can go look at trying these shared code updates and igb > > >>>>>> changes internally again. We at Intel really could've > > >>>>>> done a better job of making sure these changes worked > > >>>>>> across a wider variety of devices. > > >>>>>> > > >>>>>> - Eric > > > > > > I've reverted the changes to head. I'll reopen the reviews and we > > > can proceed from there. > > > > > > sean > > > > > > > > >>>>>> > > >>>>>> On Fri, Sep 18, 2015 at 9:50 AM Sean Bruno > > >>>>>> <sbruno@freebsd.org <mailto:sbruno@freebsd.org>> wrote: > > >>>>>> > > >>>>>> > > >>>>>>> > > >>>>>>> r287762 broke the system > > >>>>>> > > >>>>>> > > >>>>>> Before I revert this changeset *again* can you test > > >>>>>> revert r287762 from if_igb.c, e1000_82575.c and > > >>>>>> e1000_82575.h *only* > > >>>>>> > > >>>>>> That narrows down the change quite a bit. > > >>>>>> > > >>>>>> sean _______________________________________________ > > >>>>>> freebsd-current@freebsd.org > > >>>>>> <mailto:freebsd-current@freebsd.org> mailing list > > >>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > > >>>>>> To unsubscribe, send any mail to > > >>>>>> "freebsd-current-unsubscribe@freebsd.org > > >>>>>> <mailto:freebsd-current-unsubscribe@freebsd.org>" > > >>>>>> > > >>> > > >>> I'm now on r288057 on that specific machine, supposedly > > >>> reverted changes that seemingly has been identified as the > > >>> culprit. Still NO change in behaviour! > > >>> > > >>> r287761 works with the same configuration on igb (i210), any > > >>> further does not. Not ping/connect from the outside, no > > >>> ping/connect from the inside. Tried different protocols (SAMBA, > > >>> ssh, LDAP, DNS). Affected is/are only boxes with the igb driver > > >>> and i210 chipset (we do not have other chips covered by igb). > > >>> > > >>> Regards, Oliver > > >>> > > >> _______________________________________________ > > >> freebsd-current@freebsd.org mailing list > > >> https://lists.freebsd.org/mailman/listinfo/freebsd-current To > > >> unsubscribe, send any mail to > > >> "freebsd-current-unsubscribe@freebsd.org" > > > > > > > > > > > > For my entertainment (and HPS's), can you run HEAD and revert r287775? > > > > sean > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v2 > > > > iQF8BAEBCgBmBQJWAbWOXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w > > ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx > > MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kPTAH/jmm1tudLRYVtC+xb9NXHQgr > > dl8/fZC8/xL3m0EVM8pWdKlRbF1tHUDSB/2ftYUBEe6SIkab2IZx2Z/0VgdflrbB > > 05HQUuq1yM3dYBiEAjyM0oK6lfeWu2Jg8nOaA5YWi1GO2OfkuDfXRUkK3sm7xa0C > > PE+ZMlfofQCV0RyDu2ew17yZKYRbCXdc+GYg6CGNRRVJHeITZPyAAh8X1d7pC8G3 > > 8vJLKC8JOmg0i5yToYSkKvXdrReHUpzF+hZKgxsl5Lb4BhcHEukkSWQVsJ9IuVGU > > 615sN6eVub2+OBbxJyV+CcjUVwdLJba/YBUXhWdKslDrN2z9l/sAFHCxDJlmAvc=3D > > =3DzdDL > > -----END PGP SIGNATURE----- > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" > > --Sig_/Wrj/nXPNLM7QaPWmxb/ekyk Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWDWYVAAoJEOgBcD7A/5N8VkEH/j4Ssfu+oQ7KnyOdMyPUuK89 jbRcGSyYgGzlm1Hrh32ZNqArCFRjfnwSIF5Zn+I+dgSqav5tnWo81yTnnmiaeTWY ttENPY7qmCwQNc0Xq6wtAG1YVqLH9ZC1aNkvEcRMuvs79HgNfRanOGcNL0tx/zg4 griMk9KSkUzo9vZwA+DZ7hUdqHla2d0M7KfQxtTKhgH/3xZJYYXwXvPe9tHW8xIg IlzzGyjswmKSvnfU6C6NlKtDnYD+ugMdsik7Efh4T+AFjTouU8epnXSiudQnr6BM GA6g3+Ffc8+xJr3aEFsYB48ekWxKVkC960CNgvQje1vCViD7AwhY/Dqi6tqkGik= =99dN -----END PGP SIGNATURE----- --Sig_/Wrj/nXPNLM7QaPWmxb/ekyk--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151001185757.03aef51e.ohartman>