1357344064 M * ard I have a single trace (stopped the console log because I am on a very low powered arm netbook ;-) ) 1357344074 M * ard jock login: BUG: spinlock recursion on CPU#0, ab/3467 1357344086 M * Bertl sounds good 1357344144 M * ard http://paste.linux-vserver.org/23164 1357344216 M * Bertl that is without the patch, yes? 1357344251 M * ard correct 1357344259 M * ard I think that kernel has now finished compiling 1357344275 M * ard ow noes... 1357344283 M * ard No space left on device 1357344285 A * ard sighs 1357344291 M * Bertl okay, that one should be fixed by the patch and might be the actual problem you discovered ... 1357344730 A * ard is still waiting for the du to report where my 48G went 1357344969 A * ard reclaimed 2G by removing 2.6 kernel builds :-) 1357345755 M * ard it still works... 1357345759 M * ard :-) 1357345789 M * Bertl is this now with spin lock debugging enabled or disabled? 1357345816 M * ard it\s the same config as previous (with DEBUG_SPINLOCK) 1357345825 M * Bertl okay, great! 1357346006 M * ard 2400r/s with 0.417ms average time per request 1357346033 M * ard with a concurrency level of 1 that's pretty ok 1357346068 M * Bertl don't forget that the spinlock debugging has some overhead 1357346209 M * ard with a -c 20 the number is tenfold... 25kr/s 1357346269 M * ard if you then use 7 packets total per connection, it's about 176k/s .. 1357346294 M * ard a 2.4 kernel would choke on 70kp/s ... 1357346325 M * Bertl there is a reason we do not use them anymore :) 1357346350 M * Bertl (except for really stable debian systems :) 1357346368 M * ard I was really astonished... during a ddos I was upgrading a loadbalancer/firewall from 2.4.30 to 2.6.24 1357346391 M * ard from 70kp/s and near death it went to 600kp/s and not a single problem.... 1357346434 M * ard and about stable debian systems... I still have a system: up 2613 days 1357346455 M * ard probably rebooted due to a power maintenance 1357346492 M * ard but these last few kernels, especially combined with linux-vserver... 1357346509 M * ard linux-vserver allows one to fully stress all parts of the kernel at the same time 1357346511 M * Bertl 1158 days here, no maintainance (good ups) 1357346564 M * ard A lot of troubles with md raid 1 :-( 1357346612 M * ard As a newspaper company our UPS gives us more trouble than the 5 or more feeds of 10kV we get to power the presses ;-) 1357346621 M * Bertl okay, so I take it, that the spinlock debugging doesn't gave any comments during stressing? 1357346640 M * ard still nothing on the console... 1357346659 M * ard yay! o// \\o \o/ :-) 1357346663 M * ard thanks Bertl ! 1357346663 M * Bertl good, I'd say, disable the spinlock debugging, and test on the original bnx2 system 1357346690 M * Bertl you're welcome! and thanks for testing/reporting! 1357346758 M * ard the normal DEBUG_INFO is just static data, right? Like normal debug info in any elf file? 1357346767 M * Bertl yes, leave it in 1357346782 M * Bertl doesn't hurt, and will help a lot in case something comes up 1357348553 M * ard d \ 1357348562 M * ard Hmmmmm 1357348579 M * ard weird that that installation maxes at 16kr/s 1357348591 M * ard (from network as well as from lo) 1357348651 M * ard anyway, thanks again, I now have to spend time with the kittens, else they will take over the keyboard :-) 1357348656 M * ard 0/~ 1357348663 M * Bertl have fun! 1357351991 M * Bertl off for a nap ... bbl 1357351995 N * Bertl Bertl_zZ 1357371952 J * Ghislain ~aqueos@adsl1.aqueos.com 1357375203 Q * Ghislain Quit: Leaving. 1357375359 J * Ghislain ~aqueos@adsl1.aqueos.com 1357375591 Q * Ghislain 1357378879 J * bonbons ~bonbons@2001:960:7ab:0:9142:79e7:47d:e542 1357380419 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f 1357383602 Q * fisted Remote host closed the connection 1357383662 J * fisted ~fisted@xdsl-87-78-180-239.netcologne.de 1357385658 Q * ircuser-1 Read error: Operation timed out 1357387346 J * Ghislain ~aqueos@adsl1.aqueos.com 1357389477 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net 1357389788 Q * Aiken Remote host closed the connection 1357390343 Q * ensc|w Remote host closed the connection 1357390352 J * ensc|w ~ensc@www.sigma-chemnitz.de 1357398167 N * Bertl_zZ Bertl 1357398171 M * Bertl morning folks! 1357399371 J * nkukard ~nkukard@41.177.82.218 1357399703 J * hijacker_ ~hijacker@cable-84-43-134-121.mnet.bg 1357406020 J * isAAAc ~isaaac@pat35-4-88-164-240-246.fbx.proxad.net 1357407820 Q * karasz Remote host closed the connection 1357410253 J * karasz ~karasz@00015555.user.oftc.net 1357414956 Q * hparker Remote host closed the connection 1357415546 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f 1357415936 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647 1357417789 Q * Ghislain Quit: Leaving. 1357421646 Q * hijacker_ Quit: Leaving 1357422134 J * isAAAc_ ~isaaac@pat35-4-88-164-240-246.fbx.proxad.net 1357422134 Q * isAAAc Read error: Connection reset by peer 1357423390 Q * cuba33ci Ping timeout: 480 seconds 1357423861 J * mikez mike@inet-sec.eu 1357423885 M * mikez Bertl: any way to run my vserver on boot? 1357423909 M * mikez the way on linux-vserver doesnt work at all 1357425234 M * Bertl hmm? 1357425263 M * Bertl util-vserver includes a sysv runlevel script to start guests marked with 'default' 1357426802 Q * fisted Remote host closed the connection 1357426863 J * fisted ~fisted@xdsl-78-35-87-51.netcologne.de 1357427320 M * mikez it does not work i think 1357427550 Q * bonbons Quit: Leaving 1357427680 M * Bertl is the runlevel script started? 1357427687 M * Bertl i.e. does it show something like: 1357427710 M * Bertl Starting vservers of type 'default'...[ OK ] 1357427820 Q * isAAAc_ Quit: Konversation terminated! 1357427885 M * mikez my was was diffrent i think 1357428028 M * Bertl well, check it if something similar shows up, if not, make sure your init system executes them 1357428127 M * mikez erm how does it work if i run /etc/init.d/vservers stop 1357428132 M * mikez it will shutdown my vs 1357428141 M * mikez but if i type start 1357428145 M * mikez it does not 1357428154 M * Bertl it's not supposed to start any 1357428167 M * Bertl that's what the vservers-default script is for 1357428218 M * mikez what is for util-vserver init script for? 1357428236 M * Bertl initializing the util-vserver environment 1357428408 M * mikez hm 1357428411 M * mikez cannot start it 1357428412 M * mikez * Starting vservers of type 'default' ... [ ok ] 1357428416 M * mikez touch: nie można dotknÄ 1357428418 M * mikez Ä â/var/lock/vservers/vservers-defaultâ 1357428451 M * Bertl use export LANG=C 1357428554 M * Bertl and maybe export LC_ALL=C 1357428622 M * mikez ks367289 vservers # /etc/init.d/vservers.default start * Starting vservers of type 'default' ... OK 1357428633 M * Bertl looks good 1357428651 M * Bertl so, do your guests have a 'default' mark? 1357428722 M * Bertl if not, do 'mkdir -p /etc/vservers//apps/init; echo "default" >/etc/vservers//apps/init/mark' 1357428897 M * mikez Bertl: yes its sorted now 1357428936 M * mikez i was reading http://linux-vserver.org/Frequently_Asked_Questions before but it was notginy mentioned about vserver.default 1357428970 M * mikez so i done this default init but i stuck with this init.d/vserver script ;) 1357429036 M * Bertl well, the scripts are started by default on any sysv compatible distro 1357429046 M * mikez not gentoo tho :) 1357429069 M * Bertl yeah, maybe they messed something up, but I guess it is a config problem 1357429325 M * mikez well anyway, thanks for your brilliant support 1357429330 M * Bertl you're welcome! 1357429330 M * mikez like always!