Re: Is there a way to tell poudriere to allocate more memory to a pkg build?

Hello, On Fri, 23 May 2025, at 18:45, Dennis Clarke wrote: > I have been watching qt6-webengine-6.8.3 fail over and over and over > for some days now and it takes with it a pile of other stuff. I'm using a dual xenon @3GHz with 512GB ram for amd64 poudriere builds. This has hyperthreading turned

Re: Is there a way to tell poudriere to allocate more memory to a pkg build?

> PARALLEL_JOBS=3 # this appears to help avoid conflicts, and gives > appreciable speedups. > ALLOW_MAKE_JOBS=yes > MAX_FILES=8192 > > MUTUALLY_EXCLUSIVE_BUILD_PACKAGES="irid* llvm* rust* gcc* electr* > libre* firef* npm* node* nerd* qt* ghc webkit*" # this also helps avoid > conflicts > > TMPFS

Re: epair(4)

On Fri, May 23, 2025 at 09:36:22AM +0200, Patrick M. Hausen wrote: If I did not get this conversation entirely wrong, the problem is exactly that there are probably many people running an unsupported configuration without knowing. How to reach them? I think an entry on the 15.0-RELEASE page,

Re: epair(4)

On Thu, May 22, 2025 at 11:06:46PM +0200, Patrick M. Hausen wrote: "The documentation was on display in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of the Leopard.'" I enjoyed this reference :D --

Re: epair(4)

On Thu, May 22, 2025 at 07:40:52PM +0200, Patrick M. Hausen wrote: The handbook has always been clear about the only correct way to configure a bridge and member interfaces since the introduction of if_bridge(4) and the removal of the previous bridge(4) in 2007: https://svnweb.freebsd.org/doc/h

Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument”

On Thu, May 22, 2025 at 08:09:13PM +0100, Lexi Winter wrote: as kp said, this is broken, but you can trivially fix it by moving the IP addresses to the bridge interface instead. note that for SLAAC to work on a bridge, you have to set ‘accept_rtadv’ and ‘auto_linklocal’ on the bridge interface

Re: Updating build and jail manual pages to include missing or obscure information

On Thu, May 22, 2025 at 07:56:38AM -0600, Warner Losh wrote: I object to removing these. I do agree we should document other methods, but my spidt sense is this is still in use... I object also. `make kernel` is useful if only for that by using it, one doesn't need to type `make buildkernel &&

Re: epair(4)

On Fri, May 16, 2025 at 09:21:29PM +0100, Lexi Winter wrote: i am not sure about this. i admit i have not done a survey :-) however, i believe most people using jails or bhyve are not affected. the Handbook is clear about the correct way to configure this[0], so people who followed the handboo

Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument”

On Wed, May 21, 2025 at 04:44:46PM +0200, Kristof Provost wrote: [2] because here bge1 has an ip addigned to it and is a bridge member Yes, that is a problem. Assign REDACTED.REAL.IP to bridge1, not to bge1. Oof! Thank you for clarifying. I'm glad I asked. This bhyve host was set up followi

Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument”

On Mon, May 19, 2025 at 11:33:50AM +0100, Lexi Winter wrote: although it's possible everyone who is affected by this is already aware of the change, i thought i should send a heads up anyway, if only to have a single place to discuss this (since there was quite a lot of discussion). in short, fo

Re: pkg: invalid option --, and pkg: illegal option --

On Fri, May 02, 2025 at 07:32:34AM +0100, Graham Perrin wrote: root@mowa219-gjp4-zbook-freebsd:~ # pkg version -C -vRL= | grep -v orphaned pkg: invalid option -- C pkg: invalid option -- v pkg: invalid option -- R pkg: invalid option -- L pkg: invalid option -- = how odd. I'd try re-making pkg

Re: zfs (?) issues?

On Sat, Apr 26, 2025 at 03:01:01PM +0300, Sulev-Madis Silber wrote: that might be it!? there is hdd on machine that was tested but now never really likes to complete the long smart tests, and short take ages. there are no "usual" disk errors, tho. that hdd is part of 2 disk mirror that the gi

Re: zfs (?) issues?

On Mon, Apr 21, 2025 at 04:25:16AM +0300, Sulev-Madis Silber wrote: i have long running issue in my 13.4 box (amd64) others don't get it at all and only suggest adding more than 4g ram it manifests as some mmap or other problems i don't really get basically unrestricted git consumes all the me

