Re: ZFS deadlock in 14

2023-08-10 Thread Graham Perrin
On 11/08/2023 04:32, Kevin Bowling wrote: Spoke too soon still seeing zfs lockups Kevin, do you have a log device? (ZIL) under heavy poudriere workload … Can you tell what was building when the problem occurred? For example, qutebrowser

Re: ps(1) bugs and problems

2023-08-10 Thread Piotr P. Stefaniak
I thought about this more and the change I proposed in https://reviews.freebsd.org/D41231 seems unnecessarily complicated, regardless of which characters will be chosen to denote going up and down the process tree. ps -D'^$' suggests there are possibly more characters to use and maybe even some

Re: ZFS deadlock in 14

2023-08-10 Thread Kevin Bowling
Spoke too soon still seeing zfs lockups under heavy poudriere workload after the MFVs. Regression time matches what has been reported here. On Thu, Aug 10, 2023 at 4:33 PM Cy Schubert wrote: > I haven't experienced any problems (yet) either. > > > -- > Cheers, > Cy Schubert > FreeBSD UNIX:

Re: ZFS deadlock in 14

2023-08-10 Thread Cy Schubert
I haven't experienced any problems (yet) either. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org e^(i*pi)+1=0 In message , Kevin Bowling writes: > The two MFVs on head have improved/fixed stability with

Re: ZFS deadlock in 14

2023-08-10 Thread Kevin Bowling
The two MFVs on head have improved/fixed stability with poudriere for me 48 core bare metal. On Thu, Aug 10, 2023 at 6:37 AM Cy Schubert wrote: > > In message om> > , Kevin Bowling writes: > > Possibly https://github.com/openzfs/zfs/commit/2cb992a99ccadb78d97049b40bd4= > > 42eb4fdc549d > > > >

Re: port lang/python27 does not build in 14.0-CURRENT w/ poudriere

2023-08-10 Thread Tomoaki AOKI
On Thu, 10 Aug 2023 18:09:54 -0400 Charlie Li wrote: > Enji Cooper wrote: > > Hmm… All lang/python27 requiring ports should be marked BROKEN and > > removed — upstream stopped supporting 2.7 3.5 years ago (04/01/2020) :/. > We can't entirely do that yet. Unfortunately, moinmoin, original

Re: Has the update procedure changed?

2023-08-10 Thread Tomoaki AOKI
On Thu, 10 Aug 2023 16:08:26 +0200 Dag-Erling Smørgrav wrote: > Tomoaki AOKI writes: > > Yes. But if bsdinstall and freebsd-update automatically bootstrap > > etcupdate if not yet done, newbies and casual users wouldn't be bitten. > >

Re: Has the update procedure changed?

2023-08-10 Thread Tomoaki AOKI
On Thu, 10 Aug 2023 03:15:43 -0700 (PDT) "Jeffrey Bouquet" wrote: > On Thu, 10 Aug 2023 06:32:14 +0900, Tomoaki AOKI > wrote: > > > On Wed, 9 Aug 2023 05:50:05 -0700 > > David Wolfskill wrote: > > > > > On Wed, Aug 09, 2023 at 09:38:22PM +0900, Tomoaki AOKI wrote: > > > > ... > > > > > > >

Re: port lang/python27 does not build in 14.0-CURRENT w/ poudriere

2023-08-10 Thread Charlie Li
Enji Cooper wrote: Hmm… All lang/python27 requiring ports should be marked BROKEN and removed — upstream stopped supporting 2.7 3.5 years ago (04/01/2020) :/. We can't entirely do that yet. Unfortunately, moinmoin, original mailman and the CSM for UEFI-EDK2 (used in bhyve) still staunchly

Re: port lang/python27 does not build in 14.0-CURRENT w/ poudriere

2023-08-10 Thread Enji Cooper
> On Aug 10, 2023, at 2:56 PM, Matthias Apitz wrote: … > Don't know if I can answer your questions. I'm building ports with > poudriere and lang/python27 is pulled in from some other ports. The port > lang/python27 itself is not on my list for poudriere: > > # grep python

Re: port lang/python27 does not build in 14.0-CURRENT w/ poudriere

2023-08-10 Thread Matthias Apitz
El día jueves, agosto 10, 2023 a las 01:46:56p. m. -0700, Enji Cooper escribió: > > > On Aug 10, 2023, at 2:38 AM, Matthias Apitz wrote: > > > > El día Wednesday, August 09, 2023 a las 06:04:16PM +0200, Moin Rahman > > escribió: > > > >> This perfectly builds on the latest HEAD without any

Re: port lang/python27 does not build in 14.0-CURRENT w/ poudriere

