missing network interface flags

Hi,

I'm using RedHat AS 3.0 on an S/390:

Linux stldv002 2.4.21-4.0.1.EL #1 SMP Thu Oct 23 01:19:46 EDT 2003 s390x s390x 
s390x GNU/Linux

[root@stldv002 linux]# cat /proc/cpuinfo 
vendor_id       : IBM/S390
# processors    : 1
bogomips per cpu: 643.89
processor 0: version = FF,  identification = 02888A,  machine = 2066

And I've noticed that when I run tcpdump, the PROMISC flag does not get 
reported in ifconfig. Please note the lack of difference before and after 
running tcpdump (which puts the interface into promiscuous mode):

[root@stldv002 linux]# ifconfig ctc0
ctc0      Link encap:Serial Line IP  
          inet addr:10.208.12.75  P-t-P:10.208.12.23  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP  MTU:1492  Metric:1
          RX packets:430059 errors:0 dropped:0 overruns:0 frame:0
          TX packets:389571 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:110566199 (105.4 Mb)  TX bytes:125643131 (119.8 Mb)

[root@stldv002 linux]# tcpdump -i ctc0 >/dev/null &
[1] 14443
tcpdump: listening on ctc0
[root@stldv002 linux]# tail -1 /var/log/messages
Jan 21 17:22:56 stldv002 kernel: device ctc0 entered promiscuous mode
[root@stldv002 linux]# date
Wed Jan 21 17:23:02 CST 2004
[root@stldv002 linux]# ifconfig ctc0
ctc0      Link encap:Serial Line IP  
          inet addr:10.208.12.75  P-t-P:10.208.12.23  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP  MTU:1492  Metric:1
          RX packets:430203 errors:0 dropped:0 overruns:0 frame:0
          TX packets:389650 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          RX bytes:110575463 (105.4 Mb)  TX bytes:125651727 (119.8 Mb)

If that's not proof enough, I've also written a program which retrieves the 
interface flags from the kernel via the SIOCGIFFLAGS ioctl call, and it too 
fails to see the PROMISC flag as set.

Has anyone else ever seen behavior like this?

On a similar note, it appears that there are processes missing from the 
process table as it's retrieved by the ps command (in the following example 
my syslogd is running under pid 322):

[root@stldv002 linux]# ps -fp 322
UID        PID  PPID  C STIME TTY          TIME CMD
[root@stldv002 linux]# ls -ld /proc/322
dr-xr-xr-x    3 root     root            0 Jan 21 17:27 /proc/322
[root@stldv002 linux]# kill -HUP 322 
[root@stldv002 linux]# tail -1 /var/log/messages
Jan 21 17:27:22 stldv002 syslogd 1.4.1: restart.
[root@stldv002 linux]# ps -fp 322
UID        PID  PPID  C STIME TTY          TIME CMD
[root@stldv002 linux]# 

If anyone else has seen behavior like this, or knows what my problem is, I 
would be very thankful for the validation/help.

Thanks!
Martin McGreal