Date: Wed, 1 Mar 2006 17:42:06 +0000 From: Chris Howells <howells@kde.org> To: Gleb Smirnoff <glebius@freebsd.org>, Jack Vogel <jfvogel@gmail.com>, freebsd-net@freebsd.org Subject: Re: Which motherboards work well with em(4)? Message-ID: <200603011742.07429.howells@kde.org> In-Reply-To: <20060226103244.GF55275@FreeBSD.org> References: <63472.192.168.0.1.1140456976.squirrel@webmail.devrandom.org.uk> <57314.192.168.0.1.1140522671.squirrel@webmail.devrandom.org.uk> <20060226103244.GF55275@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 26 February 2006 10:32, Gleb Smirnoff wrote: > On Tue, Feb 21, 2006 at 11:51:11AM -0000, Chris Howells wrote: > C> Oh yes sorry, should have clarified that. Correct, it hangs on receive, > C> consistently -- never ever on transmit. Though the conditions to cause > it C> to hang on rx are sadly somewhat unpredictable. I haven't seen the > problem C> really since before Christmas until recently when I've seen it > quite a C> lot. But then again I am transferring more data around at the > moment due C> to trying to recover from a hard disk failure in the 6.1-pre > machine. > > Can you please try the following, when the card wedges again: > > sysctl dev.dev.em.0.stats=1 > > Then show us the last part of the dmesg output. Sorry for the delay in replying. I think this is it: em0: link state changed to UP em0: Excessive collisions = 0 em0: Symbol errors = 0 em0: Sequence errors = 0 em0: Defer count = 5622 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: XON Rcvd = 6209 em0: XON Xmtd = 0 em0: XOFF Rcvd = 21561 em0: XOFF Xmtd = 0 em0: Good Packets Rcvd = 1419602 em0: Good Packets Xmtd = 1631954 em0: Adapter hardware address = 0xc17d9924 em0:CTRL = 0x18f00249 em0:RCTL = 0x8002 PS=(0x8402) 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 = 0 em0: hw tdh = 0, hw tdt = 0 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 I am starting to become convinced that it is the motherboard though, I have tried the card in a Nforce3 (Asus A8n) and Nforce4 (Asus A8n-SLI) board and been unable to reproduce the problelm Thanks. -- Cheers, Chris Howells -- chris@chrishowells.co.uk, howells@kde.org Web: http://chrishowells.co.uk, PGP ID: 0x33795A2C KDE/Qt/C++/PHP Developer: http://www.kde.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200603011742.07429.howells>