pfSense becomes unresponsive, dying NIC?



  • Hi, first apologies I would normally search or google first but my internet is up and down. So quick question, I'm seeing a lot of this, any ideas? Replace the network card? Thanks.

    Jun 3 17:31:05 kernel em0: RX Next to Refresh = 729
    Jun 3 17:31:05 kernel em0: RX Next to Check = 730
    Jun 3 17:31:05 kernel em0: RX discarded packets = 0
    Jun 3 17:31:05 kernel em0: hw rdh = 730, hw rdt = 729
    Jun 3 17:31:05 kernel em0: RX Queue 0 ------
    Jun 3 17:31:05 kernel em0: Tx Descriptors avail failure = 0
    Jun 3 17:31:05 kernel em0: TX descriptors avail = 1021
    Jun 3 17:31:05 kernel em0: Tx Queue Status = -2147483648
    Jun 3 17:31:05 kernel em0: hw tdh = 58, hw tdt = 61
    Jun 3 17:31:05 kernel em0: TX Queue 0 ------
    Jun 3 17:31:05 kernel Interface is RUNNING and ACTIVE
    Jun 3 17:31:05 kernel em0: Watchdog timeout Queue[0]-- resetting


  • Netgate Administrator

    Not necessarily. This just started happening? At upgrade?

    What are you running on?

    What is em0 connected to?

    Steve



  • I'm 99% sure after upgrading to latest version. On hardware? Not a VM if that's what you mean. em0 is connected to my switch, it's the VLAN trunk interface.

    Thanks.


  • Netgate Administrator

    As a test I would swap the NICs and see if the fault follows the hardware or the assigned interface.

    Steve



  • I too just started seeing the same errors on the physical console and lost connectivity to the pfSense node.
    Jun 3 13:31:05 kernel em0: Watchdog timeout Queue[0]-- resetting
    Jun 3 13:31:05 kernel Interface is RUNNING and ACTIVE
    Jun 3 13:31:05 kernel em0: TX Queue 0 ------
    Jun 3 13:31:05 kernel em0: hw tdh = 167, hw tdt = 177
    Jun 3 13:31:05 kernel em0: Tx Queue Status = -2147483648
    Jun 3 13:31:05 kernel em0: TX descriptors avail = 1014
    Jun 3 13:31:05 kernel em0: Tx Descriptors avail failure = 0
    Jun 3 13:31:05 kernel em0: RX Queue 0 ------
    Jun 3 13:31:05 kernel em0: hw rdh = 808, hw rdt = 879
    Jun 3 13:31:05 kernel em0: RX discarded packets = 0
    Jun 3 13:31:05 kernel em0: RX Next to Check = 880
    Jun 3 13:31:05 kernel em0: RX Next to Refresh = 879

    In my case the netgear switch had flaked out and partially zapped it's VLAN configuration. I did switch assignments and ports and the issue still existed. Once the VLANs were restored at the switch level, then the errors stopped. The Netgear switch is a "GS116Ev2 - 16-Port Gigabit ProSAFE Plus Switch" which is usually quite stable.



  • It's actually been stable for the last week. I'm glad you mentioned that mine is a Netgear switch too so if it happens again I'll take care on that.

    Thanks all.


Log in to reply