Re: NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

take" and in the >> vain of discussion >> it has been revealed that my nanoBSD specific "make.conf/src.conf" >> configurations were wrong. >> >> So, again: >> >> The builder host is a recent CURRENT (FreeBSD 14.0-CURRENT #2 >> main-n261876

Re: NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

;make.conf/src.conf" > configurations were wrong. > > So, again: > > The builder host is a recent CURRENT (FreeBSD 14.0-CURRENT #2 > main-n261876-f5a365e51fee: Thu > Mar 30 11:23:19 CEST 2023 amd64), the target is a most recent 13-STABLE (git > pull on a > daily/hourly/mo

NanoBSD: CURRENT unable to compile 13-STABLE : ld: error: args.o: Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 14.0.5')

,-Wdeprecated-non-prototype] [...] but being able compiling the kernel was "a lucky shot/mistake" and in the vain of discussion it has been revealed that my nanoBSD specific "make.conf/src.conf" configurations were wrong. So, again: The builder host is a recent CURRENT (Fre

Re: oudriere/CURRENT jail upgrade: install error: libc.so.7: Operation not permitted *** [_libinstall]

I don't know why this broke, but as a temp hack you can probably get away with just removing chflags, like so chflags -R noschg /path/to/the/jail On 3/15/23, FreeBSD User wrote: > Hello, > > running CURRENT on the host and a CURRENT jail on that specific host for > poudrier

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

FreeBSD User wrote on Date: Thu, 09 Mar 2023 08:42:44 UTC : > Having set > > WITHOUT_CROSS_COMPILER=YES > WITHOUT_SYSTEM_COMPILER=YES > WITHOUT_SYSTEM_LINKER=YES > This is contradictory: a mix of a setting that first tells it to not build some things and then some settings telling it to build

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

Am Wed, 8 Mar 2023 12:13:49 +0100 tue...@freebsd.org schrieb: > > On 8. Mar 2023, at 11:42, FreeBSD User wrote: > > > > Am Wed, 8 Mar 2023 11:28:11 +0100 > > Dimitry Andric schrieb: > > > >> On 8 Mar 2023, at 11:19, FreeBSD User wrote: > >> ... > >>> But I don't understand why the make en

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

> On Mar 8, 2023, at 10:26 PM, Ed Maste wrote: > > On Thu, 2 Mar 2023 at 05:14, Dimitry Andric wrote: >> >> WITHOUT_SYSTEM_COMPILER >> Do not opportunistically skip building a cross-compiler during >> the bootstrap phase of the build. Normally, if the currently >

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

On Thu, 2 Mar 2023 at 05:14, Dimitry Andric wrote: > > WITHOUT_SYSTEM_COMPILER > Do not opportunistically skip building a cross-compiler during > the bootstrap phase of the build. Normally, if the currently ... > I find the double negative phrasing "do not skip" alw

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

> On 8. Mar 2023, at 11:42, FreeBSD User wrote: > > Am Wed, 8 Mar 2023 11:28:11 +0100 > Dimitry Andric schrieb: > >> On 8 Mar 2023, at 11:19, FreeBSD User wrote: >> ... >>> But I don't understand why the make environment is trying to compile a >>> piece of code that >>> is disabled via "nodev

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

Am Wed, 8 Mar 2023 11:28:11 +0100 Dimitry Andric schrieb: > On 8 Mar 2023, at 11:19, FreeBSD User wrote: > ... > > But I don't understand why the make environment is trying to compile a > > piece of code that > > is disabled via "nodevice" as shown in my initial report herein: > > > > [...] >

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

On 8 Mar 2023, at 11:19, FreeBSD User wrote: ... > But I don't understand why the make environment is trying to compile a piece > of code that is > disabled via "nodevice" as shown in my initial report herein: > > [...] > src/sys/dev/an/if_an_pci.c:143:1: error: a function definition without a

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

Am Thu, 2 Mar 2023 11:13:51 +0100 Dimitry Andric schrieb: > On 2 Mar 2023, at 06:41, FreeBSD User wrote: > > > > Am Mon, 27 Feb 2023 23:46:21 +0100 > > Dimitry Andric schrieb: > ... > > > > I tried to find some documentation on my CURRENT host r

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

Dimitry Andric wrote on Date: Thu, 02 Mar 2023 10:13:51 UTC : > On 2 Mar 2023, at 06:41, FreeBSD User wrote: >> >> Am Mon, 27 Feb 2023 23:46:21 +0100 >> Dimitry Andric schrieb: > ... >> >> I tried to find some documentation on my CURRENT host regard

Re: Making -current machines accept mail from sendmail

On Sat, Mar 04, 2023 at 10:57:59AM -0800, David Wolfskill wrote: > > You might start with checking the output of "sockstat -l" on the machine > that is intended to receive the mail: SMTP is expected to be on 25/tcp. > > If the intended recipient machine does NOT show that 25/tcp is being > listen

Making -current machines accept mail from sendmail

Is there some special step to turn on dma so hosts can receive email from a sendmail-using host? I've got three hosts using 12/stable (hence sendmail) and a few more running -current (hence dma). The -stable hosts report "connection refused" when sending to -current, but -current

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

Am Thu, 2 Mar 2023 11:13:51 +0100 Dimitry Andric schrieb: > On 2 Mar 2023, at 06:41, FreeBSD User wrote: > > > > Am Mon, 27 Feb 2023 23:46:21 +0100 > > Dimitry Andric schrieb: > ... > > > > I tried to find some documentation on my CURRENT host r

Re: continuing 14-CURRENT buildworld error...

27;t inform > which process stopped it. > > ld.lld error: undefined symbol FreeBSD_nvlist_* [ many undefined symbols > each starting with that... > and referenced by > libpfctl_pie.a > libpfctl_pie.c > libpfctl_pie.pieo. > > . > the same source tree on a new

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

ied to find some documentation on my CURRENT host regarding >> "WITH_SYSTEM_COMPILER". None >> found via man src.conf, nor via make make.conf. Please delegate me to some >> place where I can >> find such infos. > > Ah I was confused, WITH_SYSTEM_COMPILE

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

On 2 Mar 2023, at 06:41, FreeBSD User wrote: > > Am Mon, 27 Feb 2023 23:46:21 +0100 > Dimitry Andric schrieb: ... > > I tried to find some documentation on my CURRENT host regarding > "WITH_SYSTEM_COMPILER". None > found via man src.conf, nor via make make.c

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

Am Mon, 27 Feb 2023 23:46:21 +0100 Dimitry Andric schrieb: > On 27 Feb 2023, at 22:23, Paul Mather wrote: > > > > On Feb 27, 2023, at 2:57 PM, Dimitry Andric wrote: > > > >> On 27 Feb 2023, at 19:19, FreeBSD User wrote: > >>> > >>>

continuing 14-CURRENT buildworld error...

with that... and referenced by libpfctl_pie.a libpfctl_pie.c libpfctl_pie.pieo. . the same source tree on a newly installed 14-CURRENT machine completes. Strangely, the build machine is mostly 13-STABLE except the kernel ??? which is best figured out by completing the 14-CURRENT build

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

On Mon, Feb 27, 2023 at 3:46 PM Dimitry Andric wrote: > On 27 Feb 2023, at 22:23, Paul Mather wrote: > > > > On Feb 27, 2023, at 2:57 PM, Dimitry Andric wrote: > > > >> On 27 Feb 2023, at 19:19, FreeBSD User wrote: > >>> > >>> Running r

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

On 27 Feb 2023, at 22:23, Paul Mather wrote: > > On Feb 27, 2023, at 2:57 PM, Dimitry Andric wrote: > >> On 27 Feb 2023, at 19:19, FreeBSD User wrote: >>> >>> Running recent CURRENT as host (FreeBSD 14.0-CURRENT #23 >>> main-n261147-b8bb73ab724b: Su

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

On Feb 27, 2023, at 2:57 PM, Dimitry Andric wrote: > On 27 Feb 2023, at 19:19, FreeBSD User wrote: >> >> Running recent CURRENT as host (FreeBSD 14.0-CURRENT #23 >> main-n261147-b8bb73ab724b: Sun Feb 26 >> 17:39:38 CET 2023 amd64), and nanoBSD (rece

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

On Mon, Feb 27, 2023 at 03:40:41PM -0500, Shawn Webb wrote: > On Mon, Feb 27, 2023 at 08:57:19PM +0100, Dimitry Andric wrote: > > On 27 Feb 2023, at 19:19, FreeBSD User wrote: > > > > > > Running recent CURRENT as host (FreeBSD 14.0-CURRENT #23 > > > m

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

Am Mon, 27 Feb 2023 20:57:19 +0100 Dimitry Andric schrieb: > On 27 Feb 2023, at 19:19, FreeBSD User wrote: > > > > Running recent CURRENT as host (FreeBSD 14.0-CURRENT #23 > > main-n261147-b8bb73ab724b: Sun > > Feb 26 17:39:38 CET 2023 amd64), and nanoBSD (recent 13

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

On Mon, Feb 27, 2023 at 08:57:19PM +0100, Dimitry Andric wrote: > On 27 Feb 2023, at 19:19, FreeBSD User wrote: > > > > Running recent CURRENT as host (FreeBSD 14.0-CURRENT #23 > > main-n261147-b8bb73ab724b: Sun Feb 26 > > 17:39:38 CET 2023 amd64), and nanoBSD (rece

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

On 27-02-23 19:19, FreeBSD User wrote: Running recent CURRENT as host (FreeBSD 14.0-CURRENT #23 main-n261147-b8bb73ab724b: Sun Feb 26 17:39:38 CET 2023 amd64), and nanoBSD (recent 13-STABLE, git stable/13). Building an appliance based on 13-STABLE sources, a customized kernel via nanoBSD

Re: NanoBSD: CURRENT unable to compile 13-STABLE : error: a function definition without a prototype is deprecated ... in C

On 27 Feb 2023, at 19:19, FreeBSD User wrote: > > Running recent CURRENT as host (FreeBSD 14.0-CURRENT #23 > main-n261147-b8bb73ab724b: Sun Feb 26 > 17:39:38 CET 2023 amd64), and nanoBSD (recent 13-STABLE, git stable/13). > > Building an appliance based on 13-STABLE sou

Re: CURRENT: Crash in multiuser mode while shutdown

g as I finish my work. The I hope I can provide you with a backtrace. cpu-data has been updated recently, I use this on these two IvyBridge methusalem riggs, I may disable this first and see what happens ... Regards oh > > rick > > On Sun, Feb 19, 2023 at 1:38 AM FreeBSD User wrote

CURRENT: Crash in multiuser mode while shutdown

Hello, most recent CURRENT crashes on shutdown from multiuser mode (singleuser mode, used after repairing failed FFS filesystems, is all right). The crashes go on since roughly a 1/2 week from now. The boxes involved are all cumtomized kernels (in most cases hard linked modules into kernel

Re: py-libzfs build failure on current, zpool_search_import() missing

Quoting Ryan Moeller (from Fri, 3 Feb 2023 10:48:35 -0500): The build still fails on -current as of end of Jan with "too few argument to function call, expected 4, have 3" for zfs_iter_filesystems. Is a patch for openzfs in -current missing? I haven't seen a commit to -curren

Re: py-libzfs build failure on current, zpool_search_import() missing

Quoting Ryan Moeller (from Thu, 2 Feb 2023 10:43:53 -0500): I've updated the py-libzfs port to fix the build. The build still fails on -current as of end of Jan with "too few argument to function call, expected 4, have 3" for zfs_iter_filesystems. Is a patch for open

Re: py-libzfs build failure on current, zpool_search_import() missing

Thanks! But for the record, what was the actual required change? Could you like to the PR? On Thu, Feb 2, 2023 at 8:44 AM Ryan Moeller wrote: > > I've updated the py-libzfs port to fix the build. > > -- > Ryan Moeller > iXsystems, Inc. > OS Developer > Email: r...@ixsystems.com

Re: py-libzfs build failure on current, zpool_search_import() missing

Quoting Alan Somers (from Thu, 2 Feb 2023 06:58:35 -0700): Unfortunately libzfs doesn't have a stable API, so this kind of breakage is to be expected. libzfs_core does, but libzfs_core is incomplete. You should report this problem upstream at https://github.com/truenas/py-libzfs . I did a

Re: py-libzfs build failure on current, zpool_search_import() missing

gt; > Hi, > > the build of py-libzfs fails on -current due to a missing > zpool_search_import(), and as such iocage can not be build (and the > old iocage segfaults, so the ABI seems to have changed too). The > symbol is available in libzutil, but I can not find > zpool_search_import(

py-libzfs build failure on current, zpool_search_import() missing

Hi, the build of py-libzfs fails on -current due to a missing zpool_search_import(), and as such iocage can not be build (and the old iocage segfaults, so the ABI seems to have changed too). The symbol is available in libzutil, but I can not find zpool_search_import() in /usr/include

Re: 14.0-CURRENT fails Norelsys NS1081

-STABLE? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263868 Thanks Max > On Jan 27, 2023, at 23:27, Innocenti Maresin > wrote: > > By the way, the same error happened to > FreeBSD-13.1-STABLE-amd64-20230120-4a8af507ebe5-253535, > hence it does not seem to be specifical

Re: 14.0-CURRENT fails Norelsys NS1081

By the way, the same error happened to FreeBSD-13.1-STABLE-amd64-20230120-4a8af507ebe5-253535, hence it does not seem to be specifically a CURRENT issue. --Incnis Mrsi

14.0-CURRENT fails Norelsys NS1081

Hello. FreeBSD-14.0-CURRENT-amd64-20230120-43703bc489ec-260163 failed to attach to Norelsys NS1081 card-reader controller. In short: umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x8100 (probe0:umass-sim0:0:0:0): CAM status: Auto-Sense Retrieval Failed In more details: https

Trying to switch to 14-CURRENT for linuxulator netlink, now sudo hanging in sbwait in linux jail

Hi all, I was not sure if I should go with this to -current or -emulation, I threw a coin and landed here :) Tell me if I need to take this to -emulation. I’m testing a few linux triplestore in a linux jail, and used 13.1 which worked fine most of the time. Now one of the stores shows

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

On 04-01-23 11:24, Konstantin Belousov wrote: On Tue, Jan 03, 2023 at 11:38:55AM +0100, Floyd, Paul wrote: On 30/12/2022 01:54, Konstantin Belousov wrote: The backtrace is needed to make a further analysis. Any suggestions for getting a backtrace? I get the panic booting either the inst

VirtualBox: screenshots (was: 14.0-CURRENT panic on boot, i386 VirtualBox client)

On 04/01/2023 10:24, Konstantin Belousov wrote: … No idea how to take the virtual screen snapshot under VB. … For me, it's the Control key to the right + E OpenPGP_signature Description: OpenPGP digital signature

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

On Tue, Jan 03, 2023 at 11:38:55AM +0100, Floyd, Paul wrote: > > On 30/12/2022 01:54, Konstantin Belousov wrote: > > > > The backtrace is needed to make a further analysis. > > > Any suggestions for getting a backtrace? I get the panic booting either the > installer ISO or the VM image, both in

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

On 30/12/2022 01:54, Konstantin Belousov wrote: The backtrace is needed to make a further analysis. Any suggestions for getting a backtrace? I get the panic booting either the installer ISO or the VM image, both in VirtualBox. A+ Paul

AMD Ryzen 5 5600G graphics acceleration fails now on -current

Greetings, I have been happily using an AMD 5600G box for about 9 months on -current with zero hiccups. After performing my quarterly git pull + buildworld + installworld + pkg update + pkg upgrade, no packages that require graphics work. This is broad based, from kitty to mpv, thunderbird

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

On Thu, Dec 29, 2022 at 09:39:44AM +0100, Paul Floyd wrote: > > > On 28-12-22 18:12, Ronald Klop wrote: > > > > > I've had success to capture errors by recording the screen with my phone > > and playing back on slow speed. > > Another option might be to enable serial port for the console of the

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

On 28-12-22 18:12, Ronald Klop wrote: I've had success to capture errors by recording the screen with my phone and playing back on slow speed. Another option might be to enable serial port for the console of the guest and capture the output. But I don't know if the default ISO uses that a

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

On 12/28/22 17:45, Paul Floyd wrote: Hi For quite a few weeks I've been unable to boot 14.0-CURRENT i386 in a VirtualBox VM. I've tried both booting from iso image and the vmdk image. I get a kernel panic The host is running 13.1-RELEASE-p3 amd64 No problems with 14.0-CURRENT am

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

On 28-12-22 18:05, Graham Perrin wrote: If the guest has more than CPU, try reducing to one. A step further: try booting the guest in safe mode. Neither of those changed anything (I was using 2 CPUs) A+ Paul

Re: 14.0-CURRENT panic on boot, i386 VirtualBox client

On 28/12/2022 16:45, Paul Floyd wrote: … I haven't been able to see the last message before the panic as it scrolls past too quickly. Any suggestions for a working either how to get more info or what vbox settings to use? If the guest has more than CPU, try reducing to one. A step further

14.0-CURRENT panic on boot, i386 VirtualBox client

Hi For quite a few weeks I've been unable to boot 14.0-CURRENT i386 in a VirtualBox VM. I've tried both booting from iso image and the vmdk image. I get a kernel panic The host is running 13.1-RELEASE-p3 amd64 No problems with 14.0-CURRENT amd64 guests. I haven't been able

Re: Problem compiling CURRENT

I deleted /usr/obj and restarted world I will see tomorrow the outcome.Filippo On Wednesday, December 14, 2022 at 02:22:57 PM GMT+1, Filippo Moretti wrote: I downloaded src for current on 13/12 11.20 CEST.I did have the same issues for about 5 days I made a few attempts all whit

Re: Problem compiling CURRENT

I downloaded src for current on 13/12 11.20 CEST.I did have the same issues for about 5 days I made a few attempts all whit same error.Filippo On Wednesday, December 14, 2022 at 02:18:20 PM GMT+1, Herbert J. Skuhra wrote: On Wed, 14 Dec 2022 14:08:01 +0100, Filippo Moretti wrote

Re: Problem compiling CURRENT

On Wed, 14 Dec 2022 14:08:01 +0100, Filippo Moretti wrote: > > FreeBSD ROXY 14.0-CURRENT FreeBSD 14.0-CURRENT #4 > main-n258255-de56ac88099: Wed Sep 28 19:35:24 CEST 2022 > root@ROXY:/usr/obj/usr/src/amd64.amd64/sys/ROXY amd64 > > > > > > > > Dear

Problem compiling CURRENT

FreeBSD ROXY 14.0-CURRENT FreeBSD 14.0-CURRENT #4 main-n258255-de56ac88099: Wed Sep 28 19:35:24 CEST 2022 root@ROXY:/usr/obj/usr/src/amd64.amd64/sys/ROXY amd64 Dear Sir I had the following error while trying to compile CURRENT===> usr.bin/rs (all) make[4]: /usr/obj/usr/src/am

Re: Buildword Error on a recent -CURRENT

Hi Michael, On Fri, Dec 02, 2022 at 12:02:15PM +0100, Michael Tuexen wrote: > > On 2. Dec 2022, at 00:30, Gordon Bergling wrote: > > > > Hello, > > > > I am currently having the following build work error on a recent > > -CURRENT. > > > > = ===

Buildword Error on a recent -CURRENT

Hello, I am currently having the following build work error on a recent -CURRENT. = ===> usr.bin/less (all) -16372 bytes available --- loader_lua.bin --- *** [loader_lua.bin] Error code 1 make[5]: stopped in /boiler/nfs/src/stand/i386/loader_lua --- all_subdir_stand --- mak

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Mon, Nov 21, 2022 at 12:24 PM Mark Millard wrote: > On Nov 20, 2022, at 19:48, Archimedes Gaviola < > archimedes.gavi...@gmail.com> wrote: > > > On Wed, Nov 9, 2022 at 10:15 AM Archimedes Gaviola < > archimedes.gavi...@gmail.com> wrote: > > On Wed, Nov 9, 2022 at 1:37 AM Mark Millard wrote: >

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Nov 20, 2022, at 19:48, Archimedes Gaviola wrote: > On Wed, Nov 9, 2022 at 10:15 AM Archimedes Gaviola > wrote: > On Wed, Nov 9, 2022 at 1:37 AM Mark Millard wrote: > On Nov 8, 2022, at 04:15, Ronald Klop wrote: > > > Van: Warner Losh > > Datum: dinsdag, 8 november 2022 04:28 > > Aan: A

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Wed, Nov 9, 2022 at 10:15 AM Archimedes Gaviola < archimedes.gavi...@gmail.com> wrote: > > > On Wed, Nov 9, 2022 at 1:37 AM Mark Millard wrote: > >> On Nov 8, 2022, at 04:15, Ronald Klop wrote: >> >> > Van: Warner Losh >> > Datum: dinsdag, 8 november 2022 04:28 >> > Aan: Archimedes Gaviola >

Re: DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? (on FreeBSD14 CURRENT)

ps://askubuntu.com/questions/1038184/how-to-lockdown-system-wide-settings-with-dconf > > /etc/ in those should be read /usr/local/etc/ on FreeBSD. > And possibly defaults of each application are stored > under /usr/local/share/ or under /usr/local/lib/. > > BTW, I'm basicall

Re: DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? (on FreeBSD14 CURRENT)

tting-starting-from-just-created-ad https://askubuntu.com/questions/1038184/how-to-lockdown-system-wide-settings-with-dconf /etc/ in those should be read /usr/local/etc/ on FreeBSD. And possibly defaults of each application are stored under /usr/local/share/ or under /usr/local/lib/. BTW,

Re: DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? (on FreeBSD14 CURRENT)

disable ACPI in FreeBSD so that even gdm can not > "kill" the machine !! > I say ^kill^ because there is also another bug, the machine is not properly > restarting form hibernation, > Even not from S1. > > Louis > > -Original Message- > Fr

RE: DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? (on FreeBSD14 CURRENT)

riginal Message- From: Kirk McKusick Sent: Sunday, November 13, 2022 1:23 AM To: louis.free...@xs4all.nl Cc: freebsd-current@FreeBSD.org Subject: Re: DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? (on FreeBSD14 CURRENT) > From: > To: > Subject: DESPARATE: How to stop Fr

Re: DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? (on FreeBSD14 CURRENT)

On Thu, Nov 10, 2022 at 10:21:24PM -0500, Alexander Motin wrote: > On 10.11.2022 15:29, louis.free...@xs4all.nl wrote: > > I am still desperately trying to stop FreeBSD from sleeping, but I > > simply do not manage. > > > > It is really very annoying that I have to restart the machine every 10 > >

Re: DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? (on FreeBSD14 CURRENT)

On 10.11.2022 15:29, louis.free...@xs4all.nl wrote: I am still desperately trying to stop FreeBSD from sleeping, but I simply do not manage. It is really very annoying that I have to restart the machine every 10 minutes, when I am working via SSH. So if any one has a solution, it would be ve

Re: DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? (on FreeBSD14 CURRENT)

> On Nov 11, 2022, at 4:29 AM, > wrote: > > I am still desperately trying to stop FreeBSD from sleeping, but I simply do > not manage. > > It is really very annoying that I have to restart the machine every 10 > minutes, when I am working via SSH. I think you will need to find the event

Re: DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? (on FreeBSD14 CURRENT)

Hi, I don't know what you mean by "sleep", but some CPUs have bug and setting: sysctl machdep.idle=spin Helps! --HPS

DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? (on FreeBSD14 CURRENT)

I am still desperately trying to stop FreeBSD from sleeping, but I simply do not manage. � It is really very annoying that I have to restart the machine every 10 minutes, when I am working via SSH. So if any one has a solution, it would be very much appreciated! � It should ….. be possibl

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Wed, Nov 9, 2022 at 1:37 AM Mark Millard wrote: > On Nov 8, 2022, at 04:15, Ronald Klop wrote: > > > Van: Warner Losh > > Datum: dinsdag, 8 november 2022 04:28 > > Aan: Archimedes Gaviola > . . . > > ... > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 256929, size: 4096 > > swap_p

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Tue, Nov 8, 2022 at 8:15 PM Ronald Klop wrote: > > > *Van:* Warner Losh > *Datum:* dinsdag, 8 november 2022 04:28 > *Aan:* Archimedes Gaviola > *CC:* Mark Millard , freebsd-current < > freebsd-current@freebsd.org> > *Onderwerp:* Re: 14.0-CURRENT failed to

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Nov 8, 2022, at 04:15, Ronald Klop wrote: > Van: Warner Losh > Datum: dinsdag, 8 november 2022 04:28 > Aan: Archimedes Gaviola . . . > ... > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 256929, size: 4096 > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 3628, size: 4096 > swa

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

Van: Warner Losh Datum: dinsdag, 8 november 2022 04:28 Aan: Archimedes Gaviola CC: Mark Millard , freebsd-current Onderwerp: Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build On Mon, Nov 7, 2022 at 7:40 PM Archimedes Gaviola wrote: On Sat, Nov 5, 2022 at 5:28 PM

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Tue, Nov 8, 2022 at 3:16 PM Mark Millard wrote: > On Nov 7, 2022, at 22:50, Archimedes Gaviola > wrote: > > > . . . > > > > > >> # sysctl -W vm.pfault_oom_attempts > >> vm.pfault_oom_attempts: -1 > >> > >> # sysctl -W vm.pfault_oom_wait > >> vm.pfault_oom_wait: 10 > > FYI: the -W just limits

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Nov 7, 2022, at 22:50, Archimedes Gaviola wrote: > . . . > > >> # sysctl -W vm.pfault_oom_attempts >> vm.pfault_oom_attempts: -1 >> >> # sysctl -W vm.pfault_oom_wait >> vm.pfault_oom_wait: 10 FYI: the -W just limits the command to writable cases. If the text is not a writable, it will no

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Tue, Nov 8, 2022 at 11:53 AM Mark Millard wrote: > On Nov 7, 2022, at 19:28, Warner Losh wrote: > > > > . . . > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 256929, size: 4096 > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 3628, size: 4096 > > swap_pager: indefinite wait

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

the new way. >>> >>> >>>> Basically, the memory subsystem can be saturated without all >>>> the cores being in use. The extra interference made things >>>> take longer.) >>>> >>> >>> Oh I see so it's the reason.

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Tue, Nov 8, 2022 at 11:25 AM Mark Millard wrote: > On Nov 7, 2022, at 18:40, Archimedes Gaviola > wrote: > > > . . . > > > > Hi Mark, > > > > With this set of build commands now, > > > > # cd /usr/src; make -j3 KERNCONF=ARM TARGET_ARCH=aarch64 buildworld > kernel-toolchain buildkernel install

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Nov 7, 2022, at 19:28, Warner Losh wrote: > > . . . > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 256929, size: 4096 > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 3628, size: 4096 > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 255839, size: 40960 > pid 46153 (c++),

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

were using the likes of: >>> >>> # cd /usr/src ; make KERNCONF=ARM TARGET_ARCH=aarch64 \ >>> buildkernel buildworld installkernel installworld distribution \ >>> DESTDIR=/home/freebsd/rpi3b >>> >>> I'll note that the standard order of the f

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Nov 7, 2022, at 18:40, Archimedes Gaviola wrote: > . . . > > Hi Mark, > > With this set of build commands now, > > # cd /usr/src; make -j3 KERNCONF=ARM TARGET_ARCH=aarch64 buildworld > kernel-toolchain buildkernel installworld installkernel distribution > DESTDIR=/home/freebsd/rpi3b > >

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

itself but does use. >> > > Okay this is noted, thanks for clarifying and correcting me, I really > appreciate it. I'll reflect on the proper build sequence for much > efficiency. > > >> There is a kernel-toolchain target for avoiding the >> need to do

Re: How to disable ACPI? (on FreeBSD14 CURRENT)

On 6 Nov 2022, at 16:47, Alexander Motin wrote: > Hi Louis, > > You should not try to disable ACPI these days. It was a recommendation in > some cases probably ~15 years ago, but for many years now modern systems > depend on ACPI for proper operation. I have no idea what causes crash in > you

Re: How to disable ACPI? (on FreeBSD14 CURRENT)

Hi Louis, You should not try to disable ACPI these days. It was a recommendation in some cases probably ~15 years ago, but for many years now modern systems depend on ACPI for proper operation. I have no idea what causes crash in your case, but I would not expect it to end up good any way.

How to disable ACPI? (on FreeBSD14 CURRENT)

I need to disable acpi and the indicated method for that is to add ^hint.acpi.0.disabled="1"^ in /boot/loader.conf . However that crashes my system !! Not only that, to make it work again I have to edit loader.conf on a system which does ^not start^. � After a lot of searching Interne

Options for production testing under current(samba slow)

cd /usr/src/sys/amd64/conf cp GENERIC-NODEBUG MYKERNEL; (add: options BHYVE_SNAPSHOT) cd /usr/src make -j12 buildworld -DWITH_BHYVE_SNAPSHOT -DWITH_MALLOC_PRODUCTION make -j12 buildkernel KERNCONF=MYKERNEL make installkernel KERNCONF=MYKERNEL etc Been playing with current lately

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

o. > I do not know how long a from-scratch buildworld > buildkernel without a -jN takes on a RPi3B these > days. If I remember right, for -jN with 1 saw claims about such they were somewhere in the > range 36hr..48hr. There's an ongoing build at the moment, it's already taki

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On 2022-Nov-2, at 14:09, Archimedes Gaviola wrote: > On Mon, Oct 31, 2022 at 1:47 PM Archimedes Gaviola > wrote: > > . . . > > . . . > > > Hi Mark, > > Just an update, as kernel and world compilation is ongoing with my RPi3B > system (with swap partition) is doing so far, so good. It alr

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

Sorry, wrong post! Nuno Teixeira escreveu no dia quarta, 2/11/2022 à(s) 21:44: > Hello, > > From > https://lists.freebsd.org/archives/freebsd-ports/2022-August/002476.html > > --- > With both FLANG and MLIR: > (...) > [13:49:55] [01] [13:49:17] Finished devel/llvm13 | llvm13-13.0.1_3: Success >

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

Hello, From https://lists.freebsd.org/archives/freebsd-ports/2022-August/002476.html --- With both FLANG and MLIR: (...) [13:49:55] [01] [13:49:17] Finished devel/llvm13 | llvm13-13.0.1_3: Success load averages: . . . MaxObs: 6.43, 5.91, 5.77 (Note: spanned overnight so the nightly cron

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Mon, Oct 31, 2022 at 1:47 PM Archimedes Gaviola < archimedes.gavi...@gmail.com> wrote: > > > Okay noted on GPT not MBR method with gpart. > > >> I did not happen to have a MBR example around. So I could >> only show GPT. The note was more to avoid confusion than >> anything, since the two are n

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

> Okay noted on GPT not MBR method with gpart. > I did not happen to have a MBR example around. So I could > only show GPT. The note was more to avoid confusion than > anything, since the two are not equivalent for how they > work. > Okay, this is noted. > > > By the way, what's the proper all

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On 2022-Oct-30, at 21:00, Mark Millard wrote: > On 2022-Oct-30, at 19:47, Archimedes Gaviola > wrote: > >> On Mon, Oct 31, 2022 at 1:29 AM Mark Millard wrote: >> Archimedes Gaviola wrote on >> Date: Sun, 30 Oct 2022 13:41:52 UTC : >> >>> I am b

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On 2022-Oct-30, at 19:47, Archimedes Gaviola wrote: > On Mon, Oct 31, 2022 at 1:29 AM Mark Millard wrote: > Archimedes Gaviola wrote on > Date: Sun, 30 Oct 2022 13:41:52 UTC : > > > I am building a kernel and world in 14.0-CURRENT > > https://download.freebsd.org/ftp

Re: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

On Mon, Oct 31, 2022 at 1:29 AM Mark Millard wrote: > Archimedes Gaviola wrote on > Date: Sun, 30 Oct 2022 13:41:52 UTC : > > > I am building a kernel and world in 14.0-CURRENT > > > https://download.freebsd.org/ftp/snapshots/arm64/aarch64/ISO-IMAGES/14.0/FreeBSD-14.0-C

RE: 14.0-CURRENT failed to reclaim memory error in RPi 3B build

Archimedes Gaviola wrote on Date: Sun, 30 Oct 2022 13:41:52 UTC : > I am building a kernel and world in 14.0-CURRENT > https://download.freebsd.org/ftp/snapshots/arm64/aarch64/ISO-IMAGES/14.0/FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20221027-769b884e2e2-258837.img.xz > with Raspberry Pi

14.0-CURRENT failed to reclaim memory error in RPi 3B build

Hi, I am building a kernel and world in 14.0-CURRENT https://download.freebsd.org/ftp/snapshots/arm64/aarch64/ISO-IMAGES/14.0/FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20221027-769b884e2e2-258837.img.xz with Raspberry Pi 3B (ARM kernel config file and in default system configurations) and

Re: pkg won't bootstrap on -current

On 17/10/2022 15:08, void wrote: … arm64.aarch64 … version is main-n258626-865f46b25559 built today 17th Oct 22. In context: around twenty hours ago. … Child process pid=10086 terminated abnormally: Segmentation fault … A lazy gues

RE: pkg won't bootstrap on -current

void wrote on Date: Mon, 17 Oct 2022 14:08:11 UTC : > It seems pkg won't bootstrap on -current, at least not for me on arm64.aarch64 > I've not tried yet with just a snapshot. > > version is main-n258626-865f46b25559 built today 17th Oct 22. > > The error is >

<    1   2   3   4   5   6   7   8   9   10   >