2023-08-10 Thread Enji Cooper
> On Aug 10, 2023, at 2:38 AM, Matthias Apitz wrote: > > El día Wednesday, August 09, 2023 a las 06:04:16PM +0200, Moin Rahman > escribió: > >> This perfectly builds on the latest HEAD without any problem as shared in my >> build log. I am not sure what is wrong at your end. Neither can I

Re: Has the update procedure changed?

2023-08-10 Thread Dag-Erling Smørgrav
Tomoaki AOKI writes: > Yes. But if bsdinstall and freebsd-update automatically bootstrap > etcupdate if not yet done, newbies and casual users wouldn't be bitten. https://cgit.freebsd.org/src/commit/?id=e9120a256075543376496fbd75949eed1f13a887 DES -- Dag-Erling Smørgrav - d...@freebsd.org

Re: ZFS deadlock in 14

2023-08-10 Thread Cy Schubert
In message , Kevin Bowling writes: > Possibly https://github.com/openzfs/zfs/commit/2cb992a99ccadb78d97049b40bd4= > 42eb4fdc549d > > On Tue, Aug 8, 2023 at 10:08=E2=80=AFAM Dag-Erling Sm=C3=B8rgrav sd.org> wrote: > > > > At some point between 42d088299c (4 May) and f0c9703301 (26 June), a > >

Re: The future for support of BeagleBone Black and its variants

2023-08-10 Thread George Abdelmalik
Hi David, The problems are kernel related. If I understand correctly it's in the area of clock definitions I think but I've not properly studied the patches. DTC is good. Regards, George. On 10/8/23 14:52, David Chisnall wrote: Hi, What are the changes to the DTS files? If there are

Re: The future for support of BeagleBone Black and its variants

2023-08-10 Thread David Chisnall
Hi, What are the changes to the DTS files? If there are problems with DTC handling the new files, please can you raise issues here: https://github.com/davidchisnall/dtc/issues If there are problems with the kernel’s handling of the dtb, please ignore me. David > On 10 Aug 2023, at 13:24,

The future for support of BeagleBone Black and its variants

2023-08-10 Thread George Abdelmalik
Hi all, For a long while now CURRENT has not been working on the BBB due to incompatible upstream changes in vendor DTS files. I know there are some patches available which at least get FreeBSD running but those have yet to be incorporated into the project's repository. This leaves me with

Re: ZFS deadlock in 14

2023-08-10 Thread Kurt Jaeger
Hi! > > At some point between 42d088299c (4 May) and f0c9703301 (26 June), a > > deadlock was introduced in ZFS. It is still present as of 9c2823bae9 (4 > > August) and is 100% reproducable just by starting poudriere bulk in a > > 16-core VM and waiting a few hours until deadlkres kicks in. > >

ifconfig: missing or corrupted regdomain database

2023-08-10 Thread void
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

Re: ZFS deadlock in 14

2023-08-10 Thread Kurt Jaeger
Hi! > At some point between 42d088299c (4 May) and f0c9703301 (26 June), a > deadlock was introduced in ZFS. It is still present as of 9c2823bae9 (4 > August) and is 100% reproducable just by starting poudriere bulk in a > 16-core VM and waiting a few hours until deadlkres kicks in. I have a

Re: port lang/python27 does not build in 14.0-CURRENT w/ poudriere

2023-08-10 Thread Matthias Apitz
El día jueves, agosto 10, 2023 a las 09:50:31 +, Alastair Hogge escribió: > On 2023-08-10 17:38, Matthias Apitz wrote: > > El día Wednesday, August 09, 2023 a las 06:04:16PM +0200, Moin Rahman > > escribió: > > > >> This perfectly builds on the latest HEAD without any problem as shared in

Re: port lang/python27 does not build in 14.0-CURRENT w/ poudriere

2023-08-10 Thread Alastair Hogge
On 2023-08-10 17:38, Matthias Apitz wrote: > El día Wednesday, August 09, 2023 a las 06:04:16PM +0200, Moin Rahman > escribió: > >> This perfectly builds on the latest HEAD without any problem as shared in my >> build log. I am not sure what is wrong at your end. Neither can I see any >>

Re: port lang/python27 does not build in 14.0-CURRENT w/ poudriere

2023-08-10 Thread Matthias Apitz
El día Wednesday, August 09, 2023 a las 06:04:16PM +0200, Moin Rahman escribió: > This perfectly builds on the latest HEAD without any problem as shared in my > build log. I am not sure what is wrong at your end. Neither can I see any > fallout on the clusters. > I've cc'ed freebsd-current@

poudriere && --MAKE_ENV-- section

2023-08-10 Thread Matthias Apitz
If I look into the log of a job run in poudriere, from where the section --MAKE_ENV-- OPENSSLBASE=/usr/local OPENSSLDIR=/usr/local/openssl ... --MAKE_ENV-- is pulled in? It is not (my) definition from the jail's make.conf. I have the problem, that a given port (lang/python27) does not