Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - io-pkt-v4 termination with SIGSEGV with QNX 6.4.0 and MPC8360-BSP: (1 Item)
   
io-pkt-v4 termination with SIGSEGV with QNX 6.4.0 and MPC8360-BSP  
Hi QNX community,

we are using a board where the MPC8360 is connected with the Marvell PHYs as in the Freescale reference board MPC8360MDS
.
SW-Development with QNX Momentics Version 4.5 (qnxsdp-6.4.0-200810211530-win32.exe)
We included the BSP bsp-nto640-freescale-mpc8360e-mds-trunk.zip with minor changes to adapt to our hardware.
The 2 network interfaces are started with

io-pkt-v4 -v -d ucc_ec-mds mac=zzzzzzzzzz,channel=1,mode=RGMII,phy=0
waitfor /dev/io-net/en0
mount -Tio-net -o mac=zzzzzzzzzz,channel=2,phy=1,mode=RGMII /proc/boot/devn-ucc_ec-mds.so
waitfor /dev/io-net/en1
ifconfig en0 192.168.91.181 netmask 255.255.255.0
ifconfig en1 192.168.92.181 netmask 255.255.255.0

Both interfaces are working well, connections to QCONN are possible.

If connected to a bigger Ethernet network with several CPUs, the io-pkt-v4 process is terminated after minutes or after 
hours with the following message on stdout:

Shutdown[0,0] S/C/F=10/3/33 C/D=00029098/00092bb8
QNX Version 6.4.0 Release 2008/10/21-10:59:55EDT
[0]PID-TID=24581-2  P/T FL=00401010/84000000 "proc/boot/io-pkt-v4"
ppcbe context[007f565c]:
0000: 60050002 47fbeea0 480d5348 47fbefc0 00000000 480f7e80 00000001 00000000
0020: 00000000 00000000 00b20bfa 480d6adc 48089ef0 480d96c4 00000000 00000000
0040: 00000000 00000000 00000000 00000000 480d0000 480fbb20 480fbb1c 006cb020
0060: 480f7e80 0000005a 480f0a40 00000800 48123020 480d0000 480d6ad8 480d6ad8
0080: 48089ed8 48089ef0 00049930 48089efc 42000042 00000000 00000000 00000000
00a0: 00000000
instruction[48089efc]:
7c 00 04 ac 7d 40 58 28 7c 0a 48 00 40 82 00 10 7c 00 5a 2c 7c 00 59 2d 40 a2 
stack[47fbeea0]:
0000: 47fbeeb0 00000103 480f7e80 480d6414 47fbeef0 4805e3fc 480f0a40 00000001
0020: 47fbeed0 480d0000 481b8400 480d82d0 47fbeef0 4809f028 48123020 0000005a
0040: 4805dd4c 48114e8c fe38a9f8 481b8400 47fbef20 fe386274 480f0a40 00000001
0060: 480d0000 480d0000 00000001 480d6ad8 480d6a34 48114e90 480f0a40 fe386104

A core-dump of the process gives with coredump the following printout:
...
thread 2 SIGNALLED-SIGSEGV code=2 ACCERR refaddr=7e568 fltno=5
  ip=0x7e568 sp=0x7edfa0 stkbase=0x47f9e000 stksize=135168
  state=STOPPED flags=84000000 last_cpu=1 timeout=00000000
  pri=21 realpri=21 policy=RR
...

Can anyone give me a hint why the error occured ? 
Can this termination referenced to a function call of a specific io-net function or a function call of the ucc_ec driver
 registered functions ? 
Unfortinally I have neither a gdb debugger running on a PowerPc nor the source code of the io-pkt-v4 to get closer to 
the reason of this error.
Attachment: Compressed file io-pkt-v4_termination.zip 1.61 MB