Re: CURRENT: net/igb broken

2016-01-09 Thread O. Hartmann
Am Fri, 08 Jan 2016 20:08:39 +
Eric Joyner  schrieb:

> Does your i210 now work with the reverted version of igb? I didn't get a
> chance to follow up on this earlier.
> 
> Also, can you give us the device ID for the device? There are a couple
> versions of the i210 hardware.
> 
> - Eric

Not yet, since the box is in the lab and I have access to it earliest on Monday 
- but of
course, I will provide the informations as soon I have access.

oh

> 
> On Sun, Oct 4, 2015 at 10:23 PM O. Hartmann 
> wrote:
> 
> > On Fri, 2 Oct 2015 08:52:57 -0700
> > Sean Bruno  wrote:
> >  
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA512
> > >
> > >
> > >
> > > On 10/02/15 00:47, O. Hartmann wrote:  
> > > > On Thu, 01 Oct 2015 15:39:11 + Eric Joyner 
> > > > wrote:
> > > >  
> > > >> Oliver,
> > > >>
> > > >> did you try Sean's suggestion?
> > > >>
> > > >> - Eric
> > > >>
> > > >> On Tue, Sep 22, 2015 at 1:10 PM Sean Bruno 
> > > >> wrote:
> > > >>  
> > > >
> > > >
> > > > On 09/21/15 23:23, O. Hartmann wrote:  
> > > > On Mon, 21 Sep 2015 21:13:18 + Eric Joyner
> > > >  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
> > > >>  wrote:
> > > >>  
> > > >>> On Sat, 19 Sep 2015 11:23:44 -0700 Sean Bruno
> > > >>>  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
> > > >> >
> > > >> 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  
> >
> > [...]
> >  
> > > >>>  
> > > >>  
> > > 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
> 

Re: CURRENT: net/igb broken

2016-01-08 Thread Eric Joyner
Does your i210 now work with the reverted version of igb? I didn't get a
chance to follow up on this earlier.

Also, can you give us the device ID for the device? There are a couple
versions of the i210 hardware.

- Eric

On Sun, Oct 4, 2015 at 10:23 PM O. Hartmann 
wrote:

