1506912878 J * fstd_ ~fstd@x5ce4922e.dyn.telefonica.de
1506913200 Q * fstd Ping timeout: 480 seconds
1506913201 N * fstd_ fstd
1506913521 Q * fstd Remote host closed the connection
1506913524 J * fstd ~fstd@x5ce4922e.dyn.telefonica.de
1506913939 Q * fstd Remote host closed the connection
1506913959 J * fstd ~fstd@x5ce4922e.dyn.telefonica.de
1506915225 J * fstd_ ~fstd@x5ce4c283.dyn.telefonica.de
1506915607 Q * fstd Ping timeout: 480 seconds
1506915607 N * fstd_ fstd
1506917840 J * fstd_ ~fstd@x4db6246c.dyn.telefonica.de
1506918227 Q * fstd Ping timeout: 480 seconds
1506918227 N * fstd_ fstd
1506918773 J * fstd_ ~fstd@x4e372431.dyn.telefonica.de
1506919092 Q * fstd Ping timeout: 480 seconds
1506919092 N * fstd_ fstd
1506922577 M * Bertl  off to bed now ... have a good one everyone!
1506922579 N * Bertl Bertl_zZ
1506927817 Q * aj__ Ping timeout: 480 seconds
1506930254 J * nikolay ~nikolay@149.235.255.3
1506932439 Q * Aiken Remote host closed the connection
1506932647 J * Aiken ~Aiken@d63f.h.jbmb.net
1506937117 M * Ghislain1 hello there. I have a fuzz in the 4.1.44 patching:checking file arch/parisc/kernel/syscall_table.S 
1506937117 M * Ghislain1 Hunk #1 succeeded at 358 with fuzz 1.
1506941749 M * Guy- Ghislain1: fwiw, I didn't encounter that fuzz (I patched up from 4.1.43+vs to 4.1.44) and my 4.1.44+vs kernel seems to work
1506941773 M * Guy- did you examine the patch/fuzz? it's probably harmless
1506942514 Q * Aiken Remote host closed the connection
1506942754 N * Bertl_zZ Bertl
1506942758 M * Bertl  morning folks!
1506944233 M * gnarface  morning Bertl!
1506944253 M * gnarface remember that machine i had with the bunk cpu?
1506944265 M * gnarface at half clock-speed, i got 578 days of uptime out of it
1506944289 M * gnarface rebooted for a kernel patch, forgot i never added the downclock commands to the boot up scripts, it didn't even last 8 hours
1506944300 M * gnarface seized right up
1506944307 M * gnarface definitely faulty cpu :(
1506944415 M * gnarface no problems since then though
1506944427 M * gnarface once i downclocked again (added to the bootup scripts this time)
1506945351 M * Bertl yup, I remember ;-)
1506945444 M * gnarface sorry to have wasted all your time chasing that
1506945460 M * gnarface i really appreciate *knowing* though
1506956797 Q * nikolay Quit: Leaving
1506960217 M * Ghislain1 Guy-: well yes it seems harmless but i prefer to tell because i am just a dumb sysadmin and i do not know if it is or not in reallity :)
1506960969 M * Bertl it doesn't hurt to check it ... even hunks which patch perfectly fine (but at an offset) could potentially end up in the wrong place (and already did, at least once :)
1506962026 M * Ghislain1 the patch seems to only do
1506962028 M * Ghislain1 -       ENTRY_SAME(ni_syscall)  /* 263: reserved for vserver */ 
1506962028 M * Ghislain1 +       ENTRY_DIFF(vserver)
1506962073 M * Ghislain1 it seems applied, so i dont know what's the fuzz about ( ;p )
1506962120 M * gnarface whitespace?
1506962421 M * Ghislain1 well i did not see any other difference
1506962556 M * Ghislain1 perhaps the lines are in different order
1506962646 M * Ghislain1 well no..
1506963311 M * Bertl you can easily check for whitespace fuzz by adding the --ignore-whitespace option to patch
1506963330 J * aj__ ~aj@p2003008E6C0FCF00187F8180E64A00CD.dip0.t-ipconnect.de
1506975647 J * fstd_ ~fstd@x5ce4a6da.dyn.telefonica.de
1506976034 M * Bertl  off to bed now ... have a good one everyone!
1506976036 N * Bertl Bertl_zZ
1506976037 Q * fstd Ping timeout: 480 seconds
1506976038 N * fstd_ fstd
1506977301 J * Aiken ~Aiken@d63f.h.jbmb.net