FW: TCP/IP "receive 3" panic

Smith, Gene Gene.Smith at sea.siemens.com
Tue Jul 24 20:27:50 UTC 2001

Is this a red-herring?

************ MBUF STATISTICS ************
mbufs: 512    clusters: 128    free: 128
drops:   0       waits:   0  drains:   0
      free:503           data:3           header:9           socket:0       
       pcb:0           rtable:0           htable:0           atable:0       
    soname:0           soopts:0           ftable:0           rights:0       
    ifaddr:0          control:0          oobdata:0       

Note that the number of free+data+header add to 515, yet the number of mbufs
is 512.
Is this typical?  I see this quite often.

-----Original Message-----
From: Smith, Gene 
Sent: Friday, July 20, 2001 3:51 PM
To: rtems-users at oarcorp.com
Subject: RE: TCP/IP "receive 3" panic

>-----Original Message-----
>From: Smith, Gene 
>Sent: Thursday, July 19, 2001 8:44 AM
>Am I the only one or has anyone seen the panic("receive 3") in
>libnetworking/kern/uipc_socket.c? I can produce it fairly easily on my
>system.  However,  and this may be bad, I can substitute a 
>printk for it and
>its occurrence *seems* to cause no harm!

The networking supplement states "A given socket can be read or written by
only one task at a time."
I have a read task and write task that access the same sockets.  However, my
sockets are all non-blocking so functions read and write in their respective
tasks would not be active at the same time, I think.   

More information about the users mailing list