From owner-freebsd-net@FreeBSD.ORG Fri Jul 9 16:26:57 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B6471065670 for ; Fri, 9 Jul 2010 16:26:57 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0F98B8FC19 for ; Fri, 9 Jul 2010 16:26:56 +0000 (UTC) Received: by gxk24 with SMTP id 24so1648893gxk.13 for ; Fri, 09 Jul 2010 09:26:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=JB98xSKIyhb5vLacL16kVr3ppWhYSIMqlQ43nQVjB/4=; b=jLTU6iUQAx5c6md6jhV77hdkPgD9gU+RALrSHAVUEcBXaGAzCccGuS1eH9FkWISgon uVaeR5iqbkuYwbiY92ZiMdinYy2/t5x+E2Xvz3LXfYxx/Mx6j27DesUqkubXqZM+lc9l bhMcMKXCf7aC+jv7+Ic4T+qPXBml2CdLFv1Qc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=UZDIPsJmT0UGzf5IpCuJB99OhEjRO67bJdkizt/ioJUUB18vb7kxNLDSOirVTLm22g 2TiWBLBe81a9XCRwmziY/8nDcpl6vTl4iaUrY92Lr5qYGa0yJ1/0eI+uf1oV/OhUu16A YjTZ0YwKJHh7L0k/qgEgz6gMPm0dz1R2hQ6Cs= MIME-Version: 1.0 Received: by 10.229.181.13 with SMTP id bw13mr6145565qcb.79.1278692810367; Fri, 09 Jul 2010 09:26:50 -0700 (PDT) Received: by 10.229.220.5 with HTTP; Fri, 9 Jul 2010 09:26:50 -0700 (PDT) In-Reply-To: <1278688046.20612.45.camel@stormi-desktop> References: <1278330234.10826.18.camel@stormi-desktop> <1278356796.10826.35.camel@stormi-desktop> <1278404933.20433.26.camel@stormi-desktop> <1278496982.21743.50.camel@stormi-desktop> <20100709233505.J54166@sola.nimnet.asn.au> <1278688046.20612.45.camel@stormi-desktop> Date: Fri, 9 Jul 2010 09:26:50 -0700 Message-ID: From: Jack Vogel To: Shtorm Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-net@freebsd.org, Ian Smith Subject: Re: Intel 82574L Gigabit Ethernet Controller X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jul 2010 16:26:57 -0000 LOL, the way the watchdog code works these days it records the clock at key TX points and then compares that in the timer code, so if your system is dinking around with the time that could be the cause of this. Can you change the environment to guarantee a continuous time stream and then see what happens?? Jack On Fri, Jul 9, 2010 at 8:07 AM, Shtorm wrote: > On Fri, 2010-07-09 at 23:58 +1000, Ian Smith wrote: > > On Wed, 7 Jul 2010, Shtorm wrote: > > > > > > > Yow, 30 vlans, but only em1 is using vlans not em0? > > > > > > > > Is only em1 having watchdogs? I noticed you appear to > > > > have flow control off, maybe turning it on would help. > > > > > > > > I would like to see the log messages from the watchdogs. > > > > Jack > > > > > > Yes, em0 - plain untagged traffic to border router, em1 - tagged - one > > > vlan per 200-300 pppoe clients. Anyway, I saw watchdogs on em0 too, > > > there is no logs for it because remote syslog server connected via em0 > > > and it looses messages during card reset, will enable local logs to > get > > > some info. > > > > > > Log files are almost empty, is there any driver-specific debugging > > > options other than TUNABLE_INT("hw.em.sbp", &em_debug_sbp)? Anyway > will > > > try to set it to 1 and wait for watchdog. > > > > > > Here is a part from log file I have now > > > > Deleting the stuff you're most interested in :) > > > > > Jul 6 10:32:34 ntp info hostname x.x.x.8 ntpd adjusting local clock > by 5.083720s > > > Jul 6 10:33:07 ntp info hostname x.x.x.8 ntpd adjusting local clock > by 4.915903s > > > Jul 6 10:35:01 auth info hostname x.x.x.8 login login on ttyv2 as > root > > > Jul 6 10:35:01 auth notice hostname x.x.x.8 login ROOT LOGIN (root) > ON ttyv2 > > > Jul 6 10:35:24 kern crit hostname x.x.x.8 kernel em1: Watchdog > timeout -- resetting > > [..] > > > Jul 6 10:37:21 ntp info hostname x.x.x.8 ntpd adjusting local clock > by 3.641940s > > > Jul 6 10:37:46 kern crit hostname x.x.x.8 kernel em1: Watchdog > timeout -- resetting > > [..] > > > Jul 6 10:38:40 kern crit hostname x.x.x.8 kernel Limiting icmp > unreach > > > response from 237 to 200 packets/sec > > > Jul 6 10:39:10 kern crit hostname x.x.x.8 kernel em1: Watchdog > timeout > -- resetting > > > > Probably completely unrelated, but I can't help noticing those big clock > > shifts by ntp over a short period amidst all this. I don't know if that > > could affect watchdogs, but is it a regular occurrence during these? > > > > >From your latest, a bit more noise from ntp: > > > > > Jul 8 07:23:40 server kernel: em0: Watchdog timeout -- > resetting > > [..] > > > Jul 8 07:23:56 server ntpd[3687]: 2 out of 3 peers valid > > > Jul 8 07:23:56 server ntpd[3687]: bad peer from pool > pool.ntp.org (195.214.215.17) > > > Jul 8 07:27:15 server kernel: em0: Watchdog timeout -- > resetting > > > > Ignore if not relevant. > > > > cheers, Ian > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > Yeah, saw this too, it was first boot for this install and I forgot to > run tzsetup during flash image build. > > As for the latest log, this box connected to internet via em0, ntpd just > says it have some peers to sync with after interface flap. > > Thanks. > > >