08:01:10 rtprio: Wireguard is on the router and is NATing, but is also NATing traffic from the server, which therefore is causing traffic going to the server pass directly out without passing through the tunnel, because the wireguard endpoint == the server IP. I can think of one solution to this problem which would be split horizon dns, the DNS server matches against the wireguard subnet and returns the 08:01:12 private IP of the server on the network(s) 08:01:42 but this obviously would be a lot of work, so I am curious if there is any "hacks" to get it functioning now, and do it correctly later on 08:02:22 (My new server will have a different endpoint than the router which is how you should set it up, I was lazy and I have a block of /29 IPv4 addresses doing nothing :P) 12:56:38 i split my dns for this. 16:08:30 i know we can overprovision cpu with bhyve (like run 10 vms with 4 cores given to each even though i only have 24 cores) but can we overprovision ram? 16:08:44 we can overprovision disk with sparse vols in zfs or sparse flat files 16:08:48 ram is the 1 i don't know about 16:11:51 l00py: it doesn't support memory overcommit in the way that something like Hyper-V does where guests can balloon into available memory. if you don't wire the guest memory (bhyve -S) i believe it can be paged out, which is a sort of overcommit, but almost certainly not what you want 16:13:54 ya prolly not ok ty 18:16:28 I hope l00py is not wanting to overcommit RAM for VMs. I have suffered through using VMs where the hoster overcommited RAM and it's really painful and causes hard to diagnose slowness in the VM. 18:17:23 It's hard to diagnose because if you can only see the VM then the VM always thinks everything is perfect. All good. It is not paging itself. But the host is thrashing unseen on the host side. 18:43:10 Has anyone else had kernel panics with the 14.1 release? I even freebsd-updated to 14.1-p6 but I still get random panics on a new Alder Lake minipc (Intel N100). 18:44:44 FWIW the panics are mainly page faults, plus one pte related. Can provide more info if needed. Thanks. 18:46:43 kpel, Unfortunately that sounds like bad RAM. I would run it overnight with a memory test in order to check for it. 18:47:18 rwp: memtest86 thinks ram is ok. Did 4 passes without issue. 18:47:35 memtest86 is pretty good. 18:47:42 rwp: also, smartctl doesn't show disk issues 18:49:20 Are you using a graphics driver from binary pkg install? Sometimes that is a source of kernel panics due to it being a separate compilation. 18:50:03 There are various situations where the kernel API changes in incompatible ways and the pkg binary driver needs to be recompiled to match. I have experienced that in 13. 18:50:51 And that is the last of my knowledge about this. I have told you more than I know and will wait for others to jump in. 18:51:37 rwp: I am using i915kms. The thing is, I was seeing this issue even before I got X running. I see it even when I login over ssh. Anything that is io-intensive can trigger a panic. A pkg install with lots of dependencies, an nmap run... sometimes I get a panic simply by opening and closing chromium. 18:53:12 How are you loading the i915kms driver? In /etc/rc.conf in kld_list="i915kms" ?? In that case it will always load even when you are logging in from ssh. 18:53:26 rwp: I cloned the git repo and did make buildworld. Would that build i915kms as well or do I need to build the port? 18:54:26 I am using the radeonkms here and the radeonkms is a port and needs to be built separately. I don't know about the i915kms as I have different hardware. I expect is a port as well. 18:55:42 For a test if you can do it I suggest removing kld_list="i915kms" to avoid loading it, not starting X, using it only over ssh and see if the kernel panics stop happening. That would point me that direction if the panics don't happen when not loading that module. 18:55:51 rwp: I might give that a go later, thanks. I checked the freebsd forums and found a couple of similar panic reports but they seem to be years old. I wasn't sure if I'm looking at the same issue. 18:55:53 graphics/drm-stuff has been removed from the base long time ago 18:56:16 mzar: thanks 18:56:18 Then it is definitely a port and would need to be built separately. 18:56:40 The kernel module in ports causing problems is one of the well known problems. 18:56:52 rwp: will do, thanks for the tip 18:57:03 if drm module is the culprit, it will crash on load, immadiately 18:57:29 kpel: enable kernel core dumps and debug it 18:58:08 no, it doesn't crash immediately. The X session can happily stay up overnight with applications open. And then I'll do something trivial like open a second browser, or close an open browser, and everything wil freeze for a few seconds, then the reboot follows. 18:58:20 The binary pkgs are compiled on a build server that builds for the oldest supported active FreeBSD release. So for 14.1-RELEASE-p5 that is 14.1-RELEASE as in p0 I think. If any incompatible ABI changes have crept into the kernel since then it creates this mismatch problem. 18:58:32 kpel: you need sth like "dumpdev="/dev/swappartion" to make it working 18:58:50 it should be added to /etc/rc.conf 18:59:08 mzar: are you referring to the cores I have in /var/crash ? 18:59:16 yep 18:59:21 mzar, Actually I know from personal experience that I could load the radeonkms module and it would not crash until I started X and then it would crash immediately. 18:59:23 do you have them ? 18:59:24 no debug symbols :( 18:59:48 so I rebuilt GENERIC and now I have debug info for a couple of crashes 19:00:31 panics could be also related to faulty hardware 19:00:56 rum memtest at least 19:02:26 mzar: did that. Passed 4 runs 19:05:06 I even tried running a GENERIC-KASAN kernel for a few hours. I have an output file, I just don't know where to focus. It doesn't show any out-of-bounds access if I read it correctly. 19:05:23 would it help if I pasted it on pastebin? 19:08:12 it's only 4852 lines :P 19:11:16 hhelo 19:11:36 how do I switch from my compiled kernel to default, binary kernel with default config? Because I need to do freebsd-update 19:11:58 kpel: good 19:12:23 i think you can just re-build the generic kernel 19:12:59 kpel: maybe you want to test 14-2-BETA ? a lot of things were fixed and changed 19:13:00 rtprio: if I download freebsd-update, it updates the /usr/src/sys kernel sources as well? 19:13:16 so I can rebuilt from my config 19:13:50 ScrewDriver1337: you can tell freebsd-update what FreeBSD version you are using 19:13:55 you can even lie 19:14:05 yeah sure 19:14:11 but I just wanna download security patches and such 19:14:12 mzar: I'll add 14.2-BETA to the possible things to try, thanks. Right now I'm rebooting the "patient" without i915kms. 19:16:27 mzar: sometimes even a "find /usr -name '*cpu*'" over ssh would cause a panic. It looks like disk io/vfs related but I don't know enough to say so. 19:19:11 kpel: are you using ZFS ? 19:19:23 mzar: nope. ufs+ffs 19:19:46 mzar: /dev/ada0p2 on / (ufs, local, soft-updates, journaled soft-updates) 19:20:24 interesting 19:28:36 mzar: btw thx for the tip with freebsd-update fake version. Because I got cursed VM running 14.1-STABLE 20:10:17 is there a way to see which version of the OS compiled without doing installworld and installkernel? 20:10:47 you mean like `freebsd-version `? 20:11:27 well, i would like to know which version was compiled without running installworld and installkernel 20:12:10 to see if the compiled version is actually a significant update 20:47:44 I'm having trouble with a portable monitor (via DisplayLink). Is there a particular channel where it'd be appropriate to inquire about that? 20:49:55 from what i've seen, here seems like a good place fm2279 20:52:12 jauntyd: what are going to compare ? git hashes ? __FreeBSD_version numbers ? 20:53:08 jauntyd: take a look at /usr/src/sys/conf/newvers.sh /usr/src/sys/sys/param.h 20:54:41 Thanks, scoobybejesus. I'm trying to connect a USB monitor (an AOC E1659FWU). Upon plugging the device in, I see it recognized as a DisplayLink USB devince (in dmesg). I have loaded the udl kernel module. But nothing happens after the USB connection. I've read conflicting suggestions in the forums. Wondering if anybody here has wrestled with a display like this. 21:10:01 mzar: newvrs.sh is great. ty 21:19:47 hii 21:19:52 anyone offering vps? 21:32:03 ash_11: https://forums.freebsd.org/threads/freebsd-hosting-shared-vps-etc.21472/ 21:33:13 i need free 21:33:17 vps 21:41:38 ash_11: you can sign up for an oracle cloud account and get 2 amd64 vps or 1 big arm vps 21:41:41 free 21:41:56 does it require cc 21:42:06 $1 verification charge 21:42:18 :( 21:42:24 don't have cards 21:42:29 working 21:42:35 it's to prevent script k1ds 21:56:57 say, do I need to do something special to make sure that WOL works? 21:58:41 rtprio can you provide a registered account 21:58:50 im from ukraine and i cant 22:01:25 sorry, i'm already using my two vps 22:02:05 can you arrange one? 22:04:28 uh no. maybe use this opportunity to install freebsd on one of your own systems