Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
BroadcastCommunity.qnx.com will be offline from May 31 6:00pm until June 2 12:00AM for upcoming system upgrades. For more information please go to https://community.qnx.com/sf/discussion/do/listPosts/projects.bazaar/discussion.bazaar.topc28418
Forum Topic - Network Lockup with ftp: Page 1 of 7 (7 Items)
   
Network Lockup with ftp  
I get an odd lock up on my imx31ads target when I try to ftp a particular binary onto its file system.  The system 
becomes unresponsive.  I can’t execute any commands through a high prio shell and networking is completely blocked.  I 
am having a hard time debugging what is going on since I can’t get any useful information from my target.  No cores are
 being produced so I assume its just a kernel lockup.   Here is an example of what happens.

Here is a pidin before I actually send the file.  My ksh is running at 80 and you can see the ftp daemon running at 10.
imx31ads-3480# pidin
     pid tid name               prio STATE       Blocked
       1   1 oc/boot/procnto-v6   0f READY
       1   2 oc/boot/procnto-v6 255r RECEIVE     1
       1   3 oc/boot/procnto-v6 255r RECEIVE     1
       1   5 oc/boot/procnto-v6 255r RECEIVE     1
       1   6 oc/boot/procnto-v6  10r RECEIVE     1
       1   7 oc/boot/procnto-v6  10r RECEIVE     1
       1   8 oc/boot/procnto-v6  10r RECEIVE     1
       1   9 oc/boot/procnto-v6  80r RECEIVE     1
       1  10 oc/boot/procnto-v6  10r RECEIVE     1
       1  11 oc/boot/procnto-v6  10r RECEIVE     1
       1  12 oc/boot/procnto-v6  80r RUNNING
       1  13 oc/boot/procnto-v6  80r RECEIVE     1
       2   1 c/boot/devc-sermx1  24r READY
       3   1 proc/boot/slogger   10r RECEIVE     1
       4   1 proc/boot/io-pkt    21r SIGWAITINFO
       4   2 proc/boot/io-pkt    21r READY
       4   3 proc/boot/io-pkt    21r RECEIVE     15
   16389   1 proc/boot/fs-nfs2   10r RECEIVE     1
   16389   2 proc/boot/fs-nfs2   80r RECEIVE     1
   16389   3 proc/boot/fs-nfs2   80r RECEIVE     1
   16389   4 proc/boot/fs-nfs2   10r RECEIVE     1
   16389   5 proc/boot/fs-nfs2   10r RECEIVE     1
   20486   1 proc/boot/fs-nfs2   10r RECEIVE     1
   20486   2 proc/boot/fs-nfs2   10r RECEIVE     1
   20486   3 proc/boot/fs-nfs2   10r RECEIVE     1
   20486   4 proc/boot/fs-nfs2   10r RECEIVE     1
   20486   5 proc/boot/fs-nfs2   80r RECEIVE     1
   24583   1 usr/sbin/dumper     10r RECEIVE     1
   24584   1 usr/bin/portmap     10r SIGWAITINFO
   24586   1 sbin/devc-pty       10r RECEIVE     1
   24587   1 usr/sbin/inetd      10r SIGWAITINFO
   28681   1 usr/sbin/qconn      10r SIGWAITINFO
   28681   2 usr/sbin/qconn      10r CONDVAR     (0x1247a8)
   28681   3 usr/sbin/qconn      10r RECEIVE     1
   28681   4 usr/sbin/qconn      10r RECEIVE     3
   45069   1 sbin/pipe           10r SIGWAITINFO
   45069   2 sbin/pipe           10r RECEIVE     1
   45069   3 sbin/pipe           80r RECEIVE     1
   45069   4 sbin/pipe           10r RECEIVE     1
   57358   1 sbin/devc-pty       10r RECEIVE     1
   65551   1 sbin/mq             10r RECEIVE     1
   81936   1 sbin/mqueue         10r RECEIVE     1
  106508   1 bin/ksh             80r SIGSUSPEND
  151569   1 usr/sbin/ftpd       10r REPLY       4
  155666   1 bin/pidin           80r REPLY       1

From my Neutrino host I send the binary and back in my shell I try to execute pidin to see what’s happening and this is
 what I see after about 2 mins of waiting for a prompt.
imx31ads-3480# pidin
ksh: pidin: cannot execute - Host is down
imx31ads-3480#

My host Neutrino/linux 642 M2
My target imx31ads 642M2

Any suggestions for fixing / debugging this issue? 
Attachment: Text memset-chk.x4 80.81 KB