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

    kernel: em1: Watchdog timeout -- resetting

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 452 Views 1 Watching
    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.
    • Cool_CoronaC Offline
      Cool_Corona
      last edited by

      Getting tons of these....

      Running Intel dual port ET 1000 pro adapters.

      a9affab8-ee86-4d9c-a37e-5bbbe92adb20-billede.png

      Everything seems to be working as it should.

      1 Reply Last reply Reply Quote 0
      • bmeeksB Offline
        bmeeks
        last edited by bmeeks

        Hmm... I would not say everything is working. Those errors point to something being really not right. If it just started up out of the blue, my first suspicion would be hardware. Could even be something as simple as the card needs reseating into the slot to make sure it has a good connection with the bus.

        There were issues with hardware watchdog timeouts with the generic FreeBSD drivers for Realtek NICs, and in that case compiling and using the Realtek-supplied native drivers corrected the problem. However, Intel NICs have historically been very well behaved in FreeBSD using the kernel drivers.

        Just asking, but are you 100% positive beyond a shadow of a doubt that you have genuine Intel NIC hardware? There are some cheap Chinese knockoffs of popular Intel NICs out there for sale. If you got a "steal of a deal" on the NIC, I would be suspicious.

        Cool_CoronaC 1 Reply Last reply Reply Quote 0
        • Cool_CoronaC Offline
          Cool_Corona @bmeeks
          last edited by

          @bmeeks said in kernel: em1: Watchdog timeout -- resetting:

          Hmm... I would not say everything is working. Those errors point to something being really not right. If it just started up out of the blue, my first suspicion would be hardware. Could even be something as simple as the card needs reseating into the slot to make sure it has a good connection with the bus.

          There were issues with hardware watchdog timeouts with the generic FreeBSD drivers for Realtek NICs, and in that case compiling and using the Realtek-supplied native drivers corrected the problem. However, Intel NICs have historically been very well behaved in FreeBSD using the kernel drivers.

          Just asking, but are you 100% positive beyond a shadow of a doubt that you have genuine Intel NIC hardware? There are some cheap Chinese knockoffs of popular Intel NICs out there for sale. If you got a "steal of a deal" on the NIC, I would be suspicious.

          Hi B.

          Yeah. 100% sure. Bought them off Intel themselves :)

          I went to the Interface page and chose autoselect instaed of default and the errors were gone immediately.

          Weird.

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