[Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Jul 16 17:00:36 UTC 2019


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

IPTRACE <arkadiusz.majewski at iptrace.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |arkadiusz.majewski at iptrace.
                   |                            |pl

--- Comment #1 from IPTRACE <arkadiusz.majewski at iptrace.pl> ---
Hello!

I'm affected as well for FreeBSD 12.0-RELEASE-p7.

kernel: igb0: TX(0) desc avail = 1024, pidx = 0
...
kernel: igb2: TX(5) desc avail = 1024, pidx = 0


igb0 at pci0:129:0:0:      class=0x020000 card=0x00001458 chip=0x15218086 rev=0x01
hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'I350 Gigabit Network Connection'
    class      = network
    subclass   = ethernet


igb2 at pci0:132:0:0:      class=0x020000 card=0xa02c8086 chip=0x10e88086 rev=0x01
hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '82576 Gigabit Network Connection'
    class      = network
    subclass   = ethernet


Use case (forced by me but generally it happens randomly):
1. All was working.
2. I detached Ethernet cable from modem side.
3. Connected again and saw "no carrier" on igb0 interface.
4. System logged as follow:
      Jul  5 22:31:35 hpv kernel: igb0: TX(0) desc avail = 1024, pidx = 0
      Jul  5 22:31:38 hpv kernel: igb0: TX(0) desc avail = 1024, pidx = 0
      Jul  5 22:31:40 hpv kernel: igb0: TX(0) desc avail = 1024, pidx = 0
5. I was trying "server:# service netif restart igb0 && service routing
restart" without success.
6. Resarted OS to back to normal.

Is there any workaround instead of restart a system?
I was trying below without progress as well.

# ifconfig igb0 down
# ifconfig igb0 up

I think the problem is when the network card loses ethernet link and then
errors occurs with non-working interface?!

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-net mailing list