1388966422 Q * Wonka Ping timeout: 480 seconds 1388966865 J * Wonka produziert@chaos.in-kiel.de 1388967269 Q * Wonka Read error: Connection reset by peer 1388967270 J * Wonka produziert@chaos.in-kiel.de 1388967272 J * FireEgl ~FireEgl@173-23-77-153.client.mchsi.com 1388968057 Q * Wonka Read error: Connection reset by peer 1388968059 J * Wonka produziert@chaos.in-kiel.de 1388968591 Q * Wonka Ping timeout: 480 seconds 1388968957 J * looper ~looper@p5B322D91.dip0.t-ipconnect.de 1388969696 J * Wonka produziert@chaos.in-kiel.de 1388970002 Q * fisted Remote host closed the connection 1388970022 J * fisted ~fisted@xdsl-84-44-224-240.netcologne.de 1388970221 Q * Wonka Ping timeout: 480 seconds 1388970559 Q * looper Quit: Textual IRC Client: www.textualapp.com 1388971343 J * Wonka produziert@chaos.in-kiel.de 1388971829 Q * Wonka Ping timeout: 480 seconds 1388972626 J * Romster ~Romster@202.168.100.149.dynamic.rev.eftel.com 1388972894 J * Wonka produziert@chaos.in-kiel.de 1388973028 Q * Ghislain Quit: Leaving. 1388973419 Q * Wonka Ping timeout: 480 seconds 1388973917 J * Wonka produziert@chaos.in-kiel.de 1388974120 Q * fisted Remote host closed the connection 1388974212 J * fisted ~fisted@xdsl-84-44-224-240.netcologne.de 1388974423 Q * undefined Ping timeout: 480 seconds 1388976271 J * fisted_ ~fisted@xdsl-84-44-224-240.netcologne.de 1388976271 Q * fisted Read error: Connection reset by peer 1388976288 N * fisted_ fisted 1388982561 Q * Wonka Read error: Connection reset by peer 1388982563 J * Wonka produziert@chaos.in-kiel.de 1388983231 Q * Wonka Ping timeout: 480 seconds 1388984641 J * Wonka produziert@chaos.in-kiel.de 1388984969 Q * Wonka Read error: Connection reset by peer 1388985588 J * Wonka produziert@chaos.in-kiel.de 1388986071 Q * Wonka Ping timeout: 480 seconds 1388986332 Q * MC71 Ping timeout: 480 seconds 1388986529 J * Wonka produziert@chaos.in-kiel.de 1388987074 Q * Wonka Ping timeout: 480 seconds 1388987552 J * Wonka produziert@chaos.in-kiel.de 1388987883 Q * Wonka Read error: Connection reset by peer 1388987887 J * Wonka produziert@chaos.in-kiel.de 1388988059 M * Bertl off to bed now ... have a good one everyone! 1388988070 N * Bertl Bertl_zZ 1388988134 N * l0kit Guest2720 1388988140 J * l0kit ~1oxT@0001b54e.user.oftc.net 1388988279 Q * Guest2720 Remote host closed the connection 1388988374 Q * Wonka Ping timeout: 480 seconds 1388988816 J * Wonka produziert@chaos.in-kiel.de 1388989354 Q * Wonka Ping timeout: 480 seconds 1388989834 J * Wonka produziert@chaos.in-kiel.de 1388990356 Q * Wonka Ping timeout: 480 seconds 1388991162 J * Wonka produziert@chaos.in-kiel.de 1388991671 Q * Wonka Ping timeout: 480 seconds 1388992034 J * ard ~ard@gw-cistron.kwaak.net 1388992129 J * Wonka produziert@chaos.in-kiel.de 1388992651 Q * Wonka Ping timeout: 480 seconds 1388993459 J * Wonka produziert@chaos.in-kiel.de 1388993800 Q * Wonka Read error: Connection reset by peer 1388993803 J * Wonka produziert@chaos.in-kiel.de 1388994326 Q * Wonka Ping timeout: 480 seconds 1388994638 J * Ghislain ~aqueos@adsl1.aqueos.com 1388994826 J * Wonka produziert@chaos.in-kiel.de 1388995331 Q * Wonka Ping timeout: 480 seconds 1388995776 J * Wonka produziert@chaos.in-kiel.de 1388996311 Q * Wonka Ping timeout: 480 seconds 1388996796 J * Wonka produziert@chaos.in-kiel.de 1388997316 Q * Wonka Ping timeout: 480 seconds 1388997818 J * Wonka produziert@chaos.in-kiel.de 1388998331 Q * Wonka Ping timeout: 480 seconds 1388998774 J * Wonka produziert@chaos.in-kiel.de 1388999311 Q * Wonka Ping timeout: 480 seconds 1389000065 J * BWare ~itsme@31.25.99.5 1389000098 J * Wonka produziert@chaos.in-kiel.de 1389000616 Q * Wonka Ping timeout: 480 seconds 1389001740 J * Wonka produziert@chaos.in-kiel.de 1389002231 Q * Wonka Ping timeout: 480 seconds 1389002677 J * Wonka produziert@chaos.in-kiel.de 1389003212 Q * Wonka Ping timeout: 480 seconds 1389003453 M * Jb_boin what are the limitations on 3.10 kernels, some ressources limitations using cgroup doesnt works? 1389003696 J * Wonka produziert@chaos.in-kiel.de 1389004231 Q * Wonka Ping timeout: 480 seconds 1389004717 J * Wonka produziert@chaos.in-kiel.de 1389005172 Q * Wonka Read error: Operation timed out 1389005679 J * Wonka produziert@chaos.in-kiel.de 1389006214 Q * Wonka Ping timeout: 480 seconds 1389006707 J * Wonka produziert@chaos.in-kiel.de 1389007234 Q * Wonka Ping timeout: 480 seconds 1389007544 Q * BlackPanx Read error: No route to host 1389007646 J * BlackPanx ~kvirc@31.15.133.178 1389007727 J * Wonka produziert@chaos.in-kiel.de 1389007732 Q * Romster Quit: Geeks shall inherit properties and methods of object earth. 1389007930 M * ard Jb_boin : my experience is that cgroup limiting works. But you must watch out with memory limiting. There are some races that will make your host "hang" 1389007985 M * ard I am trying to build a testcase : https://github.com/ardje/misc/tree/master/memstress 1389008001 M * ard but right now I seem to have the need to switch to enlightenment 1389008234 Q * Wonka Ping timeout: 480 seconds 1389008680 J * Wonka produziert@chaos.in-kiel.de 1389009214 Q * Wonka Ping timeout: 480 seconds 1389010008 J * Wonka produziert@chaos.in-kiel.de 1389010071 Q * ircuser-1 Read error: Operation timed out 1389010532 Q * Wonka Ping timeout: 480 seconds 1389010790 N * Bertl_zZ Bertl 1389010811 M * Bertl morning folks! 1389011246 M * morfoh moin Bertl 1389011337 J * Wonka produziert@chaos.in-kiel.de 1389011834 Q * Wonka Ping timeout: 480 seconds 1389012280 J * Wonka produziert@chaos.in-kiel.de 1389012375 M * Jb_boin ok, thanks for the info 1389012436 M * Jb_boin so i will stick with 3.10 as i only put "safe" memory limits that shouldnt be hit on normal use 1389012784 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net 1389012811 Q * Wonka Ping timeout: 480 seconds 1389012874 M * ard Jb_boin : that's ok. I've got a lot of stable machines with 3.10, but when the userspace starts pounding on the memory limits the chance of getting stuck is big 1389013202 Q * fisted Remote host closed the connection 1389013227 J * fisted ~fisted@xdsl-78-35-83-9.netcologne.de 1389013300 J * Wonka produziert@chaos.in-kiel.de 1389013831 Q * Wonka Ping timeout: 480 seconds 1389014032 Q * fisted Ping timeout: 480 seconds 1389014034 J * fisted ~fisted@xdsl-78-35-83-9.netcologne.de 1389014319 J * Wonka produziert@chaos.in-kiel.de 1389014834 Q * Wonka Ping timeout: 480 seconds 1389014965 M * ard Bah... memstress does not trigger it... 1389014972 A * ard is spitting in old OOPSes.. 1389015081 M * ard http://paste.linux-vserver.org/39557 1389015106 M * ard at least one ext4 reference... 1389015155 M * ard Hmmmm, I think: 1389015162 M * ard [] ? mem_cgroup_cache_charge+0x7a/0x80 1389015162 M * ard [] ? add_to_page_cache_locked+0x45/0x170 1389015162 M * ard [] ? ext4_get_block_write+0x10/0x10 1389015216 M * ard that part is the cause of it: page cache is assigned to a cgroup, cgroup is full, but ext4 needs the memory to be able to write it. 1389015280 J * thierryp ~thierry@zebra.inria.fr 1389015282 J * Wonka produziert@chaos.in-kiel.de 1389015465 M * ard Hmmm, my current problem is that my memstress software doesn't OOM :-(. 1389015811 Q * Wonka Ping timeout: 480 seconds 1389016301 J * Wonka produziert@chaos.in-kiel.de 1389016834 Q * Wonka Ping timeout: 480 seconds 1389017321 J * Wonka produziert@chaos.in-kiel.de 1389017487 M * ard Hah, my test system is now dead 1389017513 M * ard "dead" 1389017532 M * ard no oops :-( 1389017550 M * Bertl not dead, just sleeping? 1389017622 M * ard Hmmmm it's weird... 1389017628 M * ard I can log in, but vtop hangs 1389017640 M * ard (log into the host) 1389017649 M * Bertl maybe it just takes a while 1389017658 M * Bertl i.e. looong 1389017706 M * ard what's more interesting is that I don't see the vtop anymore 1389017711 M * ard and the sshd... 1389017722 A * ard will try the serial console 1389017810 M * ard ah.. the vtop runs in xid 1 right? And that's not viewable from 0 1389017819 M * Bertl yup 1389017825 M * ard using serial console the vtop doesn't stop 1389017836 Q * Wonka Ping timeout: 480 seconds 1389017838 M * ard but using ssh login it really stops 1389017864 M * Bertl can have a number of causes 1389017865 M * ard still no oops :-( 1389017886 M * ard I can live with not being able to run vtop :-) 1389017887 M * Bertl if you want to trigger OOM kills, you need to write to allocated memory 1389017907 M * ard I do, but I think I am too simple... 1389017915 M * Bertl (or switch from overcommitment to correct accounting) 1389017923 M * ard https://github.com/ardje/misc/blob/master/memstress/memstress.c 1389017954 M * ard I probably need to allocate more than 8k to get ... ow wait I get something now 1389017988 M * ard just task hung... 1389018014 M * ard But I probably need to allocate a few MB to get overcommitment, and only then start writing to it 1389018016 M * Bertl that's probably something you want to disable 1389018042 M * Bertl because in my experience, once you get a task hung dump, the kernel is going downhill 1389018085 M * Bertl it's hard to say what is the cause and what the effect, just speaking of my observations 1389018090 M * ard and /proc///stacktrace can do the same :-) 1389018124 M * ard (if you see something stuck I mean) 1389018161 M * Bertl yeah, well, in my experience, processes which get dumped by the hung task dumper never recover 1389018187 M * Bertl even if those processes are nfs or similar, which just takes long but usually recovers quite fine 1389018219 M * Bertl that's the main reason why I disable this feature in all my kernels 1389018398 M * ard but vps faux should work if the vserver is under memory stress but the host not, right? Because then I have at least a testcase for that ;-). 1389018414 A * ard builds a kernel without the hung task 1389018465 M * Bertl vps should not be affected by memory pressure 1389018517 M * Bertl note that vps will be affected by rapidly chaning process ids or similar (i.e the very same as ps using the proc interface) 1389018598 J * Wonka produziert@chaos.in-kiel.de 1389019032 J * MC71 ~MadCow@0001c2a3.user.oftc.net 1389019122 Q * Wonka Ping timeout: 480 seconds 1389019620 J * Wonka produziert@chaos.in-kiel.de 1389019682 M * ard Bertl : what about 'Detect Hard and Soft Lockups' 1389019717 M * Bertl should be fine, just the hung task option caused grief 1389019806 M * ard They also poop out stacktraces based on NMI and hrtime probes 1389019847 M * Bertl had no problems with nmi yet 1389019865 M * ard Ok :-) 1389020136 Q * Wonka Ping timeout: 480 seconds 1389020581 J * Wonka produziert@chaos.in-kiel.de 1389021107 Q * Wonka Ping timeout: 480 seconds 1389021191 M * ard Now that I think of it: 1389021207 M * ard the vtop hung the moment I increased the memory of the cgroup... 1389021603 J * Wonka produziert@chaos.in-kiel.de 1389021644 M * ard Hmmm, yes, increasing memory.memsw.limit_in_bytes makes vtop hung... 1389021699 M * ard root 5284 5.5 0.0 164 28 ? D 16:21 0:00 \_ vuname --get --xid killmem 1389021724 M * ard also stops until I increase memory yet again... 1389021831 M * ard http://paste.linux-vserver.org/39576 1389022128 Q * Wonka Ping timeout: 480 seconds 1389022379 M * ard hmmm, weird... 3.10.12 gave me no OOM, 3.10.25 starts OOMing right away. the difference is vs2.3.6.6 and vs2.3.6.8 1389022530 Q * ensc|w Remote host closed the connection 1389022539 J * ensc|w ~ensc@www-old.sigma-chemnitz.de 1389022625 J * Wonka produziert@chaos.in-kiel.de 1389022877 J * thierryp_ ~thierry@zebra.inria.fr 1389022877 Q * thierryp Read error: Connection reset by peer 1389022983 Q * thierryp_ Remote host closed the connection 1389023439 Q * Wonka Ping timeout: 480 seconds 1389023572 J * Wonka produziert@chaos.in-kiel.de 1389024093 Q * Wonka Ping timeout: 480 seconds 1389024094 J * zerick ~eocrospom@190.187.21.53 1389024538 M * Bertl ard: plus a bunch of mainline changes :) 1389024550 M * ard of course :-) 1389024590 J * Wonka produziert@chaos.in-kiel.de 1389024909 M * ard maybe I should just copy that guys vserver to the test environment... something uwsgi and python 1389025111 Q * Wonka Ping timeout: 480 seconds 1389025610 J * Wonka produziert@chaos.in-kiel.de 1389026131 Q * Wonka Ping timeout: 480 seconds 1389026628 J * Wonka produziert@chaos.in-kiel.de 1389027007 Q * MC71 Ping timeout: 480 seconds 1389027136 Q * Wonka Ping timeout: 480 seconds 1389027582 J * Wonka produziert@chaos.in-kiel.de 1389027669 J * MC71 ~MadCow@0001c2a3.user.oftc.net 1389028036 Q * Wonka Read error: Operation timed out 1389028603 J * Wonka produziert@chaos.in-kiel.de 1389029113 J * undefined ~undefined@24.178.29.193 1389029122 P * undefined 1389029134 Q * Wonka Ping timeout: 480 seconds 1389029175 J * undefined ~undefined@00011a48.user.oftc.net 1389029324 Q * brambles Ping timeout: 480 seconds 1389029572 J * brambles lechuck@s0.barwen.ch 1389029625 J * Wonka produziert@chaos.in-kiel.de 1389030097 Q * Wonka Read error: Connection reset by peer 1389030272 J * Wonka produziert@chaos.in-kiel.de 1389034995 Q * yang_ Remote host closed the connection 1389035554 J * yang yang@irs.si 1389036411 Q * yang Remote host closed the connection 1389036428 J * yang yang@yang.netrep.oftc.net 1389036735 J * thierryp ~thierry@home.parmentelat.net 1389036872 Q * MC71 Ping timeout: 480 seconds 1389037533 Q * thierryp Quit: ciao folks 1389042902 Q * yang Remote host closed the connection 1389043032 J * yang yang@yang.netrep.oftc.net 1389044355 J * sannes ~ace@2a02:fe0:c120:be90:224:1dff:fe14:d24 1389044481 J * ntrs ~ntrs@vault08.rosehosting.com 1389046157 Q * bonbons Quit: Leaving 1389048508 Q * ntrs Ping timeout: 480 seconds 1389048922 J * ntrs ~ntrs@vault08.rosehosting.com 1389049951 Q * Ghislain Quit: Leaving. 1389050269 Q * zerick Remote host closed the connection 1389052673 J * MC71 ~MadCow@0001c2a3.user.oftc.net 1389052726 Q * undefined Ping timeout: 480 seconds