Re: March 2025 stabilization week

Hi Gleb, On Mon, Mar 24, 2025 at 09:55:33PM -0700, Gleb Smirnoff wrote: I don't know about the 14.2 -> 15.0 upgrade path. The report sounds like a problem that definitely needs to be fixed. But it is out of scope of stabilizatoin weeks, which track CURRENT users. However, given that a STABLE

Re: March 2025 stabilization week

Hi Gleb, On Mon, 24 Mar 2025, at 08:00, Gleb Smirnoff wrote: > Hi FreeBSD/main users & developers: > > This is an automated email to inform you that the March 2025 stabilization > week > started with FreeBSD/main at main-n276073-67c1c4dfd1cc, which was tagged as > main-stabweek-2025-Mar. >snip<

Re: FreeBSD on a Lenovo T400s, GUI suggestions needed

On Fri, Jan 17, 2025 at 09:42:38AM -0800, bob prohaska wrote: Can anybody suggest a suitable X11-wm to try on this quite elderly laptop? LXQT failed with a core dump, next I'll try twm while hoping for a better suggestion. x11-wm/windowmaker I use this on any low-end hardware which needs a wm

Re: speedup build time

On Wed, Oct 30, 2024 at 12:53:01AM +0100, Olivier Cochard-Labbé wrote: On Wed, Oct 30, 2024 at 12:21 AM void wrote: this is interesting How do you use 'buildworld-jobs' ? make buildworld buildworld-jobs? make buildworld-jobs buildworld? make buildworld-jobs buildkernel-jobs

Re: speedup build time

