Re: This igb change makes my igb not working anymore - Re: regression in igb/clang?

I'm experiencing the same problem, and I can confirm that Alexander's
workaround fixes it.  Here is some more information:

* I see the exact same problem on two different systems, both with
S5520HC motherboards.
* Both systems have two igb ports, and igb1 works on both.  Only igb0 is broken.
* Disabling tso, lro, rxcsum, and txcsum has no effect.
* tcpdump reveals that igb0 transmits successfully, but fails to receive
* Curiously, "netstat -I igb0" shows nonzero values for Ipkts, even
though "tcpdump  -i igb0" shows no inbound packets at all.
* I can't really tell if IPv4 or IPv6 are working, because even ARP
doesn't work.
* SVN revisions 291495 and 292570 are both bad.  I don't know any
recent good revision.

-Alan

On Thu, Nov 19, 2015 at 11:21 PM, Alexander Leidinger
<Alexander_at_leidinger.net> wrote:
> Dual stack.
> Ping was on ipv4, no answer. Without the line I get the answer.
> I have not tried a ping6.
> --
> Send from a mobile device, please forgive brevity and misspelling.
>
>
> Gesendet mit AquaMail für Android
> http://www.aqua-mail.com
>
>
> Am 20. November 2015 02:07:11 schrieb Eric Joyner <ricera10_at_gmail.com>:
>
>> Are you using IPv6?
>>
>> On Thu, Nov 19, 2015 at 12:42 PM Alexander Leidinger <
>> Alexander_at_leidinger.net> wrote:
>>
>>> On Wed, 11 Nov 2015 11:45:32 +0100
>>> Alexander Leidinger <Alexander_at_Leidinger.net> wrote:
>>>
>>> > Hi,
>>> >
>>> > I' updated a system with -current as of r287323 (end August) to
>>> > r290633 (yesterday).
>>> >
>>> > Result: no network connection (not even ping) on igb.
>>> > Ping internally (local addresses) works, anything outgoing/incoming
>>> > doesn't.
>>>
>>> And this is the function which causes it:
>>> e1000_rx_fifo_flush_82575(&adapter->hw);
>>>
>>> If I comment it out in if_igb.c, the network card works again.
>>>
>>> Full quote below for the PCI ID of my card in case it helps for fixing
>>> the issue.
>>>
>>> Bye,
>>> Alexander.
>>>
>>> > I disabled HW support (tso4, lro, rxcsum, txcsum): doesn't help.
>>> >
>>> > Did I miss some known defect/workaround?
>>> >
>>> > Anything I should test/provide besides what is below?
>>> >
>>> > The igb device is a:
>>> > ---snip---
>>> > igb0_at_pci0:1:0:0: class=0x020000 card=0x34e28086 chip=0x10a78086
>>> > rev=0x02 hdr=0x00 ---snip---
>>> >
>>> > My src.conf:
>>> > ---snip---
>>> > WITH_IDEA=yes
>>> > WITHOUT_PROFILE=yes
>>> > CFLAGS+=-DFTP_COMBINE_CWDS
>>> > MALLOC_PRODUCTION=yes
>>> > LOADER_FIREWIRE_SUPPORT=yes
>>> > #WITH_FAST_DEPEND=yes
>>> > ---snip---
>>> >
>>> > My buildworld related config in make.conf:
>>> > ---snip---
>>> > CFLAGS+= -O2 -pipe
>>> > COPTFLAGS= -O2 -pipe
>>> > #CPUTYPE?=core2
>>> > #WITH_CCACHE_BUILD=yes
>>> > #.if (!empty(.CURDIR:M/usr/src*)
>>> > || !empty(.CURDIR:M/usr/obj*)|| !empty(.CURDIR:M/space/system/usr_obj*))
>>> > #.if !defined(NOCCACHE) && exists(/usr/local/libexec/ccache/world/cc)
>>> > #CC:=${CC:C,^cc,/usr/local/libexec/ccache/world/cc,1}
>>> > #CXX:=${CXX:C,^c\+\+,/usr/local/libexec/ccache/world/c++,1} #.endif
>>> > #.endif
>>> > ---snip---
>>> >
>>> > The commented out parts were active initially, but then I commented
>>> > them out, cleaned out /usr/obj (rm -r) and rebuild/reinstall to make
>>> > sure it's not due to them (CPUTYPE commented out due to the fact that
>>> > there's a new compiler, and I use zsh and there was a commit talking
>>> > about zsh and CPUTYPE workaround).
>>> >
>>> > Bye,
>>> > Alexander.
>>> >
>>>
>>>
>>> --
>>> http://www.Leidinger.net Alexander_at_Leidinger.net: PGP 0xC773696B3BAC17DC
>>> http://www.FreeBSD.org    netchild_at_FreeBSD.org  : PGP 0xC773696B3BAC17DC
>>> _______________________________________________
>>> freebsd-current_at_freebsd.org mailing list
>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>>>
>
>
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"