Intel 82574L Gigabit Ethernet Controller

[Shtorm]

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 <kern.crit> server kernel: em0: Watchdog timeout -- resetting
> [..]
>  > Jul  8 07:23:56 <ntp.crit> server ntpd[3687]: 2 out of 3 peers valid
>  > Jul  8 07:23:56 <ntp.crit> server ntpd[3687]: bad peer from pool pool.ntp.org (195.214.215.17)
>  > Jul  8 07:27:15 <kern.crit> server kernel: em0: Watchdog timeout -- resetting
> 
> Ignore if not relevant.
> 
> cheers, Ian
> _______________________________________________
> freebsd-net at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe at 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.