> On Fri, 2 Oct 2015 08:52:57 -0700
> Sean Bruno  wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> >
> >
> > On 10/02/15 00:47, O. Hartmann wrote:
> > > On Thu, 01 Oct 2015 15:39:11 + Eric Joyner 
> > > wrote:
> > >
> > >> Oliver,
> > >>
> > >> did you try Sean's suggestion?
> > >>
> > >> - Eric
> > >>
> > >> On Tue, Sep 22, 2015 at 1:10 PM Sean Bruno 
> > >> wrote:
> > >>
> > >
> > >
> > > On 09/21/15 23:23, O. Hartmann wrote:
> > > On Mon, 21 Sep 2015 21:13:18 + Eric Joyner
> > >  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
> > >>  wrote:
> > >>
> > >>> On Sat, 19 Sep 2015 11:23:44 -0700 Sean Bruno
> > >>>  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
> > >> >
> > >> 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
>
> [...]
>
> > >>>
> > >>
> > 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
>
> [...]
>
> > >
> > > For my entertainment (and HPS's), can you run HEAD and revert
> > > r287775?
> > >
> > > sean
>
> [...]
>
> > > I did as suggested:
> > >
> > > checking out the most recent HEAD of CURRENT this morning, which
> > > is/was for me 

Re: CURRENT: net/igb broken

2015-10-04 Thread O. Hartmann
On Fri, 2 Oct 2015 08:52:57 -0700
Sean Bruno  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> 
> 
> On 10/02/15 00:47, O. Hartmann wrote:
> > On Thu, 01 Oct 2015 15:39:11 + Eric Joyner 
> > wrote:
> > 
> >> Oliver,
> >> 
> >> did you try Sean's suggestion?
> >> 
> >> - Eric
> >> 
> >> On Tue, Sep 22, 2015 at 1:10 PM Sean Bruno 
> >> wrote:
> >> 
> > 
> > 
> > On 09/21/15 23:23, O. Hartmann wrote:
> > On Mon, 21 Sep 2015 21:13:18 + Eric Joyner
> >  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 
> >>  wrote:
> >> 
> >>> On Sat, 19 Sep 2015 11:23:44 -0700 Sean Bruno 
> >>>  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 
> >> >
> >> 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

[...]

> >>>
> >> 
> 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

[...]
 
> > 
> > For my entertainment (and HPS's), can you run HEAD and revert
> > r287775?
> > 
> > sean

[...]
 
> > I did as suggested:
> > 
> > checking out the most recent HEAD of CURRENT this morning, which
> > is/was for me r288474. I applied then "svn merge -c -287775 .",
> > which reverted(?) only r287775, which is something with
> > tcp_output.c or so. I did not remember.
> > 
> 
> Thanks.  This is what I intended.
> 
> 
> > I recompiled a fresh world (cleaning up /usr/obj completely by
> > deleting the folder) and try running the target system with the
> > created image.
> > 
> > Result: the same as >r287761, it doesn't work. I reverted back to
> > r287761, which works for me on the specific target hardware
> > (Fujitsu Primergy RX 1330 

Re: CURRENT: net/igb broken

2015-10-02 Thread Sean Bruno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512



On 10/02/15 00:47, O. Hartmann wrote:
> On Thu, 01 Oct 2015 15:39:11 + Eric Joyner 
> wrote:
> 
>> Oliver,
>> 
>> did you try Sean's suggestion?
>> 
>> - Eric
>> 
>> On Tue, Sep 22, 2015 at 1:10 PM Sean Bruno 
>> wrote:
>> 
> 
> 
> On 09/21/15 23:23, O. Hartmann wrote:
> On Mon, 21 Sep 2015 21:13:18 + Eric Joyner
>  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 
>>  wrote:
>> 
>>> On Sat, 19 Sep 2015 11:23:44 -0700 Sean Bruno 
>>>  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 
>> >
>> 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 
>>  mailing
>> list 
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>
>> 
To unsubscribe, send any mail to
>> "freebsd-current-unsubscr...@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-unsubscr...@freebsd.org"
> 
> 
> 
> 
> For my entertainment (and HPS's), can you run HEAD and revert
> r287775?
> 
> sean
>>> ___ 
>>> freebsd-current@freebsd.org mailing list 
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current To
>>> unsubscribe, send any mail to
>>> "freebsd-current-unsubscr...@freebsd.org"
>>> 
>> 

Re: CURRENT: net/igb broken

2015-10-02 Thread O. Hartmann
On Thu, 01 Oct 2015 15:39:11 +
Eric Joyner  wrote:

> Oliver,
> 
> did you try Sean's suggestion?
> 
> - Eric
> 
> On Tue, Sep 22, 2015 at 1:10 PM Sean Bruno  wrote:
> 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> >
> >
> > On 09/21/15 23:23, O. Hartmann wrote:
> > > On Mon, 21 Sep 2015 21:13:18 + Eric Joyner 
> > > 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
> > >>  wrote:
> > >>
> > >>> On Sat, 19 Sep 2015 11:23:44 -0700 Sean Bruno
> > >>>  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
> > >> > 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
> > >>  mailing list
> > >> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > >> To unsubscribe, send any mail to
> > >> "freebsd-current-unsubscr...@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-unsubscr...@freebsd.org"
> > >
> > >
> >
> >
> > For my entertainment (and HPS's), can you run HEAD and revert r287775?
> >
> > sean
> > -BEGIN PGP SIGNATURE-
> > Version: GnuPG v2
> >
> > iQF8BAEBCgBmBQJWAbWOXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> > ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx
> > MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kPTAH/jmm1tudLRYVtC+xb9NXHQgr
> > dl8/fZC8/xL3m0EVM8pWdKlRbF1tHUDSB/2ftYUBEe6SIkab2IZx2Z/0VgdflrbB
> > 05HQUuq1yM3dYBiEAjyM0oK6lfeWu2Jg8nOaA5YWi1GO2OfkuDfXRUkK3sm7xa0C
> > 

Re: CURRENT: net/igb broken

2015-10-01 Thread Eric Joyner
Oliver,

did you try Sean's suggestion?

- Eric

On Tue, Sep 22, 2015 at 1:10 PM Sean Bruno  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
>
>
> On 09/21/15 23:23, O. Hartmann wrote:
> > On Mon, 21 Sep 2015 21:13:18 + Eric Joyner 
> > 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
> >>  wrote:
> >>
> >>> On Sat, 19 Sep 2015 11:23:44 -0700 Sean Bruno
> >>>  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
> >> > 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
> >>  mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >> To unsubscribe, send any mail to
> >> "freebsd-current-unsubscr...@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-unsubscr...@freebsd.org"
> >
> >
>
>
> For my entertainment (and HPS's), can you run HEAD and revert r287775?
>
> sean
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQF8BAEBCgBmBQJWAbWOXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx
> MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kPTAH/jmm1tudLRYVtC+xb9NXHQgr
> dl8/fZC8/xL3m0EVM8pWdKlRbF1tHUDSB/2ftYUBEe6SIkab2IZx2Z/0VgdflrbB
> 05HQUuq1yM3dYBiEAjyM0oK6lfeWu2Jg8nOaA5YWi1GO2OfkuDfXRUkK3sm7xa0C
> PE+ZMlfofQCV0RyDu2ew17yZKYRbCXdc+GYg6CGNRRVJHeITZPyAAh8X1d7pC8G3
> 8vJLKC8JOmg0i5yToYSkKvXdrReHUpzF+hZKgxsl5Lb4BhcHEukkSWQVsJ9IuVGU
> 615sN6eVub2+OBbxJyV+CcjUVwdLJba/YBUXhWdKslDrN2z9l/sAFHCxDJlmAvc=
> =zdDL
> -END PGP SIGNATURE-
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To 

Re: CURRENT: net/igb broken

2015-10-01 Thread O. Hartmann
Am Thu, 01 Oct 2015 15:39:11 +
Eric Joyner  schrieb:

> Oliver,
> 
> did you try Sean's suggestion?
> 
> - Eric

Hello Eric,

no, sorry, not yet. Today was the first day with the igb-equipted servers and 
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 in a 
series the
igb0|1 interfaces and pinged the system (with most recent CURRENT as of ~ 15:00 
CEST
(UTC +2). And while doing that, this flapping the UP and DOWN state made the 
interfaces
work for a couple of seconds - but it was hardly to reproduce with a defined 
set of UP
and DOWNs.

I will report.

Oliver
> 
> On Tue, Sep 22, 2015 at 1:10 PM Sean Bruno  wrote:
> 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> >
> >
> > On 09/21/15 23:23, O. Hartmann wrote:
> > > On Mon, 21 Sep 2015 21:13:18 + Eric Joyner 
> > > 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
> > >>  wrote:
> > >>
> > >>> On Sat, 19 Sep 2015 11:23:44 -0700 Sean Bruno
> > >>>  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
> > >> > 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
> > >>  mailing list
> > >> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > >> To unsubscribe, send any mail to
> > >> "freebsd-current-unsubscr...@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-unsubscr...@freebsd.org"
> > >
> 

Re: CURRENT: net/igb broken

2015-09-22 Thread O. Hartmann
On Mon, 21 Sep 2015 21:13:18 +
Eric Joyner  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 
> wrote:
> 
> > On Sat, 19 Sep 2015 11:23:44 -0700
> > Sean Bruno  wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA512
> > >
> > >
> > >
> > > 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  > > > > 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 
> > > > mailing list
> > > > https://lists.freebsd.org/mailman/listinfo/freebsd-current To
> > > > unsubscribe, send any mail to
> > > > "freebsd-current-unsubscr...@freebsd.org
> > > > "
> > > >
> > > -BEGIN PGP SIGNATURE-
> > > Version: GnuPG v2
> > >
> > > iQF8BAEBCgBmBQJV/agsXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> > > ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx
> > > MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kkkMH/icGgcIAdm3CIxtXtnhbE5E9
> > > N6RrBrgJruoRHP2geJ9UOUGp7MaFwS6AHcwCC7FvxoydzcsT+iMj3Kreu+aEkT4C
> > > PZvLsqIvLeX0WVEXSC8jwBAZbrOwJ+4TcMMnW2KZMeUPUHAd8rP0+Skj9AeQ4feJ
> > > OfLqv52VdxYTnx+vYbvZSaOgWp8sC+PcoJxiJua7hpmqXwISbcG9eXxQHUil0fcv
> > > tqfb2dv89VN12brFuQbFtgEK2RG6gKtbj7IQkeQqzt0g5WL6UnJ5OslajcEJwIA4
> > > H6H4eke5CQUugVTUv5cbCwmQDfAF2qF8JgsxuuQDPvQRb4+XH1ks/5SEhENItv0=
> > > =JTMu
> > > -END PGP SIGNATURE-
> >
> > 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-unsubscr...@freebsd.org"

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: CURRENT: net/igb broken

2015-09-22 Thread Sean Bruno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512



On 09/21/15 23:23, O. Hartmann wrote:
> On Mon, 21 Sep 2015 21:13:18 + Eric Joyner 
> 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
>>  wrote:
>> 
>>> On Sat, 19 Sep 2015 11:23:44 -0700 Sean Bruno
>>>  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
>> > 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
>>  mailing list 
>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to 
>> "freebsd-current-unsubscr...@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-unsubscr...@freebsd.org"
> 
> 


For my entertainment (and HPS's), can you run HEAD and revert r287775?

sean
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQF8BAEBCgBmBQJWAbWOXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx
MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kPTAH/jmm1tudLRYVtC+xb9NXHQgr
dl8/fZC8/xL3m0EVM8pWdKlRbF1tHUDSB/2ftYUBEe6SIkab2IZx2Z/0VgdflrbB
05HQUuq1yM3dYBiEAjyM0oK6lfeWu2Jg8nOaA5YWi1GO2OfkuDfXRUkK3sm7xa0C
PE+ZMlfofQCV0RyDu2ew17yZKYRbCXdc+GYg6CGNRRVJHeITZPyAAh8X1d7pC8G3
8vJLKC8JOmg0i5yToYSkKvXdrReHUpzF+hZKgxsl5Lb4BhcHEukkSWQVsJ9IuVGU
615sN6eVub2+OBbxJyV+CcjUVwdLJba/YBUXhWdKslDrN2z9l/sAFHCxDJlmAvc=
=zdDL
-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-unsubscr...@freebsd.org"


Re: CURRENT: net/igb broken

2015-09-21 Thread Eric Joyner
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?

On Mon, Sep 21, 2015 at 1:58 AM O. Hartmann 
wrote:

> On Sat, 19 Sep 2015 11:23:44 -0700
> Sean Bruno  wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> >
> >
> > 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  > > > 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 
> > > mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-current To
> > > unsubscribe, send any mail to
> > > "freebsd-current-unsubscr...@freebsd.org
> > > "
> > >
> > -BEGIN PGP SIGNATURE-
> > Version: GnuPG v2
> >
> > iQF8BAEBCgBmBQJV/agsXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> > ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx
> > MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kkkMH/icGgcIAdm3CIxtXtnhbE5E9
> > N6RrBrgJruoRHP2geJ9UOUGp7MaFwS6AHcwCC7FvxoydzcsT+iMj3Kreu+aEkT4C
> > PZvLsqIvLeX0WVEXSC8jwBAZbrOwJ+4TcMMnW2KZMeUPUHAd8rP0+Skj9AeQ4feJ
> > OfLqv52VdxYTnx+vYbvZSaOgWp8sC+PcoJxiJua7hpmqXwISbcG9eXxQHUil0fcv
> > tqfb2dv89VN12brFuQbFtgEK2RG6gKtbj7IQkeQqzt0g5WL6UnJ5OslajcEJwIA4
> > H6H4eke5CQUugVTUv5cbCwmQDfAF2qF8JgsxuuQDPvQRb4+XH1ks/5SEhENItv0=
> > =JTMu
> > -END PGP SIGNATURE-
>
> 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-unsubscr...@freebsd.org"


Re: CURRENT: net/igb broken

2015-09-21 Thread O. Hartmann
On Sat, 19 Sep 2015 11:23:44 -0700
Sean Bruno  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> 
> 
> 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  > > 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  
> > mailing list 
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current To
> > unsubscribe, send any mail to 
> > "freebsd-current-unsubscr...@freebsd.org 
> > "
> > 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
> 
> iQF8BAEBCgBmBQJV/agsXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
> ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx
> MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kkkMH/icGgcIAdm3CIxtXtnhbE5E9
> N6RrBrgJruoRHP2geJ9UOUGp7MaFwS6AHcwCC7FvxoydzcsT+iMj3Kreu+aEkT4C
> PZvLsqIvLeX0WVEXSC8jwBAZbrOwJ+4TcMMnW2KZMeUPUHAd8rP0+Skj9AeQ4feJ
> OfLqv52VdxYTnx+vYbvZSaOgWp8sC+PcoJxiJua7hpmqXwISbcG9eXxQHUil0fcv
> tqfb2dv89VN12brFuQbFtgEK2RG6gKtbj7IQkeQqzt0g5WL6UnJ5OslajcEJwIA4
> H6H4eke5CQUugVTUv5cbCwmQDfAF2qF8JgsxuuQDPvQRb4+XH1ks/5SEhENItv0=
> =JTMu
> -END PGP SIGNATURE-

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-unsubscr...@freebsd.org"


Re: CURRENT: net/igb broken

2015-09-19 Thread Sean Bruno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512



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  > 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  
> mailing list 
> https://lists.freebsd.org/mailman/listinfo/freebsd-current To
> unsubscribe, send any mail to 
> "freebsd-current-unsubscr...@freebsd.org 
> "
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQF8BAEBCgBmBQJV/agsXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx
MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kkkMH/icGgcIAdm3CIxtXtnhbE5E9
N6RrBrgJruoRHP2geJ9UOUGp7MaFwS6AHcwCC7FvxoydzcsT+iMj3Kreu+aEkT4C
PZvLsqIvLeX0WVEXSC8jwBAZbrOwJ+4TcMMnW2KZMeUPUHAd8rP0+Skj9AeQ4feJ
OfLqv52VdxYTnx+vYbvZSaOgWp8sC+PcoJxiJua7hpmqXwISbcG9eXxQHUil0fcv
tqfb2dv89VN12brFuQbFtgEK2RG6gKtbj7IQkeQqzt0g5WL6UnJ5OslajcEJwIA4
H6H4eke5CQUugVTUv5cbCwmQDfAF2qF8JgsxuuQDPvQRb4+XH1ks/5SEhENItv0=
=JTMu
-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-unsubscr...@freebsd.org"


Re: CURRENT: net/igb broken

2015-09-18 Thread O. Hartmann
Am Fri, 18 Sep 2015 09:50:19 -0700
Sean Bruno  schrieb:

> 
> > 
> > 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


I have no access to the hardware before Monday, 21st, so we need to wait a bit.

Regards,

Oliver


pgpg74WuR1qpU.pgp
Description: OpenPGP digital signature


Re: CURRENT: net/igb broken

2015-09-18 Thread Sean Bruno

> 
> 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 mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: CURRENT: net/igb broken

2015-09-18 Thread Eric Joyner
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

On Fri, Sep 18, 2015 at 9:50 AM Sean Bruno  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 mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: CURRENT: net/igb broken

2015-09-17 Thread O. Hartmann
On Tue, 15 Sep 2015 18:45:35 +
"Pieper, Jeffrey E" <jeffrey.e.pie...@intel.com> wrote:

> -Original Message-
> From: owner-freebsd-curr...@freebsd.org
> [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Hans Petter Selasky
> Sent: Tuesday, September 15, 2015 4:11 AM To: O. Hartmann
> <ohart...@zedat.fu-berlin.de>; freebsd-current <freebsd-current@freebsd.org>
> Subject: Re: CURRENT: net/igb broken
> 
> On 09/15/15 12:56, O. Hartmann wrote:
> > Running CURRENT as of today (r287817), it seems that the network system of
> > CURRENT is corrupted. The machine in question is a Fujitsu server Primergy
> > RX 1330 with two Intel "igb" devices (igb0 and igb1).
> >
> > the network is now on both devices unreachable. With or without IPFW
> > (disabling, having first rule to allow everything in/out) doesn't matter.
> > Nothing get to or from that box on any device.
> >
> > With FreeBSD 11.0-CURRENT #4 r287592: Wed Sep  9 09:09:23 CEST 2015  amd64 I
> > had no problems.
> >
> > Any ideas?
> >
> > Thanks in advance,
> >
> > Oliver
> >
> >Just to rule out r287775, can you disable TSO?
> >
> >--HPS
> 
> I'm using r827826 (just pulled this morning) with igb and it seems to be
> working (icmp and ssh).
> 
> Jeff
> 
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Well, driver igb covers a lot of different hardware. We have a Fujitsu
Primergy287700 RX 1330 M1 and it is equipted with a i210 Intel dual GBit NIC.

I double checked today, r287910 doesn't work. Since I use nanoBSD, I can change
the underlying OS with the very same configuration and I did today with
different revisions and 10-STABLE. r287420 and r287700 work also, r287750 also,
r287800 does NOT!

There were changes to sys/dev/e1000/ between 287750 and r287800 and those
obviously do break the igb interface in CURRENT for, at least, i210 NICs.

oh
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: CURRENT: net/igb broken

2015-09-17 Thread O. Hartmann
On Thu, 17 Sep 2015 13:35:09 +0200
"O. Hartmann" <ohart...@zedat.fu-berlin.de> wrote:

> On Tue, 15 Sep 2015 18:45:35 +
> "Pieper, Jeffrey E" <jeffrey.e.pie...@intel.com> wrote:
> 
> > -Original Message-
> > From: owner-freebsd-curr...@freebsd.org
> > [mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Hans Petter Selasky
> > Sent: Tuesday, September 15, 2015 4:11 AM To: O. Hartmann
> > <ohart...@zedat.fu-berlin.de>; freebsd-current <freebsd-current@freebsd.org>
> > Subject: Re: CURRENT: net/igb broken
> > 
> > On 09/15/15 12:56, O. Hartmann wrote:
> > > Running CURRENT as of today (r287817), it seems that the network system of
> > > CURRENT is corrupted. The machine in question is a Fujitsu server Primergy
> > > RX 1330 with two Intel "igb" devices (igb0 and igb1).
> > >
> > > the network is now on both devices unreachable. With or without IPFW
> > > (disabling, having first rule to allow everything in/out) doesn't matter.
> > > Nothing get to or from that box on any device.
> > >
> > > With FreeBSD 11.0-CURRENT #4 r287592: Wed Sep  9 09:09:23 CEST 2015
> > > amd64 I had no problems.
> > >
> > > Any ideas?
> > >
> > > Thanks in advance,
> > >
> > > Oliver
> > >
> > >Just to rule out r287775, can you disable TSO?
> > >
> > >--HPS
> > 
> > I'm using r827826 (just pulled this morning) with igb and it seems to be
> > working (icmp and ssh).
> > 
> > Jeff
> > 
> > ___
> > freebsd-current@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 
> Well, driver igb covers a lot of different hardware. We have a Fujitsu
> Primergy287700 RX 1330 M1 and it is equipted with a i210 Intel dual GBit NIC.
> 
> I double checked today, r287910 doesn't work. Since I use nanoBSD, I can
> change the underlying OS with the very same configuration and I did today with
> different revisions and 10-STABLE. r287420 and r287700 work also, r287750
> also, r287800 does NOT!
> 
> There were changes to sys/dev/e1000/ between 287750 and r287800 and those
> obviously do break the igb interface in CURRENT for, at least, i210 NICs.
> 
> oh
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

r287762 broke the system
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


RE: CURRENT: net/igb broken

2015-09-15 Thread Pieper, Jeffrey E
-Original Message-
From: owner-freebsd-curr...@freebsd.org 
[mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Hans Petter Selasky
Sent: Tuesday, September 15, 2015 4:11 AM
To: O. Hartmann <ohart...@zedat.fu-berlin.de>; freebsd-current 
<freebsd-current@freebsd.org>
Subject: Re: CURRENT: net/igb broken

On 09/15/15 12:56, O. Hartmann wrote:
> Running CURRENT as of today (r287817), it seems that the network system of
> CURRENT is corrupted. The machine in question is a Fujitsu server Primergy RX
> 1330 with two Intel "igb" devices (igb0 and igb1).
>
> the network is now on both devices unreachable. With or without IPFW
> (disabling, having first rule to allow everything in/out) doesn't matter.
> Nothing get to or from that box on any device.
>
> With FreeBSD 11.0-CURRENT #4 r287592: Wed Sep  9 09:09:23 CEST 2015  amd64 I
> had no problems.
>
> Any ideas?
>
> Thanks in advance,
>
> Oliver
>
>Just to rule out r287775, can you disable TSO?
>
>--HPS

I'm using r827826 (just pulled this morning) with igb and it seems to be 
working (icmp and ssh).

Jeff

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: CURRENT: net/igb broken

2015-09-15 Thread Hans Petter Selasky

On 09/15/15 12:56, O. Hartmann wrote:

Running CURRENT as of today (r287817), it seems that the network system of
CURRENT is corrupted. The machine in question is a Fujitsu server Primergy RX
1330 with two Intel "igb" devices (igb0 and igb1).

the network is now on both devices unreachable. With or without IPFW
(disabling, having first rule to allow everything in/out) doesn't matter.
Nothing get to or from that box on any device.

With FreeBSD 11.0-CURRENT #4 r287592: Wed Sep  9 09:09:23 CEST 2015  amd64 I
had no problems.

Any ideas?

Thanks in advance,

Oliver


Just to rule out r287775, can you disable TSO?

--HPS

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"