Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Dc0 Network Freezing

    Scheduled Pinned Locked Moved Hardware
    3 Posts 2 Posters 3.6k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H
      heathcole
      last edited by

      I know the question about dc0 "failed to force tx and rx to idle state" has been talked about on FreeBSD forums till its ears are red. But I'm haveing a intresting symptom that I was wondering if anyone could help me with.

      I have 2 nics, dc0 is built into the motherboard(Davicom 9102 chip) and the other is a pci SMC EZ. I would actually like to just disable the dc0 but I only have 1 pci slot on this old motherboard.

      When pfSense starts up its dmesg says:

      rl0: link state changed to UP
      dc0: link state changed to UP
      rl0: link state changed to DOWN
      rl0: link state changed to UP
      dc0: failed to force tx and rx to idle state
      dc0: failed to force tx and rx to idle state
      dc0: failed to force tx and rx to idle state
      dc0: failed to force tx and rx to idle state
      pflog0: promiscuous mode enabled
      dc0: failed to force tx and rx to idle state
      rl0: promiscuous mode enabled

      Now "dc0: failed to force tx and rx to idle state" continues, over and over, after about 4-6 hours I see "dc0: TX underrun – increasing TX threshold" and the whole network freezes. Usally if I just wait 10min or so, everything is fine again for another 4-6 hours, but this usally throws downloads off track and annoys the people tring ot surf.

      Any ideas would be much appreciated, thanks.

      Edit: If its important, its a 333mhz celeron cpu, running pfsense Beta2 on a 4gb Bigfoot HD, 64mb ram, 300watt psu. dc0 is my WAN and is connecting via DHCP to my ISP Charter Communications.

      1 Reply Last reply Reply Quote 0
      • H
        hoba
        last edited by

        Not sure if there is something that can be done against the dc problems or if it is a known driver issue but there are multi port nics available (one pci card with several nics) if this is an option.

        1 Reply Last reply Reply Quote 0
        • H
          heathcole
          last edited by

          Wow I didnt think of that, thanks! I really wanted to disable as much onboard stuff as possible to prevent CPU usage. Thats a great solution thanks alot, I feel kinda dumb now.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.