From owner-freebsd-questions@freebsd.org Thu Nov 2 14:35:54 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 0FC19E5B672; Thu, 2 Nov 2017 14:35:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 CFDD880E51; Thu, 2 Nov 2017 14:35:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by mail-pf0-x22d.google.com with SMTP id d28so4779076pfe.2; Thu, 02 Nov 2017 07:35:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-disposition:in-reply-to:user-agent; bh=xVo/GE8kSq10pm5Xljp8AiTOfHmehGQd24TNa+HEArY=; b=re9SNiW/jt74QeS0m0Pa4GTNudmNhnusuaXF8+Uld61MovkECulbfUX91+ZqsgOK/B oEIqgfEsqVP2jpIFACuXCRv2EaBkri/gBfIw/Iy1JnKuv4CV1947v47XA4alqAcxiMby XONX8RQzeb4tpGZDGYke/AvqM1QR72C2KqG7YXm50xawOwUgsDFuLUEYaLY3/MuHhXX4 HQKnaeFBjo3DITH01iZZOlkCluvZ13UR6pXRxF50wbhXwVejK4Kub5kRvKxsLUUKvtAK zbJF0JkHj/GKtEA+P979AcovYLfj75mmSwcEkpIHxLGfXWVg1AOv4mfyRJZiOqbKGl4k TW0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:reply-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=xVo/GE8kSq10pm5Xljp8AiTOfHmehGQd24TNa+HEArY=; b=ZaoQPbpEWsl8SBZsLVEXv49fAXR6mEfHk2XlHVkBGacg1olcU20d8Wl4KINtTY4+GM NCx8OdWjal8+PVFHqrMYyy6lcu3WF4WthwCkKc/Tgyye5A1NNIdNTfsIM5PUzIduoiRE MXxD0ZEFBuOyVd2WpW5j0Hv+wqCQU2/qzXGwr6e2c32sZP8Yfx1G7tQyZ9DkTwNFVq0f tY3N4rqEpBtdtT6QlG3smhKPBfp9bBCTgeLzizjynwFmdtDbyfeFxdMZyUaNQIayYuPZ XF7VFrbhrwtfGwe9NTx0ssRnXD9tZyBEQ1RSWPh1H+809Y0vIYMSV2X8X5Dttl5ZBXrD tYMQ== X-Gm-Message-State: AMCzsaXJBsY9AR7RQMFfK2f+KXjDSHy2cOKPHkSxJi4wY2nyKPyHRLLh Ty3Sx4Htyhn7xudk1Z7DJrU= X-Google-Smtp-Source: ABhQp+RtYzJPm8og/B6NXlyqEr47IS9WX4L4/QGtCusFv/6MYJmoMRn2ETZY/LWCIrbf/4TPJXMcDQ== X-Received: by 10.99.123.84 with SMTP id k20mr3787823pgn.444.1509633353332; Thu, 02 Nov 2017 07:35:53 -0700 (PDT) Received: from localhost ([116.46.79.45]) by smtp.gmail.com with ESMTPSA id u188sm5812448pfb.188.2017.11.02.07.35.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Nov 2017 07:35:51 -0700 (PDT) From: YongHyeon PYUN X-Google-Original-From: "YongHyeon PYUN" Received: by localhost (sSMTP sendmail emulation); Thu, 02 Nov 2017 23:35:47 +0900 Date: Thu, 2 Nov 2017 23:35:47 +0900 To: Ernie Luzar Cc: "freebsd-questions@freebsd.org" , FreeBSD current Subject: Re: watchdog timeout problem Message-ID: <20171102143547.GA1065@michelle.fasterthan.co.kr> Reply-To: pyunyh@gmail.com References: <59FB27FB.6060704@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <59FB27FB.6060704@gmail.com> User-Agent: Mutt/1.4.2.3i 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:35:54 -0000 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 [...] Would you show me the output of dmesg? > > 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. > The watchdog timeout message is generated when vge(4) didn't see transmit completion interrupts. It has nothing to do with watchdog(8) or watchdog(4).