Date: Tue, 9 Nov 2010 11:24:19 -0800 From: Pyun YongHyeon <pyunyh@gmail.com> To: M?rcio Luciano Donada <mdonada@auroraalimentos.com.br> Cc: freebsd-stable@freebsd.org Subject: Re: watchdog Message-ID: <20101109192419.GB7766@michelle.cdnetworks.com> In-Reply-To: <4CD92E25.7060304@auroraalimentos.com.br> References: <4CD92E25.7060304@auroraalimentos.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 09, 2010 at 09:19:01AM -0200, M?rcio Luciano Donada wrote: > Hi list, > > I'm using FreeBSD (uname is below) and these days I'm caught in the log > message below: > > vpn# uname -a > FreeBSD vpn.auroraalimentos.com.br 7.3-STABLE FreeBSD 7.3-STABLE #0: Sat > Jun 19 18:39:18 BRT 2010 > root@vpn.xxx.com.br:/usr/obj/usr/src/sys/VPN i386 > > Nov 8 11:53:55 vpn kernel: xl0: watchdog timeout (missed Tx interrupts) > -- recovering > Nov 8 12:01:21 vpn kernel: xl0: watchdog timeout (missed Tx interrupts) > -- recovering > Nov 8 12:21:55 vpn kernel: xl0: watchdog timeout (missed Tx interrupts) > -- recovering > Nov 8 16:11:34 vpn kernel: xl0: watchdog timeout (missed Tx interrupts) > -- recovering > > it is possible that the network interface (xl0) is in trouble? > If my memory serve me right there were a couple of reports about xl(4) watchdog timeout in past. The message was added by me to track down possible cause of watchdog timeouts. The message means driver lost Tx completion interrupts but driver noticed that the queued frames were successfully transmitted such that it didn't reset the controller and showed the informational message. To further narrow down the issue, would you show me the following information? o full 'dmesg' output o 'pciconf -lcbv' output o 'devinfo -rv | grep phy' output
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101109192419.GB7766>