[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-amd64
Subject:    [Bug 205759] igb cannot receive packets on first port only
From:       bugzilla-noreply () freebsd ! org
Date:       2015-12-31 17:14:39
Message-ID: bug-205759-6 () https ! bugs ! freebsd ! org/bugzilla/
[Download RAW message or body]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205759

            Bug ID: 205759
           Summary: igb cannot receive packets on first port only
           Product: Base System
           Version: 11.0-CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: sbruno@FreeBSD.org
          Reporter: asomers@FreeBSD.org
                CC: Alexander@Leidinger.net, erj@freebsd.org,
                    freebsd-amd64@FreeBSD.org
                CC: freebsd-amd64@FreeBSD.org

Created attachment 164902
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=164902&action=edit
Alexander L's example fix.  Not a permanent solution.

On two separate systems with Intel S5520HC motherboards, FreeBSD CURRENT cannot
receive any packets on igb0.  igb1 works fine, and igb0 works when booted into
FreeBSD 9/stable.

* 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.
* Alexander Leidinger reported a similar problem, but didn't specify whether
all igb ports were broken or only one (or even whether he had multiple ports). 
He reported that 11-CURRENT worked at svn r287323, but failed at r290633.
* Alexander also provided the attached patch, which fixes the issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
freebsd-amd64@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-amd64
To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]