Re: buildworld FAILURE:googletest

On 30/10/2024 20:42, Simon J. Gerraty wrote: Would need more context to comment. Do you have filemon(4) loaded? yes. meta mode makes very little difference for a clean tree build, it is only update builds where the .meta files become super useful. this was a build updating an existing ob

Re: buildworld FAILURE:googletest

On 29/10/2024 06:01, Larry Rosenman wrote: on a clean /usr/obj it works.  The below was metamode. i also just ran into this with meta mode + make buildworld-jobs, src ~22429a464a5f4f6bb5a056aae1353985db83b721. ld: error: undefined symbol: testing::internal::MakeAndRegisterTestInfo(char cons

ZFS panic on shutdown

hello, i thought i should mentioned that after upgrading to FreeBSD 15.0-CURRENT #3 lf/main-n269068-2cff93ced1d: Wed Oct 23 02:48:20 BST 2024 srcma...@hemlock.eden.le-fay.org:/data/build/obj/freebsd/data/build/src/freebsd/lf/main/amd64.amd64/sys/GENERIC which is based on commit 53314e34d5e8

Re: 15.0 on RPi4, USB broken: uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT

Mark Millard: > On Mar 30, 2024, at 12:44, Lexi Winter wrote: > > when the problem happens, with USB_DEBUG enabled, the kernel logs: > > > > uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT > > uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disab

15.0 on RPi4, USB broken: uhub_reattach_port: port 2 reset failed, error=USB_ERR_TIMEOUT

hello, i'm using 15.0 (f66a994d59) on an 4GB RPi4 with a USB<>SATA adapter for the root disk: usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set for USB mass storage device ASM1153USB3.0TOSATA ASM1153USB3.0TOSATA (0x174c:0x55aa) ugen0.3: at usbus0 umass0 on uhub1 umass0: on usbus0 umass0: SCSI over

Re: after trivial update, 15.0 ARM64 system no longer boots

Lexi Winter: > i am not really an expert on either ARM64 in general or on the RPi > hardware in particular. could anyone suggest how i could debug this > problem, e.g. to get more information about why the system won't finish > booting? i dug into this a bit more, and to answe

after trivial update, 15.0 ARM64 system no longer boots

hi lists, i have a FreeBSD 15.0/arm64 system, an RPi4, which was previously running 15.0 with pkgbase. i rebuilt main on my pkg server and updated the RPi with 'pkg update', which only included ~2 commits neither of which seemed like they had anything to do with booting, but after the update, the

Re: 42fdcd9fd917 broke my snd_uaudio(4)

hi Florian, Florian Walpen: > I have a Scarlett 18i20 myself, but maybe a different generation - it has 18 > recording channels as its name suggests. Is 20 recording channels correct for > your device? this is a 3rd generation 18i20; as well the usual physical inputs it has a stereo loopback c

42fdcd9fd917 broke my snd_uaudio(4)

hello, since the commit: 42fdcd9fd917 snd_uaudio(4): Fix config detection with defaults set. my snd_uaudio(4) no longer works. the symptom is that applications attempting to play audio hang forever, and no audio is produced. reverting this commit fixed the problem. the issue only occurs if i h

Re: meta mode

void: > But, from time to time, one might be required to make > cleanworld && make cleandir (to be sure) && make clean (to be *really* sure) > What circumstances & notices in /usr/src/UPDATING would require it? one case this is required in non-meta mode is if you use pkg(8) (e.g., with poudriere

Re: poudriere: swap_pager: out of swap space

Mark Millard: > You seem to be under the impression that "Inact" means "page is not > dirty" and so can be freed without being written out to the swap > space. indeed, i was, because this is how sysutils/htop displays memory usage: top(1) Mem: 8502M Active, 15G Inact, 1568M Laundry, 5518M Wired,

Re: poudriere: swap_pager: out of swap space

Ronald Klop: > On 1/11/24 03:21, Lexi Winter wrote: > > 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) and with the > > ZFS ARC limited to 8GB. > My first guess would be

poudriere: swap_pager: out of swap space

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) and with the ZFS ARC limited to 8GB. running poudriere produces

Re: bridge(4) and IPv6 broken?

Patrick M. Hausen: > > Am 02.01.2024 um 13:56 schrieb Jan Bramkamp : > > IPv6 enabled interfaces need a link-local address for normal > > operation. Please set the auto-linklocal flag on the bridge and try > > again. > > And remove the link-local address from alc0. A bridge member must not have >

bridge(4) and IPv6 broken?

hello, i'm having an issue with bridge(4) and IPv6, with a configuration which is essentially identical to a working system running releng/14.0. ifconfig: lo0: flags=1008049 metric 0 mtu 16384 options=680003 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128