Consistently seeing the problem with SLED10 SP1 on x86_64.
With SLES9 SP4 on x86_64 I don't see the problem ever.
So there is a pid 0 in proc?
> ls /proc
0 15526 27566 349 4320 4735 4824 5552 885 irq
1 16143 27584 350 4345 4737 4829 5561 886 kallsyms
1012 16150 27608 3579 4346 4738 4831 5620 8863 kcore
1033 16186 27626 3587 4349 4739 4839 5622 887 kmsg
1036 16345 2834 3694 4359 4740 4851 5625 888 loadavg
1106 16452 2864 3697 4392 4741 4862 5630 9 locks
1107 16462 2868 374 4393 4742 4868 5639 904 mdstat
11683 17506 2870 377 4394 4743 4879 5687 910 meminfo
12105 17520 2872 3805 4395 4744 4890 5689 926 misc
12488 17521 28982 3808 4396 4745 4966 5690 9527 modules
12898 19042 29007 3809 4497 4746 4975 5693 9530 mounts
12933 2 3 381 4498 4747 4998 5715 9533 mtrr
13 20769 30717 384 4501 4748 5 598 9536 net
131 2082 30956 390 4503 475 5003 6 9542 partitions
132 2083 30991 3929 4505 4750 501 6189 acpi scsi
133 2085 30994 3938 4507 4758 504 6259 asound self
13314 2086 31029 396 4519 4766 5062 6262 buddyinfo slabinfo
134 21008 31032 3972 4575 4768 5180 6265 bus splash
13427 2149 31035 3974 4612 4772 5186 6271 cmdline stat
13428 2154 31038 3976 4655 4774 5198 6274 config.gz swaps
14 2159 31041 3978 4661 4776 5218 644 cpuinfo sys
14093 2206 31044 3980 4662 478 5250 7 crypto sysrq-trigger
14111 2208 31163 3983 467 4780 5266 714 devices sysvipc
14190 2210 31213 399 4670 4781 527 715 diskstats tty
14243 22175 31276 4 4693 4784 5277 716 dma uptime
1438 22561 31743 406 4696 4788 5410 727 driver version
14781 2281 31761 4107 4698 4789 5438 728 execdomains vmnet
14782 24241 31764 411 4700 4792 5456 757 fb vmstat
15 24303 31825 4128 4705 4796 5458 8 filesystems zoneinfo
15160 25170 32366 4139 4707 4802 5468 806 fs
15347 25232 3347 4162 4708 481 5477 807 ide
15349 26540 3387 4254 4710 4812 5500 809 interrupts
15350 27192 3471 4291 4712 4814 5502 8209 iomem
15450 27313 348 4316 472 4822 5534 8781 ioports
but if i do an ls /proc/0 it's not there, or an ls -la /proc
> ls /proc/0
/bin/ls: /proc/0: No such file or directory
So this appears to be a SLED/SLES10 issue?
I can reproduce this on both on my desktop and on a SGI Altix 450, the key
seems to be just do a ls /proc?
|