Ron, Carsten's first explanation is correct. If you see tx_errors on a HiperSockets interface, it usually means transmission of a packet fails because the receiver has currently no free receive buffer. You should verify first if the receiver has configured the maximum of 128 buffers (sysfs attribute buffer_count) for his HiperSockets device. 128 is nowadays the default, but older qeth driver versions run with a default of 16. If you see the tx_errors even though your receiver runs already with the maximum of 128 buffers, you either have to live with the autotuning mechanisms of tcp or you take actions to slow down the sender or to accelerate the receiver.
As Alan suggested we can document this in the Device Driver book. The other option would be to change the current behavior of the qeth driver and increase probably both the tx_dropped and the tx_error counter. It is definitely not a problem to report to SuSe folks. Kind regards, Ursula Braun, Linux on System z development, IBM Germany On Thu, 2013-07-25 at 13:18 +0000, Ron Foster wrote: > Carsten, > > Do you know where I would start looking for causes of the transmit errors on > Hipersockets? > > The error is occurring on SLES11 SP2 systems. We are not having it on our > SLES10 SP4 systems. > > Do I need to open a problem with the SuSe folks? > > Thanks, > > Ron Foster > > Baldor Electric Company > > 5711 R S Boreham Jr Street > > Fort Smith, AR 72901 > > Phone:479-648-5865 > > Fax:479-646-5440 > > Email: ron.fos...@baldor.abb.com > > IM Address:rfos...@baldor.com > > www.baldor.com > > > > ________________________________________ > From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Carsten Otte > [co...@de.ibm.com] > Sent: Thursday, July 25, 2013 7:53 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: TX-Errs on hipersocket interface. > > Alan wrote: > >Carsten, this is information that really needs to be in the Device Driver > >book, as it differs from the traditional interpretation of TX/RX counters. > Ah, you're right - that would be accouned as dropped, not TX error. Forget > about my > reply then, time to look at other causes for that TX error. Sorry for the > noise. > > with kind regards > Carsten Otte > System z firmware development / Boeblingen lab > --- > Every revolution was first a thought in one man's mind; > and when the same thought occurs to another man, it is the key to that era. > > - Ralph Waldo Emerson, Essays: First Series, 1841 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
