two different things happen depending on your uid.
tty1: while [ 1 ]; do ls -laR /proc; done
tty2; watch "w;echo;free"
tty3; while [ 1 ]; do ls -laR /proc; done
tty4; top
tty arrangement is irrelevant.
UID0, oopses, crashes, and reboots will happen.
UIDn, processes go D state, WCHAN is 'down_f'
of worthy mention, is when UID0, attempting to do other /proc things
after the oopses begin, often results in Illegal Instruction aborts and
restarting the above results in more oopsing. frequently the machine
crashes and attempts the automatic reboot.
this is now the second machine i can reproduce /proc bugs on. last week
i reported D state symptoms for programs using /proc.
-d
-- This is Linux Country. On a quiet night, you can hear Windows NT reboot! Do you remember how to -think- ? Do you remember how to experiment? Linux __ is an operating system that brings back the fun and adventure in computing. \/ for linux-kernel: please read linux/Documentation/* before posting problems
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/