On Sun, 19 Apr 2009, Andrey Luzgin wrote: > We have repeating problems on several servers with different versions of > the driver e1000e with kernel 2.6.28.9 (this version because of tproxy > is necessary to us). All servers is Intel® Server Systems SR1560SF with > one additional NIC 82572EI Gigabit Ethernet Controller. Enabled ioatdma. > > This is last log from server with e1000e version: 0.5.18.3-NAPI > > Apr 19 21:03:47 R2PX1 [188890.816082] 0000:06:00.0: eth1: Detected Tx > Unit Hang: > Apr 19 21:03:47 R2PX1 [188890.816083] TDH <a39> > Apr 19 21:03:47 R2PX1 [188890.816084] TDT <a25> > Apr 19 21:03:47 R2PX1 [188890.816085] next_to_use <a25> > Apr 19 21:03:47 R2PX1 [188890.816086] next_to_clean <a38> > Apr 19 21:03:47 R2PX1 [188890.816086] buffer_info[next_to_clean]: > Apr 19 21:03:47 R2PX1 [188890.816087] time_stamp <102cf691d> > Apr 19 21:03:47 R2PX1 [188890.816088] next_to_watch <a3b> > Apr 19 21:03:47 R2PX1 [188890.816088] jiffies <102cf6ab8> > Apr 19 21:03:47 R2PX1 [188890.816089] next_to_watch.status <0> > Apr 19 21:03:49 R2PX1 [188892.816132] 0000:06:00.0: eth1: Detected Tx > Unit Hang:
so is it the 82572EI that is having problems? or the ESB2 ports (LOM)? what kind of traffic are you running? And why do you have the TxDescriptor count set so high? I'm wondering if you're running with the (ill advised) setting that someone once posted to a debian mailing list long ago. Please include dmesg from boot through the network coming up. Also please attach the ethtool -e ethX eeprom dump from any ports that are having tx hangs. Also, please post the BIOS and BMC firmware versions. If you have modified the RxAbsIntDelay or RxIntDelay parameters at load, then you've likely ran into a hardware errata that can be avoided by not modifying those parameters. > Apr 19 16:47:37 R2PX3 [272540.768103] 0000:06:00.1: eth2: Detected Tx > Unit Hang: > Apr 19 16:49:31 R2PX3 [272654.768142] 0000:06:00.1: eth2: Detected Tx > Unit Hang: ugh, seems like your data pattern makes the hang repeat every two minutes. Well thats good in that it is at least reproducable. Can you try going back to the default driver settings and see if that makes any difference? ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
