Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - io-pkt-v6-hc.core: (3 Items)
   
io-pkt-v6-hc.core  
I am running io-pkt-v6-hc on a PPC460.  A memory fault (core dump) was detected by my verification engineer on our board
.  I have run gdb on the corefile (no symbols).  Can someone tell me if the trace information:

a. iis ndicative of a problem that happened while initializing io-pkt or the shim layer.
b. is a known problem with a knonw work-around or fix.

I'd also like to know the root cause of the problem if possible.

Thanks.  Here is the gdb output:


moman@cesium:~/workspace/debug$ 
moman@cesium:~/workspace/debug$ ./ntoppc-gdb ./io-pkt-v6-hc ./io-pkt-v6-hc.core
GNU gdb 6.8 qnx-nto (rev. 347)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu
--target=powerpc-unknown-nto-qnx6.4.0"...
(no debugging symbols found)
Reading symbols from /mnt/workspace/debug/libc.so.3...(no debugging symbols
found)...done.
Loaded symbols for libc.so.3
Reading symbols from /mnt/workspace/debug/devnp-shim.so...(no debugging symbols
found)...done.
Loaded symbols for devnp-shim.so
Reading symbols from /mnt/workspace/debug/devn-comm300-ep460c.so...(no
debugging symbols found)...done.
Loaded symbols for devn-comm300-ep460c.so
Program terminated with signal 11, Segmentation fault.
[New process 458782 thread 1]
[New process 458782 thread 2]
#0  0x480f4e9c in segv_handler ()
(gdb) bt
#0  0x480f4e9c in segv_handler ()
#1  <signal handler called>
#2  0xfe388ac8 in UseFreeEntry () from devnp-shim.so
#3  0xfe388d44 in MemchunkMalloc () from devnp-shim.so
#4  0xfe3883fc in ex_alloc () from devnp-shim.so
#5  0xfe3950a4 in ppc405_alloc_npkt () from devn-comm300-ep460c.so
#6  0xfe396820 in ppc405_send_packets () from devn-comm300-ep460c.so
#7  0xfe389f70 in shim_start () from devnp-shim.so
#8  0x4808cea8 in ifq_enqueue_wtp ()
#9  0x48097ffc in ether_output ()
#10 0x480da0dc in ip_output ()
#11 0x48127274 in tcp_output ()
#12 0x481255a0 in tcp_input ()
#13 0x480d32fc in ip_input ()
#14 0x480d339c in ip_intr ()
#15 0x4810ff44 in process_pkts ()
#16 0x4811086c in receive_loop_uni ()
#17 0x48102294 in thread_init ()
#18 0xfe3206b4 in timer_settime () from libc.so.3
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)
Attachment: Text io-pkt-v6-hc.core 112 KB
Re: io-pkt-v6-hc.core  
This isn't an init time issue, it's whilst running data.

There was a TCP packet received that triggered the output of a TCP packet (e.g. received an ACK and send outstanding 
data, received data and sending a delayed ACK etc.). When going to send the packet the devn driver has requested memory 
from the shim layer and it crashed when trying to give that memory to the devn driver.

The memory it is handing back is something that has been previously freed, I would be suspicious that maybe what was put
 on the free list wasn't actually what was allocated before and maybe check the devn driver in detail.
Re: io-pkt-v6-hc.core  
Thanks for the analysis.