00:03:04 trying to copy over to /boot/efi/ 00:08:33 no go 00:43:18 anyone have alfonso siciliano's ear? re sysctltui, it needs 1 feature not listed in the update: search. put in a search query, and any sysctl in the whole mib that matches query is listed, in its hierarchy 01:36:01 having someone's ear would be evidence of a crime of mutilation. 03:00:04 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289220 03:00:49 Thanks for everyone helping out with my issue. It has been narrowed down to being a problem with SMP on my specific processor. I am going to try a different processor on my next day off... 03:12:59 SponiX: have you tried updating your bios? Assuming you have an update available. 04:29:46 kenrap: last BIO/UEFI update for this board was 2017 04:30:50 How's that so when your bios version data is "07/10/2019"? 04:32:57 LOL .. Maybe I am wrong on that 04:33:11 Anyway, I do have the "latest" one ever published for the board already installed 05:58:47 okay, I can boot FreeBSD up fine on this chip as long as Hyper Threading is disabled 06:18:35 SponiX, I normally disable Hyperthreading anyway for performance reasons. When I benchmarked CAD simulators they were about 5%-10% slower with HT on than off. Faster with HT off. So no loss to disable it. 06:21:17 rwp: it is a bit of a loss for me compiling software, so I will likely follow up with additional information added to my bug report, and hope it gets resolved. BUT, I am glad to have a booting FreeBSD without it in the mean time 06:42:48 Ouch, was hoping it won't be a SMP issue. But 20 (real) cores is still plenty 09:39:39 are jail resource constraints as accurate as vm resource constraints? asking because i wanna optimize some server software i run so i want to create a bunch of different instances of it with different build settings etc and see which variant runs most efficiently 09:39:50 and i have 1 big server to use for it so i gotta divvy that up somehow 10:48:13 What do you mean when you say "... as accurate as vm resource constraints?" ? 10:48:34 What are you comparing when looking for a difference in accurate results here. 11:29:16 i want to load test variant, then load test other variant, and go through each, and see how many requests/s each variant can handle. and i want to limit each variant to 1 core and some slice of ram 11:29:45 so if i base it on bhyve vms, each vm will get 1 cpu core to use, or if i base it on jails, each jail would get 1 core 11:30:07 but i just didn't know if i can limit a jail to exactly 1 core and xGB ram like i can do with bhyve vms 13:11:36 kerneldove: cpuset(1) might be of help 13:13:31 i read about that skull. if i go with jails for it, can you mix cpuset and rctl? 13:13:57 and how would i decide if i want to use cpuset with rctl or not? 15:16:56 well, that's weird. Installed on a new disk, set up samba to move configs over, attached the old disk, and now it boots the old disk. I cannot boot the old disk alone. I can ssh in, samba is running, but now my zraid won't show up. 15:19:51 nevermind, imported the zraid, working now. Now I have a weird hobbled system, but it's up for now. 16:00:52 kerneldove: i don't really have experience with it. I only tried (and failed) to limit memory for a jail once. but you definitely can assign a cpuset to a specific jail 16:01:04 or rather: specific jails 17:41:29 divlamir: Yeah, and I can continue to follow up on my bug report from FreeBSD itself now that this is figured out 17:46:45 SponiX: Might be a BIOS/UEFI bug, you can try switching between the two boot methods, if you have you boot drive setup to boot bothways 17:47:01 Check for BIOS updates too 17:59:28 divlamir: this is an X99 board from 2015 -- It has the latest bios published for it :P 18:00:01 I did try booting BIOS also. still does the same thing 18:02:29 Out of ideas for now. A verbose boot? Maybe it won't give much more info, given it's interrupted so early, but still.. 18:26:20 I will attach FreeBSD 14.3 inxi dmesg and anything else they ask for. And see if the bug report gets any traction 18:26:43 In the mean time I'll be back and forth between Fedora 42 and FreeBSD 14.3 18:27:16 I probably won't do CURRENT until I can have all my cores for building, OR beefy18 finishes pkg builds for it, so I can have some binary support 19:35:32 SponiX: I'm missing an argument for how does using CURRENT relates to building it with all cores? You'd often cross-platform-build it for low performance platforms. 19:38:32 regis: right now 15 Current/Pre-release doesn't have any binary packages available to it like 14.3 does. It will be several more days before beefy18 finishes its package builds and they are published 19:39:12 So, if I installed current again, I myself would be building packages for days again. and I don't have the motivation to do that. So, I can just continue with 14.3 and its binary pkg support to do my stuff 19:46:33 SponiX: Binary packages can be (as I understand but have no experience around) "cross"-build for low performance platform on a buffy hardware using other platform. 19:47:29 I mean, I don't imagine mis-using raspberry PI to build LLVM :( 19:49:15 SponiX: https://man.freebsd.org/cgi/man.cgi?poudriere 20:18:05 for resource limiting proc usage of a jail, what's the difference between using cpuset and rctl to get the job done?