From owner-freebsd-questions@freebsd.org Thu Nov 2 14:13:17 2017 Return-Path: Delivered-To: freebsd-questions@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 CB5C1E5AC3C; Thu, 2 Nov 2017 14:13:17 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 92A948014C; Thu, 2 Nov 2017 14:13:17 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-io0-x235.google.com with SMTP id 101so14304054ioj.3; Thu, 02 Nov 2017 07:13:17 -0700 (PDT) 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:subject :content-transfer-encoding; bh=dDiy2HXxNia9kxPWXSJD4gI6mU8RzZ8lcb6v5GKmkBI=; b=WJICb4GQb9Z65aWamSeudVAnx7M7q4DV22aSRwAW/swn1kAPyuLFolfsZD3zL8LZKB 7S4e32mUhkEX9BqpCyQ0xXsGjFnq5lStFpESRhheE3FzAohopFeb0fjq4g0cm7fjQm9G l+nZtwcMUkmIc9R4Jcl2UnKtzkHnL1ZhJ6/XH3aijvPbDhfgcYq6MCg7j5FeT0pMnDNS dX3IaZTB+qq5AN83dygj/pJbm/mZxMB1WSBEY5zXgZMJhKaCVLL8+25yF+UqNCgpeaFd mte1+lFAx0TxPJHAvNq/TOOL9txho+BjNLsMPjWQ38toTVtGxd8CYGs14VIgRZmF242j P5JA== 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 :subject:content-transfer-encoding; bh=dDiy2HXxNia9kxPWXSJD4gI6mU8RzZ8lcb6v5GKmkBI=; b=EYUiFx++/oqw8Ku8iKiR4xqcLIw8s5WS2y8XEQtywQhIXuxO4i75bQD7ZBRaCyzezl 9zYA4lJqu8XPc4g+ASIvgQenfOGFOl7mID3WwEBGFGHoDO4On0+hzhgdjDV9Ym9wObfd woNLqqXkWR4WCRZSU1oHoh9pnwolBHdVTiARMEsZFMrDi2g/sa0JQIoxS93eYZvw+qKY i4PRsD/cN5yDcUbeyUS7X9WR5V97+zZUwfIpoEMblNnrus1aP0IqiYeYPxKvtUQCVRzU 1iLojUA4C6jQbK/H6pMVN0EVz8evZdOZWFPNLrP5ErCw1TC2eGyp4KDGmQw/HgNCsXpz ga4A== X-Gm-Message-State: AJaThX4lSE7HsX0Shx/HthZuxkuzTNWxqOBeNjKR1ZV2DJZfnnzRpXDj zDq92lJed4bhLCOvIv6xKKpzsQ== X-Google-Smtp-Source: ABhQp+QxB1+RHdjD5qvgMxYqwWgiRTBkeeLPxuTafsJ12RdP9YAcdzXZYdWRm1FkNCwW+pj38BBrrA== X-Received: by 10.107.11.219 with SMTP id 88mr4620236iol.78.1509631996817; Thu, 02 Nov 2017 07:13:16 -0700 (PDT) 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 e68sm1166798ite.0.2017.11.02.07.13.15 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 02 Nov 2017 07:13:16 -0700 (PDT) Message-ID: <59FB27FB.6060704@gmail.com> Date: Thu, 02 Nov 2017 10:13:15 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: "freebsd-questions@freebsd.org" , FreeBSD current Subject: watchdog timeout problem Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Nov 2017 14:13:17 -0000 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 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 Oct 30 23:58:39 fbsd kernel: vge0: watchdog timeout Oct 30 23:58:39 fbsd kernel: vge0: link state changed to DOWN Oct 30 23:58:43 fbsd kernel: vge0: link state changed to UP Oct 31 01:08:38 fbsd kernel: vge0: watchdog timeout Oct 31 01:08:38 fbsd kernel: vge0: link state changed to DOWN Oct 31 01:08:42 fbsd kernel: vge0: link state changed to UP Oct 31 01:53:39 fbsd kernel: vge0: watchdog timeout Oct 31 01:53:39 fbsd kernel: vge0: link state changed to DOWN Oct 31 01:53:43 fbsd kernel: vge0: link state changed to UPdob Oct 31 04:58:46 fbsd kernel: vge0: watchdog timeout Oct 31 04:58:46 fbsd kernel: vge0: link state changed to DOWN Oct 31 04:58:50 fbsd kernel: vge0: link state changed to UP Oct 31 05:23:49 fbsd kernel: vge0: watchdog timeout Oct 31 05:23:49 fbsd kernel: vge0: link state changed to DOWN Oct 31 05:23:52 fbsd kernel: vge0: link state changed to UP Oct 31 05:57:40 fbsd kernel: vge0: watchdog timeout Oct 31 05:57:40 fbsd kernel: vge0: link state changed to DOWN Oct 31 05:57:43 fbsd kernel: vge0: link state changed to UP Oct 31 09:21:43 fbsd kernel: vge0: watchdog timeout Oct 31 09:21:43 fbsd kernel: vge0: link state changed to DOWN Oct 31 09:21:47 fbsd kernel: vge0: link state changed to UP Oct 31 09:28:21 fbsd kernel: vge0: watchdog timeout Oct 31 09:28:21 fbsd kernel: vge0: link state changed to DOWN Oct 31 09:28:25 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. Production box is running RELEASE AMD64 11.1 and has 16 MB memory, with 2 Gigabit interface cards em0 & vge0. Development box is running RELEASE i386 11.1 beta 1 and has 2 MB memory, with 2 100bps interface cards rl0 & xl0. The 2 boxes are desktops manufactured by 2 different name brand companies. Both computers run the same host services. Both computers experience the same watchdog problems. This watchdog problem is also present in RELEASE 11.0 and if my memory is correct also occurred in the 10.x series. I never paid attention to this problem until lately when I am now streaming HULU and the show stops because the internet connection is lost due to the link state being reset by watchdog. Now this problem is really a problem that is impacting me. Can't see how this could be a configuration problem on my part. That is why I am posting here before I post a bug report. Watchdog is in the kernel and debugging the kernel is way outside my abilities. Trying to get this problem in front of the correct audience.