Quoting Jean-Marc Pigeon (j...@safe.ca):
> Hello Serge,
> 
>       Thanks for the small test, I do confirm
>       there is the same problem here with it, 
>       as soon started the program use ALL available 
>       CPU cycle (minus some few %) and NEVER
>       EVER come back from "clone" function.
>       The ONLY way I found to recover the
>       system is to power it down (sic!).
> 
>       See attachment, your program, the 
>       .config file, and cpu information
>       (I put back your test too, (done 
>        cosmetic changes only)).
> 
>       Once again, clone call on 2.6.32.3
>       is working fine.
> 
>       Sorry to bother the list, I was "expecting"
>       a Stack size problem, but I increase
>       your value from 4 to 10, with the same result.
>       Hopefully it could be something I overlooked
>       with my Kernel config file, if someone
>       want to have a look I attached it.
> 
>       My guess for now it is something within
>       the clone code specific to i386.
>       
>       I 'll try to pin point within the 
>       clone code.
> 
>       (could someone check tstclone.c under 
>        i386 arch and confirm trouble?)

Also might echo 1 > /proc/sys/kernel/sysrq before running the test, then
hit alt-sysrq-d to show all locks being held, alt-sysrq-l to show
stacks, alt-sysrq-p to dump registers, and alt-sysrq-t to dump tasks.

-serge
_______________________________________________
Containers mailing list
contain...@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers

_______________________________________________
Devel mailing list
Devel@openvz.org
https://openvz.org/mailman/listinfo/devel

Reply via email to