Apparently the `--stress` parameter to https://github.com/ComputationalRadiationPhysics/cuda_memtest is what I was missing to diagnose the failing GPU, it identified a memory issue pretty quickly. Now to figure out if there is a Linux BadRAM alternative for GPUs...
Soooo, I've knowingly bought a cheap second-hand 1080Ti that's a bit "broken" - visual artefacts pop up on the screen occasionally, and I managed to lock up the system too (Doom on 1440p ultra - ran smoothly until it didn't). I ran cuda_memcheck and it showed no issues. Are there any GPU diagnostic tools that could identify what's wrong?
What ended up working is a) Setting "Table = off" in the Wireguard config, not to create the "move all traffic through Wireguard" routing rules, b) manually route traffic coming from wg0: "ip route add default via $WG0_IP dev wg0 table 1000; ip rule add from $WG0_IP table 1000"
The problem I had is that I need the "AllowedIPs = 0.0.0.0/0" since I want to be able to serve traffic "from everywhere" (federation FTW!). Unfortunately, when using 'wg-quick' it means that it will set up special routing rules to redirect *all* (even outgoing) traffic through Wireguard, and thus VPS. I noticed when Steam downloads became slow :) (yes, this server is also a gaming machine).
#wireguard shenanigans - I moved and I only have a "double carrier NAT" so no open ports, no public IP. I do have a VPS that I can use as a "bounce server" with port forwarding. I use Wireguard to keep my home server always connected to the VPS, and thus in theory forward server traffic back. Also in practice, since you see this post.
This is so much fun to play^H^H^H^Hexperiment with. Queue the wrath of #diyaudio forum members for not having a proper enclosure! 😆
"We didn't call it fuzzing back in the 1950s, but it was our standard practice to test programs by inputting decks of punch cards taken from the trash.
We also used decks of random number punch cards. We weren't networked in those days, so we weren't much worried about security, but our random/trash decks often turned up undesirable behavior.
Every programmer I knew used the trash-deck technique."
-- Gerald M. Weinberg
I've misconfigured power management on my laptop, it did not suspend and my kids discovered the magic of Xscreensaver. It's been keeping them entertained for 30min already. #betterthantv
Running gnome-control-center outside of Gnome (I'm using AwesomeWM) and the damn thing crashes on a panel? Well too bad, it remembers which panel you opened last, so it will keep segfaulting. Use this to reset the last panel so you can get back to settings again: $ gsettings set org.gnome.ControlCenter last-panel ''