Forwarded from a collaborator that's cc'd:
Hi All,
I'm wondering if anyone knows the reason for the following telnet error
that results from using the tap-start function to configure 1GbE parameters
in a Roach2 design.
To configure the 1GbE block, I send:
?tap-start tap0 one_GbE2 192.168.41.1 60000 02:02:0A:00:00:14 1.1.1.1
where the arguments are: dev name, register, IP, fabric port, MAC, gateway
After sending, telnet returns the 'tap-start is OK' message, then enters
into an endless stream of:
#log warn 183324 raw tx\_queue\_still\_busy\_(8\_words\_to\_send)
Meanwhile, the network configuration in the PPC shows that tap0 has been
created, and the UDP frame contains the settings that I chose:
Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.41.1 P-t-P:192.168.41.1 Mask:255.255.255.0
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Although I can still communicate with the Roach, it's definitely lagging as
a result of whatever is happening with the transfer queue.
Any insight would be appreciated,
Sam Gordon
Brad Dober
Ph.D. Candidate
Department of Physics and Astronomy
University of Pennsylvania
Cell: 262-949-4668
