On Wed, Apr 18, 2012 at 1:45 PM, Lars Wilke <l...@lwilke.de> wrote: > Hi Jack, > > thanks for your response. > > * Jack Vogel wrote: > > On Wed, Apr 18, 2012 at 7:01 AM, Lars Wilke <l...@lwilke.de> wrote: > > > Apr 13 08:53:07 san02 kernel: em1: Watchdog timeout -- resetting > > > Apr 13 08:53:07 san02 kernel: em1: Queue(0) tdh = 232, hw tdt = 190 > > > Apr 13 08:53:07 san02 kernel: em1: TX(0) desc avail = 31,Next TX to > > > Clean = 221 > > > Apr 13 08:53:07 san02 kernel: em1: Link is Down > > > Apr 13 08:53:07 san02 kernel: em1: link state changed to DOWN > > > > > > Sometimes nothing for days, sometimes under high Network load (NFSv3), > > > sometimes > > > multiple times a day. I see this message/behaviour on always the same > two > > > of the > > > four interfaces (em1 and em3). > > > > > > Then the NIC does not have the ACTIVE flag anymore, an ifconfig em1 up > > > solves the issue. But why does it loose the ACTIVE state and why does > the > > > NIC reset itself in the first place? > > > > > > > Because a watchdog reset is just that, a reset, so it causes the > hardware to > > reinitialize. It should come back up, I do not know why it did not, > maybe > > the renegotiation with the switch fails for some reason? > > Hm, my main problem is that it did a reset in the first place. > > > One thought is to get the latest em driver and see if the behavior > changes, > > if that driver is the distributed 8.2 its pretty old. > > ok then i guess i will upgrade to 8.3-R, is the driver there reasonably > new? > > Yes, that should be fine.
Jack _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
