On Wed, 2018-06-13 at 03:58 +0200, Jason A. Donenfeld wrote: > Hi Paul, > > The current patch I'm now considering is here: > https://git.zx2c4.com/WireGuard/patch/?id=17fb4ff6064e10bb91bf2ccf653 > 4bfdf767a9b90
Ahh! Last night I recompiled with your first patch and left the machine running - this morning it was frozen again :( prh@brix:~$ sudo modinfo /lib/modules/4.16.0-2-rt- amd64/updates/dkms/wireguard.ko filename: /lib/modules/4.16.0-2-rt- amd64/updates/dkms/wireguard.ko alias: net-pf-16-proto-16-family-wireguard alias: rtnl-link-wireguard version: 0.0.20180531-1 author: Jason A. Donenfeld <ja...@zx2c4.com> description: Fast, secure, and modern VPN tunnel license: GPL v2 srcversion: 6BC9480277BB8058D75035C depends: udp_tunnel,ip6_udp_tunnel retpoline: Y name: wireguard vermagic: 4.16.0-2-rt-amd64 SMP preempt mod_unload modversions But although the machine froze I dont see the BUG's in the kernel log. So honestly I'm wondering if that freezing is just a coincidence with the bug you found since I didnt see a BUG... However I could run the non-rt kernel for 13 days without freeze but cant run the -rt- kernel without freezing for more than a few hours. Do you think think the bug could cause that? I need to run the non-rt today to get some work done and I'll run the -rt- with the new patch this evening if thats ok. The other "weird" errors are there, but I've just rebooted to the non- rt kernel and I'm getting those "ERROR block_reap:328: [bandwidth] bad exit code 1" a lot still... but searching specifically on those is pointing to i3blocks... indeed killing i3blocks does stop them, so something in my i3blocks config is screwy. Woops! I was confused because the logs show them being trapped by gdm3. Many thanks for your help and brilliant code. _______________________________________________ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard