Guys,
The issue was resolved by increasing memory at remote end. 2GB to 4GB.
Now it is failing in completing the session.
---------------------------------------------------------------------------
==================End /etc/system =========================
SUMMARY:
=================================================
SUT : 22.1.1.169
CLIENTS : 22.1.1.167
SOCKET_BUFFER: 65535
MESSAGE_SIZE : 65000
PROTOCOL_TYPE: TCP_STREAM
TCP_NODELAY : 0
TRAFFIC_TYPE : bi
# OF CARDS : 1
PORT PER CARD: 1
TOTAL_SESSION: 2000
timeout_short: 1800
THROUGH_PUT TCP TX : 154.80 mbits/s
RX : 849.92 mbits/s
BI : 1004.72 mbits/s
Finished 1960 out of 2000 sessions: failed
------------------------------------------------
print all of netperf log on 22.1.1.167
TCP STREAM TEST from ::ffff:0.0.0.0 (0.0.0.0) port 0 AF_INET to
::ffff:22.1.1.169 (22.1.1.169) port 0 AF_INET
Recv Send Send
Socket Socket Message Elapsed
Size Size Size Time Throughput
bytes bytes bytes secs. 10^6bits/sec
---------------------------------------------------------------------------
The above log is from igb LOM.
Any clue.
regards,
~Su
On Tue, May 4, 2010 at 1:33 PM, Reang Su <[email protected]> wrote:
> Robin,
>
> There is no chip reset on NIC. At the same time where Tx stalls, Rx is
> working fine. Snoop was able to capture ICMP packets received from SUT.
>
> regards,
> ~Su.
>
>
> On Tue, May 4, 2010 at 11:57 AM, tian robin luo <[email protected]> wrote:
>
>> Whether your NIC driver was hang during the test? Do you find any chip
>> reset event?
>>
>> Regards,
>> Robin
>>
>> Reang Su:
>>
>> Hi All,
>>
>> Anybody had a chance to clear netstress recently on latest source, B138
>> above.
>> I'm experiencing strange issue. After 8 hr or so Tx stalls on remote,
>> whreas Rx works fine.
>>
>> On putting remote interface through snoop, I don't see any packet reaching
>> snoop (i.e no packets from stack to driver on ping). System is up and driver
>> stats also looks ok.
>>
>> Any clue.
>>
>> regards,
>> ~Su
>>
>> ------------------------------
>>
>> _______________________________________________
>> driver-discuss mailing
>> [email protected]http://mail.opensolaris.org/mailman/listinfo/driver-discuss
>>
>>
>>
>
_______________________________________________
networking-discuss mailing list
[email protected]
