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

    Watchdog timeout – resetting

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    3 Posts 3 Posters 4.9k 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.
    • T Offline
      ToxIcon
      last edited by

      2.0-RC1 (i386)
      built on Thu Mar 10 09:34:40 EST 2011

      updated to today snap to fix errors listed below but problem is still their

      Mar 10 15:05:04 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.92.1)
      Mar 10 15:05:04 kernel: em1: link state changed to DOWN
      Mar 10 15:05:04 kernel: em1: Watchdog timeout – resetting
      Mar 10 15:05:04 check_reload_status: Linkup starting em1
      Mar 10 15:04:36 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.92.1)
      Mar 10 15:04:36 kernel: em1: link state changed to UP
      Mar 10 15:04:36 check_reload_status: Linkup starting em1
      Mar 10 15:04:33 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.92.1)
      Mar 10 15:04:33 kernel: em1: link state changed to DOWN
      Mar 10 15:04:33 kernel: em1: Watchdog timeout -- resetting

      all connection is lost  reboot box manually
      to get connection back

      1 Reply Last reply Reply Quote 0
      • N Offline
        Notanial
        last edited by

        look this

        1 Reply Last reply Reply Quote 0
        • stephenw10S Offline
          stephenw10 Netgate Administrator
          last edited by

          That thread refers to FreeBSD 7 and 2.0rc1 is based on FreeBSD 8.1.
          You are already running a more up to date driver than that.
          You can see which driver you are using by viewing the sysctl:

          
          [1.2.3-RELEASE]                                                                 
          [root@fire.box]/root(2): sysctl dev.em.1.%desc
          dev.em.1.%desc: Intel(R) PRO/1000 Network Connection 6.9.6
          
          

          I am running 1.2.3 on this box as you can see. You will have the legacy driver, which is newer!  ::)

          Steve

          Edit: Finally found a good explaination. From version 7.0.0 of the driver the code was seperated into two em and lem, although you won't see that as an end user. The lem driver is for legacy adapters, which is anything pre PCI express.

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