1540602281 J * zc0nf ~zc0nf@218.144.204.17
1540602321 Q * zc0nf Remote host closed the connection
1540608652 M * Bertl_oO please everybody register their nick and identify in case you want to send a message to the channel ... thanks!
1540608933 J * jatan ~jatan@27.79.193.98
1540608945 Q * jatan autokilled: Vulnerable SSH daemon found on this host. Contact support@oftc.net for assistance. (2018-10-27 02:55:44)
1540610504 J * andi ~andi@pl1937.ag1212.nttpc.ne.jp
1540610525 N * andi Guest1481
1540610544 Q * Guest1481 Remote host closed the connection
1540611885 J * azend|vps_ ~azend|vps@124x35x77x172.ap124.ftth.ucom.ne.jp
1540611941 Q * azend|vps_ Remote host closed the connection
1540615313 J * bildz ~bildz@109.74.67.49
1540615316 Q * bildz autokilled: This host may be infected. Mail support@oftc.net with questions. BOPM (2018-10-27 04:41:56)
1540620290 J * sudden ~sudden@37.114.146.253
1540620294 Q * sudden autokilled: This host may be infected. Mail support@oftc.net with questions. BOPM (2018-10-27 06:04:54)
1540621632 J * jab41617127 ~jab416171@2402:800:610b:bf32:b1a4:c5b1:b5e9:8dd0
1540621843 Q * jab41617127 Remote host closed the connection
1540622044 J * berFt ~berFt@61-231-41-65.dynamic-ip.hinet.net
1540622059 Q * berFt autokilled: This host has violated network policy. Contact support@oftc.net with questions (2018-10-27 06:34:19)
1540623591 J * peaveyman ~peaveyman@541E6769.cm-5-7b.dynamic.ziggo.nl
1540623607 Q * peaveyman Remote host closed the connection
1540628487 M * Guy- Bertl_oO: maybe add this to the topic?
1540629224 M * Bertl_oO yeah, will see if I can cram that in ...
1540631055 J * Hdale ~Hdale@39.115.30.189
1540631086 Q * Hdale Remote host closed the connection
1540631357 J * Rachtah ~Rachtah@softbank126066192011.bbtec.net
1540631379 Q * Rachtah autokilled: This host has violated network policy. Contact support@oftc.net with questions (2018-10-27 09:09:39)
1540631533 J * VLMC ~VLMC@p2E5A4D0B.dip0.t-ipconnect.de
1540631566 Q * VLMC Remote host closed the connection
1540636030 J * squarebracket ~squarebra@110.12.160.244
1540636069 Q * squarebracket Remote host closed the connection
1540639206 J * timotab|gone ~timotab|g@95.72.92.39
1540639249 Q * timotab|gone Remote host closed the connection
1540639798 M * Guy- Bertl_oO: maybe something like "Identify to NickServ to talk.|http://linux-vserver.org/|Latest patches for: 4.4.x, 4.9.x|Please help us complete documentation in the wiki"
1540642593 Q * Aiken Remote host closed the connection
1540644793 J * LaserAllan_ ~LaserAlla@152.170.188.86
1540644816 Q * LaserAllan_ autokilled: Possible spambot. Mail support@oftc.net if you think this is in error. (2018-10-27 12:53:36)
1540651960 J * estranger ~estranger@200.165.108.93.rev.vodafone.pt
1540651975 Q * estranger Remote host closed the connection
1540662811 J * stevest ~stevest@118-165-37-177.dynamic-ip.hinet.net
1540662840 Q * stevest Remote host closed the connection
1540665111 J * Aiken ~Aiken@b951.h.jbmb.net
1540672835 J * unek7 ~unek@x4e34f9e3.dyn.telefonica.de
1540672910 Q * unek7 Remote host closed the connection
1540673608 M * arekmx tested 4.9.135+latest patchset and unfortunately the "ping" lockup is not gone
1540675060 M * Hurga "ping" lockup?
1540675460 Q * Aiken Remote host closed the connection
1540675558 J * Aiken ~Aiken@b951.h.jbmb.net
1540676586 J * sukaeto ~sukaeto@114-25-179-59.dynamic-ip.hinet.net
1540676588 Q * sukaeto Remote host closed the connection
1540677287 M * arekmx Hurga: 4.9 kernel + network context + any network operation inside (like just ping) -> cpu lockup
1540677332 J * Shrike ~Shrike@125-230-55-238.dynamic-ip.hinet.net
1540677368 Q * Shrike Remote host closed the connection
1540677901 M * Bertl_oO arekmx: sounds interesting ... sure that's not driver/hardware related?
1540677981 M * Bertl_oO can you reproduce this issue in a kvm guest?
1540678049 J * teadrop___ ~teadrop__@192.228.144.163
1540678088 Q * teadrop___ Remote host closed the connection
1540678107 M * arekmx Bertl_oO: it's hw related because doesn't happen on every machine. But it happens only with vserver. Host only is immune
1540678147 M * arekmx (that's the same issue we talked here about few weeks/months ago)
1540678159 M * arekmx don't know how to get any useful debug info from "cpu lockup" state
1540678181 M * Bertl_oO got more than one CPU?
1540678211 M * Bertl_oO if so, do all of them lock up?
1540678254 M * arekmx testing with PROVE_LOCKING=y
1540678288 M * arekmx Bertl_oO: probably because everything halts. Rebuilding kernel with option above and can test again how many lockup messages will be there
1540678310 M * Bertl_oO also, do we have an assortment of CPU backtraces of the 'stuck' CPU(s)?
1540678326 M * arekmx last time backtraces were useless
1540678354 M * arekmx aka didn't give any hints 
1540678386 M * Bertl_oO well, they might give some clues at some point
1540678439 M * arekmx from last time https://pastebin.com/fWxSQhyu
1540678521 M * arekmx (few months ago)
1540680577 J * zduniak ~zduniak@186.47.168.92
1540680600 Q * zduniak autokilled: This host has violated network policy. Contact support@oftc.net with questions (2018-10-27 22:50:00)
1540681138 M * Bertl_oO arekmx: did you addr2line the locations?
1540681800 M * Bertl_oO could be bpf related
1540681945 M * arekmx PROVE_LOCKING didn't help :/
1540681963 M * arekmx and have no stack trace now but so far cpus 1 and 4 locked
1540682023 M * Bertl_oO well, use the magic sysrq to dump the stack for those CPUs
1540682046 M * Bertl_oO then convert the addresses to line numbers and we should be able to narrow it down
1540682048 M * arekmx and machine rebooted  (panic timeout 180s)
1540682102 M * arekmx if I only knew how to sysrq on macos terminal ;))
1540682132 M * Bertl_oO well, currently it seems you are the only one reporting this issue and nobody seems to be able to reproduce it
1540682183 M * arekmx right but there was a ntp related bug in vs that also only I triggered and it turned out to be a real bug 
1540682192 M * arekmx so hopefuly this is also a real bug hehe
1540682224 M * Bertl_oO I'm pretty sure it is, but without further investigation (read proper stack traces) we won't have much chance to do so (at the moment)
1540682317 M * Bertl_oO the trace hint towards bpf, so I would investigate there .. bpf nowadays is almost turing complete, so a lockup there is plausible
1540683254 M * arekmx need to figure out sysrq on this terminal
1540683476 J * sfeole ~sfeole@net-93-147-230-131.cust.vodafonedsl.it
1540683481 Q * sfeole autokilled: This host has violated network policy. Contact support@oftc.net with questions (2018-10-27 23:38:01)