1417911094 Q * bonbons Quit: Leaving 1417913611 Q * zerick Read error: Connection reset by peer 1417914002 Q * fstd Remote host closed the connection 1417914050 J * fstd ~fstd@xdsl-87-78-81-170.netcologne.de 1417915395 Q * Hunger- Ping timeout: 480 seconds 1417916515 J * Hunger hunger@proactivesec.com 1417922390 N * Bertl_zZ Bertl 1417922396 M * Bertl back now ... 1417936393 Q * gamingrobot Remote host closed the connection 1417936576 J * gamingrobot_ sid10990@id-10990.highgate.irccloud.com 1417938836 M * gnarface Bertl: well, so i recompiled with dynticks off, and the behavior changed a bit: http://paste.debian.net/135251/ 1417938861 M * gnarface Bertl: the lockup seems less noisy, and this is the first time its gone "back to normal" as it were after the error 1417938880 M * gnarface normally it would just like, keep erroring until i rebooted 1417938941 M * gnarface but most importantly i caught the beginning of it this time 1417939051 M * gnarface what's that amd_e400_idle thing? 1417941455 M * Bertl seems to be a routine putting a core or part of the cpu to sleep 1417941503 M * Bertl you can probably get rid of the soft lockup by disabling the kernel feature, IMHO it has been a source of false positives for some time now 1417942572 M * gnarface which uh, kernel feature? 1417942634 M * gnarface lol i'd have disabled it a long time ago if i could have figured out what is complaining 1417942641 M * gnarface or what its complaining about 1417942738 M * Bertl echo 0 > /proc/sys/kernel/hung_task_timeout_secs 1417942761 M * Bertl it basically is complaining that a kernel thread "waits" for more than seconds 1417942780 M * Bertl where can be configured via sysfs (as with the echo above) 1417942828 M * gnarface oh 1417942833 M * gnarface so i could just turn it up too 1417942834 M * gnarface ? 1417942848 M * gnarface this is the first time i've seen the error actually give a legible count of time 1417942880 M * gnarface seems like 22 seconds is a bit impatient .... though it is weird that it'd be taking so long to wake up i guess 1417942914 M * Bertl mostly depends on what it is waiting for 1417942924 M * gnarface yea that's the real puzzle 1417942929 M * Bertl I've seen this on nfs client-server setups 1417942938 M * gnarface hmm. no nfs on this machine 1417942942 M * Bertl where the nfs-client is stuck waiting for the server for example 1417942968 M * gnarface i wonder if its the pata interface... 1417942975 M * Bertl but also on non networked machines with unresponsive disk subsystems 1417942989 M * gnarface hmmmm 1417943000 M * gnarface alright, maybe i'll try a different cable or something 1417943007 M * gnarface that was one suspect 1417943031 M * Bertl but I think it is primarily a kernel bug 1417943058 Q * undefined Quit: Closing object 1417943066 M * Bertl i.e. either the kernel should know that this or that operation can "take a while" or it shouldn't be "waiting" at all 1417943074 M * gnarface hmm. indeed 1417943091 M * gnarface could be bad code in the team fortress2 server as well? 1417943098 M * Bertl but this has plaqued Linux since early 3.x 1417943128 M * Bertl I don't think your team fortress code executes in kernel space 1417943135 M * gnarface oh 1417943143 M * gnarface so it couldn't be caused by something in user space 1417943148 M * gnarface sorry i didn't understand that 1417943151 M * Bertl the only case where this could be cause by userspace is if you have real-time processes running 1417943173 M * gnarface i don't know if tf2 counts as that 1417943181 M * gnarface i have wondered if i had set the tick rate too low though 1417943186 M * Bertl unless you set it to realtime, no 1417943217 M * gnarface hmm. noted 1417943255 M * gnarface brb 1417943256 Q * gnarface Quit: Leaving 1417943342 J * gnarface ~gnarface@108-227-52-42.lightspeed.irvnca.sbcglobal.net 1417943469 M * gnarface so it couldn't be caused by something expecting CONFIG_HZ=1000 when the kernel is compiled with CONFIG_HZ=250? 1417943479 M * gnarface or something like that? 1417943526 M * Bertl unlikely, HZ=1000 is 1ms, HZ=250 still 4ms per tick, which is way less than 22 seconds 1417943576 M * gnarface ah, yes i guess that makes sense 1417943757 M * gnarface as always, thank you for your patient explanation 1417943863 M * Bertl np, you're welcome! 1417944097 J * Ghislain ~aqueos@adsl1.aqueos.com 1417946819 J * bonbons ~bonbons@2001:a18:201:5a01:e942:8f44:6745:e53f 1417947882 Q * Aiken Remote host closed the connection 1417949038 M * Bertl off to bed now ... have a good one everyone! 1417949045 N * Bertl Bertl_zZ 1417950848 J * undefined ~undefined@75-141-158-50.dhcp.mdfd.or.charter.com 1417952858 Q * gamingrobot_ Remote host closed the connection 1417956255 J * gamingrobot_ sid10990@id-10990.highgate.irccloud.com 1417956757 Q * gamingrobot_ Read error: Connection reset by peer 1417957202 Q * fstd Remote host closed the connection 1417957244 J * fstd ~fstd@xdsl-87-78-142-42.netcologne.de 1417960655 J * gamingrobot_ sid10990@id-10990.highgate.irccloud.com 1417967511 N * Bertl_zZ Bertl 1417967513 M * Bertl morning folks! 1417967642 M * Ghislain ^^ 1417971324 J * Aiken ~Aiken@d63f.h.jbmb.net 1417974220 Q * FireEgl Read error: Connection reset by peer 1417975234 J * FireEgl ~FireEgl@173-23-76-11.client.mchsi.com 1417975315 Q * derjohn_mob Remote host closed the connection 1417975388 J * derjohn_mob ~aj@ip-178-203-221-8.hsi10.unitymediagroup.de 1417977604 Q * derjohn_mob Ping timeout: 480 seconds 1417983799 J * derjohn_mob ~aj@tmo-101-26.customers.d1-online.com 1417984757 J * beng_ ~BenG@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net 1417984779 Q * beng_ 1417984899 Q * jpierre03 Remote host closed the connection 1417984996 J * jpierre03 ~jpierre03@voyage.prunetwork.fr 1417985521 Q * Ghislain Quit: Leaving. 1417987023 Q * Aiken Ping timeout: 480 seconds 1417987250 Q * jpierre03 Ping timeout: 480 seconds 1417988237 J * jpierre03 ~jpierre03@voyage.prunetwork.fr 1417989237 J * Aiken ~Aiken@quarry.jbmb.net 1417989312 Q * bonbons Quit: Leaving