Am 08.02.2014 18:01, schrieb Ajith Whowe:
Dear Martin,
These commands indicate that the link is always down with the
"NO-CARRIER“ flag. Please kindly refer to the outputs given below.
This flag is set by the function „update_carrier“, which checks 3
conditions, namely the i) priv->remote_attached ii)
l4shmc_is_chunk_ready(&priv->tx_chunk) iii)
l4shmc_is_chunk_ready(&priv->rx_chunk). Unfortunately the problem is
originated at check point "l4shmc_is_chunk_ready". This function
returns 0, the if clause fails and sets the link down.
the chunk_ready reflects the state of the link which seems to be down.
I just removed this check point from the if clause, set the link_up
to 1 and observed that the ping request showed that the
l4x_l4shmc_xmit_frame function is called. Nevertheless still no
answer back from the second instance.
This won't help if the link is down, so no packets will traverse the shmnet.
What can be the main reason for the l4x_l4shmc_xmit_frame to return
0?
Best Regards and many Thanks in Advance,
The result for the „ip addr show“ is as follows:
XXXXX - XXXX: Inside l4x_l4shmc_get_stats function - start 1: lo:
<LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue link/loopback
00:00:00:00:00:00 brd 00:00:00:00:00:00 inet127.0.0.1/8
<http://127.0.0.1/8> scope host lo 2: eth0:
<NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen
1000 link/ether 52:54:00:b0:cf:02 brd ff:ff:ff:ff:ff:ff
inet192.168.124.116/24 <http://192.168.124.116/24> scope global
eth0 inet192.168.0.5/24 <http://192.168.0.5/24> scope global
eth0:0
The result for the „ip link show“ is as follows:
XXXXX - XXXX: Inside l4x_l4shmc_get_stats function - start 1: lo:
<LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue link/loopback
00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0:
<NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen
1000 link/ether 52:54:00:b0:cf:02 brd ff:ff:ff:ff:ff:ff
So at first you should bring up the link by "ip link set eth0 up" on
both partitions.
Best regards,
Martin
_______________________________________________
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
