network problems on microblaze

What steps will reproduce the problem?
1.r14530, microblaze/qemu
2.
3.

What is the expected output? What do you see instead?
$ ./scripts/qemu/auto_qemu 
Guessed AUTOQEMU_ARCH is: microblaze
Guessed AUTOQEMU_MEM is: 16
Guessed AUTOQEMU_NICS is: xemaclite
Guessed AUTOQEMU_KVM_ARG is:
Guessed AUTOQEMU_LOAD_ARG is: -kernel ./build/base/bin/embox
Guessed AUTOQEMU_NOGRAPHIC_ARG is: -nographic
sudo qemu-system-microblaze -M petalogix-s3adsp1800 -kernel 
./build/base/bin/embox -m 16 -net 
nic,model=xlnx.xps-ethernetlite,macaddr=AA:BB:CC:DD:EE:02 -net 
tap,script=./scripts/qemu/start_script,downscript=./scripts/qemu/stop_script 
-nographic
ioctl(TUNSETIFF): Device or resource busy
Enable IP Forwarding for eth0
net.ipv4.ip_forward = 1

Embox kernel start
runlevel: init level is 0
    unit: initializing embox.driver.interrupt.mb_intc: done
    unit: initializing embox.kernel.task.task_resource: done
    unit: initializing embox.kernel.task.task_table: done
    unit: initializing embox.driver.clock.mb_timer: done
    unit: initializing embox.kernel.task.kernel_task: done
    unit: initializing embox.kernel.time.jiffies: done
    unit: initializing embox.kernel.thread.starter: done
    unit: initializing embox.mem.static_heap: done
    unit: initializing embox.kernel.time.timer: done
    unit: initializing embox.kernel.time.kernel_time: done
    test: running embox.test.stdlib.setjmp_test . done
    test: running embox.test.kernel.thread.thread_priority_test . done
    test: running embox.test.mem.pool_test ...... done
    test: running embox.test.math.math_test .. done
    test: running embox.test.util.slist_test .................. done
    test: running embox.test.util.list_test ........................................................... done
    test: running embox.test.util.bit_test ..... done
    test: running embox.test.util.array_test . done
    test: running embox.test.stdlib.qsort_test ....... done
    test: running embox.test.stdlib.bsearch_test ...... done
    test: running embox.test.posix.sleep_test ...... done
    test: running embox.test.recursion . done
    test: running embox.test.kernel.timer_test .. done
    test: running embox.test.kernel.softirq_test ..... done
    test: running embox.test.framework.mod.member.ops_test . done
    test: running embox.test.hal.context_switch_test . done
    test: running embox.test.gcc.int_arithmetic ......... done
    test: running embox.test.critical .. done
runlevel: init level is 1
    unit: initializing embox.kernel.time.timekeeper: done
    unit: initializing embox.fs.driver.repo: done
    unit: initializing embox.fs.node: done
    unit: initializing embox.net.dev: done
    unit: initializing embox.net.tcp: done
    unit: initializing embox.net.neighbour: done
    unit: initializing embox.net.net_entry: done
    unit: initializing embox.cmd.shell: done
    unit: initializing embox.driver.net.loopback: done
    unit: initializing embox.driver.net.xemaclite: done
runlevel: init level is 2
    unit: initializing embox.init.start_script: 
Started shell [] on device []
loading start script:
> ifconfig lo 127.0.0.1 netmask 255.0.0.0 up 
> route add 127.0.0.0 netmask 255.0.0.0 lo 
> ifconfig eth0 10.0.2.16 netmask 255.255.255.0 hw ether AA:BB:CC:DD:EE:02 up 
> route add 10.0.2.0 netmask 255.255.255.0 eth0 
> route add default gw 10.0.2.10 eth0 

Welcome to Embox and have a lot of fun!
embox>telnetd 
qemu: fatal: fetching nop sequence

IN: PC=154 
rmsr=800000a4 resr=53535353 rear=53535353 debug=0 imm=154 iflags=0 fsr=13
btaken=1 btarget=154 mode=kernel(saved=kernel) eip=0 ie=0
r00=00000000 r01=900ffed8 r02=53535353 r03=00000015 
r04=00000008 r05=00000003 r06=00000001 r07=900fff38 
r08=00000800 r09=00000010 r10=9018eb98 r11=900f54f4 
r12=900f54e4 r13=53535353 r14=900002a0 r15=90000354 
r16=53535353 r17=53535353 r18=00000000 r19=900ffed8 
r20=53535353 r21=53535353 r22=902b89f0 r23=00000002 
r24=53535353 r25=53535353 r26=53535353 r27=53535353 
r28=53535353 r29=53535353 r30=53535353 r31=00000000 

Please use labels and text to provide additional information.
Original issue reported on code.google.com by ki.stfu on 6 Aug 2014 at 12:39
kayws426 / embox

network problems on microblaze #699
