Date: Thu, 27 Jul 2006 09:53:27 +0900 From: Pyun YongHyeon <pyunyh@gmail.com> To: Jeremie Le Hen <jeremie@le-hen.org> Cc: freebsd-current@freebsd.org, Jack Vogel <jfvogel@gmail.com> Subject: Re: [fbsd] Re: em(4) watchdog timeout Message-ID: <20060727005326.GA19286@cdnetworks.co.kr> In-Reply-To: <20060725123603.GH6253@obiwan.tataz.chchile.org> References: <20060721123448.GV6253@obiwan.tataz.chchile.org> <2a41acea0607210927s108d1326qdad02b7d29376a09@mail.gmail.com> <20060725123603.GH6253@obiwan.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 25, 2006 at 02:36:03PM +0200, Jeremie Le Hen wrote: > On Fri, Jul 21, 2006 at 09:27:31AM -0700, Jack Vogel wrote: > > hitting watchdog means you have a hang of some sort. > > try 'sysctl dev.em.0.debug_info=1' and see if that gives any clues. > > dev.em.0.debug_info: > % em0: Adapter hardware address = 0xc2a32130 > % em0: CTRL = 0x18f00241 RCTL = 0x801a > % em0: Packet buffer = Tx=16k Rx=48k > % em0: Flow control watermarks high = 47104 low = 45604 > % em0: tx_int_delay = 66, tx_abs_int_delay = 66 > % em0: rx_int_delay = 0, rx_abs_int_delay = 66 > % em0: fifo workaround = 0, fifo_reset_count = 0 > % em0: hw tdh = 149, hw tdt = 149 > % em0: Num Tx descriptors avail = 256 > % em0: Tx Descriptors not avail1 = 0 > % em0: Tx Descriptors not avail2 = 0 > % em0: Std mbuf failed = 0 > % em0: Std mbuf cluster failed = 0 > % em0: Driver dropped packets = 0 > > dev.em.0.stats: > % em0: Excessive collisions = 0 > % em0: Symbol errors = 0 > % em0: Sequence errors = 0 > % em0: Defer count = 0 > % em0: Missed Packets = 0 > % em0: Receive No Buffers = 0 > % em0: Receive length errors = 0 > % em0: Receive errors = 0 > % em0: Crc errors = 0 > % em0: Alignment errors = 0 > % em0: Carrier extension errors = 0 > % em0: RX overruns = 0 > % em0: watchdog timeouts = 6 > % em0: XON Rcvd = 0 > % em0: XON Xmtd = 0 > % em0: XOFF Rcvd = 0 > % em0: XOFF Xmtd = 0 > % em0: Good Packets Rcvd = 3720143 > % em0: Good Packets Xmtd = 1246413 > > Most of provided debugging informations are meaningless for me. > Is any minded soul able to understand this ? > I think the debug_info is useless as it's the output after hardware reset. Would you try latest em(4) in CURRENT? I've fixed a DMA related bug. Not sure it helps. -- Regards, Pyun YongHyeon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060727005326.GA19286>