AnsweredAssumed Answered

SRIO: SDK 1.6 gives RIO: inbound message copy failed, no buffers error

Question asked by Ajay Joshi on May 29, 2016
Latest reply on Jun 16, 2016 by Ajay Joshi

Hi,

We have two P4080ds boards connected via a SRIO switch. We can see that the connection between two boards is fine. The ping also works fine, but when we run iperf with heavy load, then we see the following messages "RIO: inbound message copy failed, no buffers error". We tried increased the CONFIG_RIONET_TX_SIZE and CONFIG_RIONET_RX_SIZE to 1024. But still see these errors after repeated testing.

-------------------------------------------------------------

fsl-of-rio ffe0c0000.rapidio: bellirq: 57

fsl-of-rio ffe0c0000.rapidio: pwirq: 478

fsl-of-rio ffe0c0000.rapidio: /rapidio@ffe0c0000/port1: LAW start 0x0000000c20000000, size 0x0000000010000000.

fsl-of-rio ffe0c0000.rapidio: RapidIO PHY type: Serial

fsl-of-rio ffe0c0000.rapidio: Hardware port width: 4

fsl-of-rio ffe0c0000.rapidio: Training connection status: Four-lane

fsl-of-rio ffe0c0000.rapidio: RapidIO Common Transport System size: 256

/soc@ffe000000/rmu@d3000/message-unit@0: txirq: 60, rxirq 61

fsl-of-rio ffe0c0000.rapidio: /rapidio@ffe0c0000/port2: LAW start 0x0000000c30000000, size 0x0000000010000000.

fsl-of-rio ffe0c0000.rapidio: RapidIO PHY type: Serial

 

-------------------------------------------------------------------

 

iperf -s ==> on one board, while client on another board.

 

[ 67] local 13.0.0.8 port 5001 connected with 13.0.0.7 port 46385

RIO: inbound message copy failed, no buffers

RIO: inbound message copy failed, no buffers

RIO: inbound message copy failed, no buffers

RIO: inbound message copy failed, no buffers

RIO: inbound message copy failed, no buffers

RIO: inbound message copy failed, no buffers

 

Any inputs on the same will be appreciated ...

 

Regards,

Ajay

Outcomes