Solved (Was: current kernel built without TCO (-fno-optimize-sibling-calls) is almost unusable)

2018-10-23 Thread Lev Serebryakov
On 23.10.2018 17:25, Lev Serebryakov wrote: >> Here are NO any errors or message on console, but system drops ssh >> connection after several seconds (soemtimes before logon, sometimes >> right after showing shell), timeouts connections to it, etc. >> >> When I able to run "top -SH" (for several

current kernel built without TCO (-fno-optimize-sibling-calls) is almost unusable

2018-10-23 Thread Lev Serebryakov
On 23.10.2018 17:21, Lev Serebryakov wrote: > Here are NO any errors or message on console, but system drops ssh > connection after several seconds (soemtimes before logon, sometimes > right after showing shell), timeouts connections to it, etc. > > When I able to run "top -SH" (for several sec

current kernel built without TCO (-fno-optimize-sibling-calls) is almost unusable

2018-10-23 Thread Lev Serebryakov
I've built 13/current kernel with "-fno-optimize-sibling-calls" option to have full and true stacks. And my test stand (which is lousy Atom D2500, I need to admit) becomes unusable with such kernel. Here are NO any errors or message on console, but system drops ssh connection after several se