On Tue, Oct 29, 2024 at 03:52:24PM -0700, Simon J. Gerraty wrote: Maku Bex wrote: * What (if any) "max_jobs" (make's "-j" parameter) are you using? 16 BTW if you use 'buildworld-jobs' jobs.mk will default to -j 1.33C (1.33 * ncpu) and also save the output to ../buildworld.log this is inter

Re: speedup build time

On Mon, Oct 28, 2024 at 02:23:06AM +, void wrote: make -j16 buildworld make -j16 kernel should read 'make -j16 buildworld && make -j16 kernel' --

Re: speedup build time

On Sun, Oct 27, 2024 at 07:00:17PM -0500, Maku Bex wrote: Hello, I'm trying to figure out a way to decrease build time of -CURRENT and/or -STABLE but it is not working out that well. * Tuning /etc/make.conf and /etc/src-env.conf based on their manpages (make.conf(5), make(1), src.conf(5))

Re: Build failure in share/examples/tests/tests/googletest/sample1_unittest.full

On Sun, Oct 20, 2024 at 05:14:29AM -0700, David Wolfskill wrote: This is in meta-mode, on a 32x2 Epyc running "make -j 112 buildworld". I'm just guessing here - but ISTR that with large -j that sometimes a build failure can occur. I've just had one where I forgot where I was and ran a -j10 bui

Re: new tls-cert-store and cert-bundle methods

On Mon, Oct 14, 2024 at 09:40:38AM +0200, Dag-Erling Smørgrav wrote: void writes: Now that we have system tls-cert-store, if one needs to reference a tls-cert-bundle like provided by ca_root_nss, do we need to concatenate all of the certs listed in /usr/share/certs/trusted into, for example

Re: weekly locate error Was: September 2024 stabilization week

On Mon, 30 Sep 2024, at 22:32, Kyle Evans wrote: > - install $tmp $FCODES > + cat $tmp > $FCODES thank you! --

Re: weekly locate error Was: September 2024 stabilization week

On Mon, Sep 30, 2024 at 02:08:18PM -0700, Gleb Smirnoff wrote: M> > Manual run of the periodic job doesn't reproduce the problem :( M> M> Backing out commit f62c1f3f8e91c78d402e1db4e518e4899a4ba2b9 resolves it for M> me, Sorry but I'm quite dense regarding git. Can you describe how exactly wha

Re: September 2024 stabilization week

On Sun, Sep 29, 2024 at 10:21:57AM -0400, Michael Butler wrote: This happens on all my amd64 -current installs. really!!! Maybe I missed domething in the etcupdate on my -current amd64 instances --

Re: Is INET6 a required option these days? (kernel build failure)

On Sun, Sep 29, 2024 at 02:13:01PM +, Gary Jennejohn wrote: I personally have been using a customized kernel configuration file for 25 years or more and I have no intention of changing it. Just because INET6 shows up in all the boilerplate config files doesn't change the fact that INET6 is

Re: September 2024 stabilization week

Hello Gleb, On Wed, Sep 25, 2024 at 01:32:59PM -0700, Gleb Smirnoff wrote: On Mon, Sep 23, 2024 at 01:00:11AM -0700, Gleb Smirnoff wrote: T> This is an automated email to inform you that the September 2024 stabilization week T> started with FreeBSD/main at main-n272449-6e414739fc95, which was t

sccache-overlay and different major os versions

Hello, am asking this here because I guess most of you will be familiar with building in poudriere. Is it expected that using sccache-overlay will work when the host is running current but the builder is for example a 14.1-p6 poudriere jail? errors like [00:00:03] ==> Starting sccache [00:00:03

Re: change in /usr/bin/bc with CTRL-d no longer exit

On Mon, Sep 16, 2024 at 12:08:48AM +0100, void wrote: [void@vm5 ~ ] uname -KU 1400504 1400504 [void@vm5 ~ ] echo 2+2 | bc -l 4 [void@vm3 ~ ] uname -KU 1500023 1500023 [void@vm3 ~ ] echo 2+2 | bc -l 4 other replies way faster than mine :D the -current was built yesterday --

Re: change in /usr/bin/bc with CTRL-d no longer exit

on their system. [void@vm5 ~ ] uname -KU 1400504 1400504 [void@vm5 ~ ] echo 2+2 | bc -l 4 [void@vm3 ~ ] uname -KU 1500023 1500023 [void@vm3 ~ ] echo 2+2 | bc -l 4 --

Re: Loader needs to be updated message

On Sun, Sep 08, 2024 at 11:23:46AM -0600, Warner Losh wrote: Great. This warning is new so people keep things uptodate. There has been minor breakage due to really old loader.efi not updating, but i backed that silent (mostly) breakage and added the loud version thing you see now. It shouldn't b

Re: Loader needs to be updated message

On Sun, Sep 08, 2024 at 09:14:50AM -0600, Warner Losh wrote: On Sun, Sep 8, 2024, 7:50 AM void wrote: Do you think a source upgrade on the server would fix the issue? Yes. But the warning at this time isn't super urgent for you. It is telling you of problems in the future. Can co

Re: Loader needs to be updated message

On Sun, Sep 08, 2024 at 09:14:50AM -0600, Warner Losh wrote: On Sun, Sep 8, 2024, 7:50 AM void wrote: Do you think a source upgrade on the server would fix the issue? Yes. But the warning at this time isn't super urgent for you. It is telling you of problems in the future. relate

Re: Loader needs to be updated message

On Sat, Sep 07, 2024 at 09:34:27PM -0600, Warner Losh wrote: Yes. If you are getting the too old error, then there is a preupdate world booting a stable/13 after my change I think. Warner So, on the server (15.0-CURRENT #0 n270917-5dbf886104b4: Thu Jul 4 ) ls -lah /boot/gptzfsboot -r--r--r-

Re: Loader needs to be updated message

SP) to kick the guests? If so, version mismatch happenes, but newer kicks older. But yes, usually it is not at all the problem, as newer loader codes in same interpreter (lua/4th) is keeping backward compatibilities, I guess. Another case is that void already stated that In such a case, you might

Re: Loader needs to be updated message

On Sat, Sep 07, 2024 at 11:47:12AM -0600, Warner Losh wrote: Wait. On the guest? Then what's the VM system you're using? Warner Bhyve. The server is freebsd-current. The guest is 13.2-stable. I see the error in the ascii beastie menu when booting the guest with vmrun.sh --

Re: Loader needs to be updated message

On Sat, Sep 07, 2024 at 08:20:07AM -0700, Mark Millard wrote: I'm more interested in what is there than just what is not there. May be show something analogous to: # gpart list | grep -E '(Name|type|efi|media)' 1. Name: mmcsd1s1 efimedia: HD(1,MBR,,0x8000,0x3b68000) rawtype: 12 t

Re: Loader needs to be updated message

hello again, On Fri, Sep 06, 2024 at 03:13:59PM -0700, Mark Millard wrote: What shows if you do the likes of (showing an amd64 context example): # ls -lah /boot/efi/efi/*/* -r-xr-xr-x 1 root wheel 643K Aug 24 05:32 /boot/efi/efi/BOOT/bootx64.efi -rwxr-xr-x 1 root wheel 643K Aug 24 05:32 /b

Re: Loader needs to be updated message

On Fri, Sep 06, 2024 at 03:13:59PM -0700, Mark Millard wrote: What shows if you do the likes of (showing an amd64 context example): # ls -lah /boot/efi/efi/*/* -r-xr-xr-x 1 root wheel 643K Aug 24 05:32 /boot/efi/efi/BOOT/bootx64.efi -rwxr-xr-x 1 root wheel 643K Aug 24 05:32 /boot/efi/efi/FR

Re: Loader needs to be updated message

On Sat, Sep 07, 2024 at 02:50:52AM +0900, Tomoaki AOKI wrote: Some additional explanation. Before, loader.efi itself could not be kicked directly from UEFI firmware and needs boot1.efi to kick loader.efi. In this case, boot code in ESP (uEFI System Partition, formatted with FAT32, 16 or possibl

Re: Loader needs to be updated message

On Fri, Sep 06, 2024 at 09:00:58AM -0600, Warner Losh wrote: man loader.efi has the instructions. I followed the instructions: # gpart list | grep -Ew '(Name|efi)' 1. Name: da0p1 type: efi 2. Name: da0p2 3. Name: da0p3 1. Name: da0 The manpage says: " Second, let's mount the

Re: Loader needs to be updated message

On Fri, Sep 06, 2024 at 08:25:16AM -0600, Warner Losh wrote: On Fri, Sep 6, 2024 at 8:13 AM void wrote: Hi, when booting -current (arm64) after building world & friends and rebooting, the beastie menu shows "Loader needs to be updated". I presume this to be gptzfsboot because

Loader needs to be updated message

Hi, when booting -current (arm64) after building world & friends and rebooting, the beastie menu shows "Loader needs to be updated". I presume this to be gptzfsboot because the system is root-on-zfs. The issue I'm having is that I can't see in the manpage how to actually update it. The system

a zfs thank you :)

Hi, I was pleasantly surprised when I installed a new [1] zfs-on-root -current to rpi4 that when adduser was invoked, I was given the option to encrypt the homedir. This is a great feature for my context [2]. It doesn't automount on boot but I think this is more of a feature rather than a bug

aesni_load present in /boot/loader.conf on arm64

Hi, Looking at man 4 aesni it appears this pertains to intel and AMD only? is its prescence on arm64 a bug? It seems to be added to /boot/loader.conf by default. The method I used to install is to boot to the latest snapshot at the time, then plug in a usb3 disk, ran bsdinstall to that disk, re

Re: setting the console to serial by defailt seems to not work

On Tue, Jul 30, 2024 at 08:55:22PM +0200, Dag-Erling Smørgrav wrote: void writes: The arm64 device is headless and i connect to it via serial. I noticed the beastie menu come up with the option Video for console. Cycled it to Serial, booted, all fine. [...] man boot.config Thank you for

Re: filemon

On Tue, Jul 30, 2024 at 11:57:07PM +0900, Tomoaki AOKI wrote: Another aspect is that loading multiple too large modules easily makes boots crash. Staging area (memory region which loader allocates to load kernel and modules, and maybe configured buffers) is limited. This is why I went looking

setting the console to serial by defailt seems to not work

Hi, I have an rpi4 arm64 device at n271321-9ae91f59c500 and an amd64 image running in screen(8) as zvol-backed vm at n271360-82283cad12a4 The arm64 device is headless and i connect to it via serial. I noticed the beastie menu come up with the option Video for console. Cycled it to Serial, booted

Re: filemon

Hi, On Tue, 30 Jul 2024, at 10:10, Dag-Erling Smørgrav wrote: > void writes: >> How would I go about remedying the issue that usage/examples >> are not present in manpages for either the device line in kernel >> config or filemon.ko ? > > https://reviews.freebsd.org/D46184 thank you!

Re: filemon

How would I go about remedying the issue that usage/examples are not present in manpages for either the device line in kernel config or filemon.ko ? --

rebuilding with zfs-on-root on arm64

Hi, What/where are the full instructions for installing new kernel and world in a rpi4/arm64 zfs context? I'm looking for instructions that would account for u-boot, zfs and zfs encryption. --

Re: filemon

On Sat, Jul 27, 2024 at 03:01:22PM +, Gary Jennejohn wrote: filemon is not a device, it's an option. So you can't have "device filemon" in your kernel config file. man 4 filemon has the following NAME filemon – the filemon device [...] DESCRIPTION The filemon device allows a

Re: filemon

On Sat, Jul 27, 2024 at 03:01:22PM +, Gary Jennejohn wrote: filemon is not a device, it's an option. So you can't have "device filemon" in your kernel config file. I compile it with makeoptions MODULES_OVERRIDE="filemon ..." in my kernel config file. What's the actual line in your kernel

filemon

Is it better to load filemon as kldload filemon, or to have it set as a device via 'device filemon' in the kernel config file? or to just load it when rebuilding the system? There is man 4 filemon but nothing there to describe usage as .ko or device. System is n271321-9ae91f59c500 on arm64. --

Re: May 2024 stabilization week

On Sat, Jun 01, 2024 at 03:13:23PM -0400, Mike Karels wrote: Sorry, this is a different instance of the problem that pkg had with its scripts. This is fallout from removal of security_daily_compat_var. The 900.tcpwrap script was modified for this in April. Did you run etcupdate? yes - etcupda

Re: May 2024 stabilization week

Hi Mike, On Sat, Jun 01, 2024 at 08:06:53AM -0400, Mike Karels wrote: On 30 May 2024, at 8:31, void wrote: On Mon, May 27, 2024 at 09:24:14PM -0700, Gleb Smirnoff wrote: Replying to this email thread with your success reports as well as reporting any regressions is very much appreciated

Re: May 2024 stabilization week

On Mon, May 27, 2024 at 09:24:14PM -0700, Gleb Smirnoff wrote: Replying to this email thread with your success reports as well as reporting any regressions is very much appreciated. Thanks! This is new. In the daily security run output (arm64.aarch64): /etc/periodic/security/900.tcpwrap: secu

Re: May 2024 stabilization week

Hi Gleb, On Mon, May 27, 2024 at 09:24:14PM -0700, Gleb Smirnoff wrote: Replying to this email thread with your success reports as well as reporting any regressions is very much appreciated. Thanks! Works fine, no issues on arm64.aarch64 where it's running nginx, monit and a poudriere instanc

Re: pkg server for current/arm64 stopped ? [main-armv7 on ampere2, elapsed so far: 651:21:56]

On Thu, Apr 18, 2024 at 08:02:30AM -0700, Mark Millard wrote: void wrote on Date: Thu, 18 Apr 2024 14:08:36 UTC : Not sure where to post this.. The last bulk build for arm64 appears to have happened around mid-March on ampere2. Is it broken? main-armv7 building is broken and the last

new tls-cert-store and cert-bundle methods

Hello, Now that we have system tls-cert-store, if one needs to reference a tls-cert-bundle like provided by ca_root_nss, do we need to concatenate all of the certs listed in /usr/share/certs/trusted into, for example cert.pem then symlink /etc/ssl/cert.pem to that concatenated file? thanks in ad

Re: make buildworld failure on arm64 on -current n267777

On Fri, 26 Jan 2024, at 00:14, void wrote: > In /usr/src # git rev-list --count --first-parent HEAD > 26 in /usr/src, a 'git reset --hard' followed by 'git pull' and then 'git checkout main' fixed this. For some reason, 'git pull --ff-only

Re: meta mode

On Sat, 27 Jan 2024, at 13:59, Warner Losh wrote: > Approximately never. The only time I've had issues were when the > machine crashed due to sudden power failure during the build which lead > to the last few .o files to be zero length with UFS. > > Non clean normal builds have lots of issues wi

Re: meta mode

Hi, On Sat, 27 Jan 2024, at 13:51, Lexi Winter wrote: > the (easiest) fix for that is to do a full rebuild every time > __FreeBSD_version changes. > > pkg(8) bug report: https://github.com/freebsd/pkg/issues/2162 > > i don't know if meta mode will catch this and rebuild correctly, but > since thi

meta mode

Hi, I use meta-mode in /etc/src-env.conf so that if (for example) a small change in the kernel config is made, the machine doesn't take hours recompiling. Also, (I *think* it works this way) if src gets updated by git and world/kernel rebuilt it won't recompile already compiled files provided I

make buildworld failure on arm64 on -current n267777

In /usr/src # git rev-list --count --first-parent HEAD 26 include/machine -> /usr/src/sys/arm64/include Building /usr/obj/usr/src/arm64.aarch64/stand/efi/loader_4th/vers.c Building /usr/obj/usr/src/arm64.aarch64/stand/efi/loader_4th/8x16.c Building /usr/obj/usr/src/arm64.aarch64/stand/efi/l

Re: loading vmm.ko crashes main-n267684-e4b646ce1610

On Thu, Jan 25, 2024 at 03:34:54PM +0800, Zhenlei Huang wrote: You may want to configure the dump device before get the coredump. See https://docs.freebsd.org/en/books/developers-handbook/kerneldebug/#kerneldebug-obtain

loading vmm.ko crashes main-n267684-e4b646ce1610

Hello, Loading vmm either via vmm_load=YES in /boot/loader.conf or manually via kldload vmm crashes the system to db> prompt as shown in the link below: http://void.f-m.fm.user.fm/Screenshot_20240122_135539.png Thing is, access is via a html5 console with no up/down scrolling or buffer. Nothing

Re: vmm_load crashes to debugger early

Hi, On Mon, 22 Jan 2024, at 12:48, Ronald Klop wrote: > Hi, > > Can you mount /boot on another system? not sure how as the system cannot find the pool called 'zroot'. There are two zpools on the server - zroot for HD and 'ssd' for the ssds. I can boot to -current usb stick and zpool import -f ss

vmm_load crashes to debugger early

Hello, On a very recent -current, vmm_load="YES" in /boot/loader.conf crashes the system to debugger early on in the boot sequence. I can't even reach single user mode How can I prevent this one element of /boot/loader.conf from loading? thanks in advance for any advice --

Re: bsdinstall use on rpi4

On Sat, Jan 13, 2024 at 08:24:13AM -0800, bob prohaska wrote: On Sat, Jan 13, 2024 at 03:26:19PM +, void wrote: Hi, I'm trying to use bsdinstall on FreeBSD-15.0-CURRENT-arm64-aarch64-RPI-20240111-a61d2c7fbd3c-267507.img to install to usb3-connected HD, using the 'expert mod

bsdinstall use on rpi4

Hi, I'm trying to use bsdinstall on FreeBSD-15.0-CURRENT-arm64-aarch64-RPI-20240111-a61d2c7fbd3c-267507.img to install to usb3-connected HD, using the 'expert mode' for UFS, after having initially booted from mmcsd. The goal is to boot to usb3 with freebsd on UFS filesystem, and to have that f

Re: poudriere: swap_pager: out of swap space

On Thu, Jan 11, 2024 at 02:21:19AM +, Lexi Winter wrote: hi list, i'm having a recurring problem with poudriere that i hope someone might have an idea about. i'm building packages with poudriere on a system with 32GB memory, with tmpfs and md disabled in poudriere (so it's using ZFS only) a

Re: route ipv6 errors on bootup in -current main-n267425-aa1223ac3afc on arm64

On Tue, Jan 09, 2024 at 12:24:40PM +, void wrote: On Tue, Jan 09, 2024 at 10:24:53AM +, void wrote: On Mon, Jan 08, 2024 at 01:07:30PM -0800, Enji Cooper wrote: Was the kernel/utility built with IPv6? If not, that’s a general bug which should be filed (which can be easily checked

Re: route ipv6 errors on bootup in -current main-n267425-aa1223ac3afc on arm64

On Tue, Jan 09, 2024 at 10:24:53AM +, void wrote: On Mon, Jan 08, 2024 at 01:07:30PM -0800, Enji Cooper wrote: Was the kernel/utility built with IPv6? If not, that’s a general bug which should be filed (which can be easily checked/avoided using the FEATURES(9) subsystem)… Cheers! -Enji

Re: noatime on ufs2

On Tue, Jan 09, 2024 at 09:47:59AM +0100, Olivier Certner wrote:i So, to me, at this point, it still sounds more than a gimmick than something really useful. If someone has a precise use case for it and motivation, than of course please go ahead. The only use-cases I [1] can think of are eit

Re: noatime on ufs2

On Mon, Jan 08, 2024 at 12:41:02PM -0800, Xin LI wrote: On Sun, Jan 7, 2024 at 5:27 AM void wrote: Hi, Does /var/mail still need atime? I've installed a ufs2-based -current main-n267425-aa1223ac3afc on rpi4/8BG which installs into one / . If it's mounted with noatime, wi

Re: route ipv6 errors on bootup in -current main-n267425-aa1223ac3afc on arm64

On Mon, Jan 08, 2024 at 01:07:30PM -0800, Enji Cooper wrote: Was the kernel/utility built with IPv6? If not, that’s a general bug which should be filed (which can be easily checked/avoided using the FEATURES(9) subsystem)… Cheers! -Enji world/kernel was built with WITHOUT_INET6= in /etc/src

route ipv6 errors on bootup in -current main-n267425-aa1223ac3afc on arm64

Hi, on a rpi4/8GB, my rc.conf looks like so. It's an ipv4-only system on a LAN not directly connected to the internet hostname="generic.home.arpa" ifconfig_genet0="inet 192.168.1.199 netmask 255.255.255.0" defaultrouter="192.168.1.1" sshd_enable="YES" sendmail_enable="NONE" sendmail_submit_ena

noatime on ufs2

Hi, Does /var/mail still need atime? I've installed a ufs2-based -current main-n267425-aa1223ac3afc on rpi4/8BG which installs into one / . If it's mounted with noatime, will it have consequences for /var/mail ? --

Re: Request for Testing: TCP RACK

On Thu, Nov 16, 2023 at 10:13:05AM +0100, tue...@freebsd.org wrote: You can load the kernel module using kldload tcp_rack You can make the RACK stack the default stack using sysctl net.inet.tcp.functions_default=rack Hi, thank you for this. https://klarasystems.com/articles/using-the-freebsd

odd bhyve guest message (Khelp module "ertt" can't unload)

I'm seeing this message on exit from a 14.0-RC1 guest on a host running main-n265915 when it exits normally (via poweroff within the guest): pflog0: promiscuous mode disabled Waiting (max 60 seconds) for system process `vnlru' to stop... done Waiting (max 60 seconds) for system process `syncer' t

Re: nvme timeout issues with hardware and bhyve vm's

On Sun, 15 Oct 2023, at 15:53, Warner Losh wrote: > The one with the uboot traceback? I can't help you there. The report is > confusing. I don't know the error / problem being reported to even know > what to look at. Or is it a different thing? I'm so confused at this > point. I also think we

Re: nvme timeout issues with hardware and bhyve vm's

On Sun, 15 Oct 2023, at 15:35, Warner Losh wrote: > I've fixed all known nvme issues in current that aren't caused by other > parts of the system. If it isn't a very recent 15 or 14, then there > are known issues and you'll need to try those first. The problem manifested with a source upgrade

Re: nvme timeout issues with hardware and bhyve vm's

Hi, On Fri, 13 Oct 2023, at 03:40, Pete Wright wrote: > I had similar issues on my workstation as well. Scrubbing the NVMe > device on my real-hardware workstation hasn't turned up any issues, but > the system has locked up a handful of times. > > Just curious if others have seen the same, or i

Re: how to set vfs.zfs.arc.max in 15-current ?

On Fri, Oct 13, 2023 at 09:46:08AM +0300, Toomas Soome wrote: That is a bit odd, arc min used to be 64MB as lowest value - that is, it should never be 0. It was the default here (i.e. the value wasn't set in either loader.conf or sysctl.conf) world+kernel was built/installed today the 13th m

Re: how to set vfs.zfs.arc.max in 15-current ?

On Fri, Oct 13, 2023 at 08:12:47AM +0200, Juraj Lutter wrote: Set also vfs.zfs.arc.min to some value higher than zero. aha! that worked!!! :D root@beer:/root# sysctl vfs.zfs.arc.min=1073741824 vfs.zfs.arc.min: 0 -> 1073741824 root@beer:/root# sysctl vfs.zfs.arc.max=8589934592 vfs.zfs.arc.max:

Re: how to set vfs.zfs.arc.max in 15-current ?

On Thu, Oct 12, 2023 at 11:27:49AM -0700, Cy Schubert wrote: In message , void writes: Is there a new way to set arc.max in 15-current? It's no longer settable (except to "0") in main-n265801 (Oct 7th) while multiuser. # sysctl vfs.zfs.arc.max=8589934592 vfs.zfs.ar

how to set vfs.zfs.arc.max in 15-current ?

Is there a new way to set arc.max in 15-current? It's no longer settable (except to "0") in main-n265801 (Oct 7th) while multiuser. # sysctl vfs.zfs.arc.max=8589934592 vfs.zfs.arc.max: 0 sysctl: vfs.zfs.arc.max=8589934592: Invalid argument --

Re: CURRRENT snapshot won't boot due missing ZFS feature

On Sat, Sep 16, 2023 at 06:05:14PM +0100, void wrote: On Sat, Sep 16, 2023 at 05:22:20PM +0100, Warner Losh wrote: So, either you have to turn off those features (which I got no clue how to do in the normal installer), or you have to update userboot.so to the FreeBSD 14 version (which I think

Re: CURRRENT snapshot won't boot due missing ZFS feature

On Sat, Sep 16, 2023 at 06:35:01PM +0200, Michael Gmelin wrote: As this is the continuation of a thread I started in June, let me top post again the solution I used back then: Hi, I saw your fix but vm-bhyve is unavailable for me to use for a variety of reasons. --

Re: CURRRENT snapshot won't boot due missing ZFS feature

On Sat, Sep 16, 2023 at 05:22:20PM +0100, Warner Losh wrote: So, either you have to turn off those features (which I got no clue how to do in the normal installer), or you have to update userboot.so to the FreeBSD 14 version (which I think had a good chance of actually running on FreeBSD 13 sinc

Re: CURRRENT snapshot won't boot due missing ZFS feature

On Sat, Sep 16, 2023 at 08:43:49AM -0700, Mark Millard wrote: void wrote on Date: Sat, 16 Sep 2023 12:12:02 UTC : On Sat, Sep 16, 2023 at 12:55:19PM +0100, Warner Losh wrote: >Yes. The boot loader comes from the host. It must know how to read ZFS. It knows how to read zfs. I expect War

Re: CURRRENT snapshot won't boot due missing ZFS feature

On Sat, Sep 16, 2023 at 12:55:19PM +0100, Warner Losh wrote: Yes. The boot loader comes from the host. How does this work for non-zfs aware hosts? --

Re: CURRRENT snapshot won't boot due missing ZFS feature

On Sat, Sep 16, 2023 at 12:55:19PM +0100, Warner Losh wrote: Yes. The boot loader comes from the host. It must know how to read ZFS. It knows how to read zfs. On the host in question, there are many guests, some with zfs-boot, some not, just file-based. What the host is not, is zfs-on-root. I

Re: CURRRENT snapshot won't boot due missing ZFS feature

On Thu, Jun 08, 2023 at 06:11:15PM +0200, Michael Gmelin wrote: Hi, I didn't dig into this yet. After installing the current 14-snapshot (June 1st) in a bhyve-vm, I get this on boot: ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 (booting stops at this point) Seems like the boot lo

ifconfig: missing or corrupted regdomain database

Hello current@, I'm trying to set up atheros wireless on a desktop. The error in response to "ifconfig wlan0 up" is the expected info sans IP address with the added message of "ifconfig: missing or corrupted regdomain database" How can I fix this? System is amd64 built around 1020 UTC today 14.

Re: qt6 the default qt on -current?

On Wed, Aug 09, 2023 at 04:47:36PM +0200, Jan Beich wrote: Please, use ports@ list next time. Every supported FreeBSD version uses the same ports/ tree. Not supported FreeBSD versions require a time machine i.e., rolling back the ports/ tree to a date before EOL. OK. I didn't think the query be

qt6 the default qt on -current?

Hello list, How can I build making qt6 the default Qt? I'm using poudriere to build. I can see that for some ports there's a 'uses: qt6' that goes in the port. What I was looking for was a default string I can use with a poudriere make.conf like there is for python or perl. ty --

Re: poudriere && git

On Sun, Aug 06, 2023 at 04:11:00PM +0200, Matthias Apitz wrote: I'm now already running a new "make buildworld" again, which perhaps will but the actual tools into .../legacy/... and they will work because tools and shared libs fit together. I think there is something broken in buildworld with

Re: cc_vegas isn't built in recent current

On Wed, Jul 12, 2023 at 01:42:03PM +0100, void wrote: (cc_vegas) I notice that on -current the default is cc_cubic so will roll with that for now. Unless there's an algo that better suits FTTP which has spiky latency. --

  1   2   >