<div dir="ltr"><div><div>Dear All,<br><br></div>We are trying to set up the tracing module bfscope and facing an issue.<br><br></div><div>It is waiting forever for e1000_ARP when the function nameservice_blocking_lookup() is called through idc_connect_ARP_lookup_service() while running bfscope. Following are the traces:<br></div><br>spawnd.0: spawning /x86_64/sbin/bfscope on core 0<br>bfscope running on core 0<br>bfscope: trying to connect to the e1000 driver...<br>lwip_init_ex: starting......................<br>LWIP_other: Inside lwip_init<br>#### bfscope Going ahead with default wait-set<br>LWIP: lwip_init: done with sanity check<br>LWIP: done with sanity check<br>idc_c_port_mng_srv: trying to [e1000_PORTS_MNG]<br>init_net_ports_connection: called<br>init_net_ports_connection: connecting to [e1000_PORTS_MNG]<br>init_net_ports_connection: resolving driver e1000_PORTS_MNG<br>init_net_ports_connection: terminated<br>idc_c_port_mng_srv: success [e1000_PORTS_MNG]<br>LWIP: ctl 0<br>init_net_ARP_connection: called e1000_ARP<br>init_net_ARP_connection: resolving driver e1000_ARP<br><b>skb.0: waiting for: e1000_ARP</b><br><br><div>I looked into the code of the file lib/lwip/src/barrelfish/ARP_lookup_client.c and
there is a FIXME me note "decide if this is the best place to connect
with net_ARP" in the function idc_connect_ARP_lookup_service.<br><br></div><div>Could this be a potential cause for the block? <br>If it is not kindly give us some insights as to where we have gone wrong.<br></div><div><br><b>Set Up:</b><br><br>We have and Intel 82576 and we are using e1000 as the cardname. We have
both NKGDM and netd modules up as you can find in the attached log
trace.<br><br>Also please find the menu.lst we used to boot for your perusal.<br><br>Your help is highly appreciated.<br><br></div>Thanks and Regards,<br>Akshay</div>