From owner-freebsd-current@freebsd.org Tue Nov 7 13:56:05 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 301FCE59433; Tue, 7 Nov 2017 13:56:05 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E95726778F; Tue, 7 Nov 2017 13:56:04 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id y15so2472915ita.4; Tue, 07 Nov 2017 05:56:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=t1VKZpRyqkrxH+N4TdNRE1zbRQj+UZv0UM6P4f7gvkY=; b=T9RVUSEta2MozudGmXs8dIJuo8GDevt+Mx7/g8t6M/Mfo/szopN7pfocTguRoRjeTa SshjndGbcjidXKpYOvt3dwpS0zGDR0BTg1QYFl8g+8O6+rhG2cd4wRTnr4aYHk7LLgEy EaDJzpf6C9/wDDPDLwP7tDlqLce87Mup12mpZk1nR791aW+FtgtCS80RbkEBm75AiAcD +IgHlNlup7Si6RTP8F9Nlvq4Nqetna9qF9SvRZnx1wBBm6rnpLVdL1Yj1Kp4BkxlH647 NBxm1zbvQBTqJTw3i8oMefXwrS0P+7GpfsK5m19ZMvB+9YR0O4YMqf3xT14z9DTW2XH0 JpqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=t1VKZpRyqkrxH+N4TdNRE1zbRQj+UZv0UM6P4f7gvkY=; b=XwM9ly5biA8MpD3niFE9+s4VofdmdkZ1bgr3lXUetYJwgfwaRTR9vGxlwtFJPCWsu7 5SfvUepbiWGcnK2gDUlUiloduu3Ebpfy9i88I7A9mUpqBF+t51Dw/V8mMn7ZGhut1ByP xNQ9yv4vRqA8Sv1m00WHYobMBVlTeX7Hycu41li4RzqGmt3VhQUFbpv6nU+fzCfEiHB5 Q77zPDzDj0eIxMOddwy0z73xZQ1WugPICTSCOSsYnRkon44uWzt/foXxFMnxdBgwCUrn lBlL2TakCEJVbqrrKpjw6y/LpEAd9lgr2V7Ir6lPku4cyGHA6evy39Ivd0st6E3Wd6Q3 onvQ== X-Gm-Message-State: AJaThX4xXuJIEQdh6sUpT67P0KZG3/Jc7pQNauPQ3olDPIVlgh7nZwD1 g8iqPqtYXz2VEIqj11Ukgqfl+Q== X-Google-Smtp-Source: ABhQp+T68lHvYV/pefaTkTURIyS1b3vq0wYu+AVYNx2kqIXOgtD4bKmUjnNt0BTo72ObEWuY3/uIlA== X-Received: by 10.36.81.21 with SMTP id s21mr2188400ita.144.1510062964334; Tue, 07 Nov 2017 05:56:04 -0800 (PST) Received: from [10.0.10.7] (cpe-65-25-50-122.neo.res.rr.com. [65.25.50.122]) by smtp.googlemail.com with ESMTPSA id 76sm464012itk.23.2017.11.07.05.56.03 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 07 Nov 2017 05:56:03 -0800 (PST) Message-ID: <5A01BB73.5060501@gmail.com> Date: Tue, 07 Nov 2017 08:56:03 -0500 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: pyunyh@gmail.com CC: "freebsd-questions@freebsd.org" , FreeBSD current Subject: Re: watchdog timeout problem References: <59FB27FB.6060704@gmail.com> <20171102143547.GA1065@michelle.fasterthan.co.kr> In-Reply-To: <20171102143547.GA1065@michelle.fasterthan.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Nov 2017 13:56:05 -0000 YongHyeon PYUN wrote: > On Thu, Nov 02, 2017 at 10:13:15AM -0400, Ernie Luzar wrote: >> Posted this 10/31/2017 got no reply. >> >> Been getting these error messages since about release 10.0 I think. >> Have changed to new hardware box and new cable modem and still having >> the same error messages. Also occurs when I use em0 interface to connect >> to the public internet instead of vge0. >> >> vge0: flags=8843 >> metric 0 mtu 1500 >> options=389b> WOL_UCAST,WOL_MCAST,WOL_MAGIC> >> ether 00:0b:db:19:33:18 >> hwaddr 10:00:60:21:00:93 >> inet xxx.xxx.xxx.xxx netmask 0xfffff000 >> broadcast 255.255.255.255 >> nd6 options=29 >> media: Ethernet autoselect (1000baseT ) >> status: active >> >> >> >> Oct 30 23:43:38 fbsd kernel: vge0: watchdog timeout >> Oct 30 23:43:38 fbsd kernel: vge0: link state changed to DOWN >> Oct 30 23:43:42 fbsd kernel: vge0: link state changed to UP >> >> 11/2/2017 posting this now as a update >> >> I have continued to research this problem. >> The "man watchdog" says that the command, >> watchdog -d will provide debugging info, and >> watchdog -t will set a new timeout timer value >> >> When I issue either of those commands I get this error message >> watchdog: patting the dog: Operation not supported >> >> The man page also says a value of -t 0 disables the watchdog function. >> >> Issuing "watchdog -t 0" does not get that above error message, but the >> watchdog function is still enabled because I am still getting the >> >> kernel: vge0: watchdog timeout >> kernel: vge0: link state changed to DOWN >> kernel: vge0: link state changed to UP >> >> messages. >> For the archives. After a lot of trial and error testing finally determined the cause of this problem is ddclient. When I disable ddclient from running those messages stop happening. ddclient is a dynamic DNS auto updater written in perl. I have now deinstalled ddclient and written my own dynamic DNS auto updater sh script that I am calling dynip with intention to add it to the port system later.