FreeBSD Status Report First Quarter 2024
Here is the first 2024 status report, with 21 entries.
The New Year brings us many new interesting projects, such as the new libsys
that separates system calls from libc and libpthread or work on a graphical
installer for FreeBSD, which will help making
On May 4, 2024, at 09:59, Mark Millard wrote:
> I recently did some of my rare "poudriere bulk -c -a" high-load-average
> style experiments, here on a 7950X3D (amd64) system and I ended up with
> a couple of stuck builders (one per bulk run of 2 runs). Contexts:
>
> # uname -apKU
> FreeBSD
https://www.youtube.com/watch?v=oHO5a4l_8zY
Kenny Wayne Shepherd - Voodoo Child (Slight Return) - KTBA Cruise 2019
youtube.com
I recently did some of my rare "poudriere bulk -c -a" high-load-average
style experiments, here on a 7950X3D (amd64) system and I ended up with
a couple of stuck builders (one per bulk run of 2 runs). Contexts:
# uname -apKU
FreeBSD 7950X3D-UFS 15.0-CURRENT FreeBSD 15.0-CURRENT #142
Nice to see that upstream chose the more correct solution. :)
-Dimitry
> On 2 May 2024, at 11:57, Nuno Teixeira wrote:
>
> Hello Dimitry,
>
> I've quoted your words in upstream PR and it solved with:
>
> Stop using namespace std
>
Hello Dimitry,
I've quoted your words in upstream PR and it solved with:
Stop using namespace std
https://github.com/amsynth/amsynth/commit/6fb79100a6254220e5adc69a1428572539ecc377
I'm using patch globally that unbreak main and rest of supported releases
don't complaint about it.
Thanks!
Hello,
After upgrading from February's 14-stable amd64 to 14.1-PRERELEASE amd64 one of
my systems can't boot anymore. Bootloader was, of course, updated.
It's freezes on "Feeding entropy ." message.
The system installed on pretty old Supermicro server with dual Intel Xeon E5620
CPU, uses BIOS
On 30 Apr 2024, at 14:26, Nuno Teixeira wrote:
>
> I'm lost on build failure of audio/amsynth (updated to version 1.13.3) on
> recent main.
> Thre strange thing is if I use llvm from ports, USES+=llvm, it fails with
> same error so I suspect that something related to main.
>
> Any help is
Hello all,
I'm lost on build failure of audio/amsynth (updated to version 1.13.3) on
recent main.
Thre strange thing is if I use llvm from ports, USES+=llvm, it fails with
same error so I suspect that something related to main.
Any help is welcome and I didn't openned an upstream PR yet.
On Apr 29, 2024, at 20:11, Mark Millard wrote:
> On Apr 29, 2024, at 19:54, Mark Millard wrote:
>
>> On Apr 28, 2024, at 18:06, Philip Paeps wrote:
>>
>>> On 2024-04-18 23:14:22 (+0800), Mark Millard wrote:
On Apr 18, 2024, at 08:02, Mark Millard wrote:
> void wrote on
>
On Apr 29, 2024, at 19:54, Mark Millard wrote:
> On Apr 28, 2024, at 18:06, Philip Paeps wrote:
>
>> On 2024-04-18 23:14:22 (+0800), Mark Millard wrote:
>>> On Apr 18, 2024, at 08:02, Mark Millard wrote:
void wrote on
Date: Thu, 18 Apr 2024 14:08:36 UTC :
> Not sure where
On Apr 28, 2024, at 18:06, Philip Paeps wrote:
> On 2024-04-18 23:14:22 (+0800), Mark Millard wrote:
>> On Apr 18, 2024, at 08:02, 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
Hello!
Who uses their own kernel config, please share the diff between the 14 and 13.x
branches
Thanks.
--
Vladislav V. Prodan
System & Network Administrator
support.od.ua
On 2024-04-18 23:14:22 (+0800), Mark Millard wrote:
On Apr 18, 2024, at 08:02, 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?
Am Sat, 27 Apr 2024 11:28:55 +0200
FreeBSD User schrieb:
Just for the record: running a small "victim NAS" based on an HP EliteDesk 800
G2 mini,
XigmaNAS (latest official version, kernel see below), installing packages from
an official
FreeBSD site for FBSD 13.2-RELEASE, gives me on an ESP32
Am Thu, 25 Apr 2024 21:51:21 +0200
Tomek CEDRO schrieb:
> CP2102 are pretty good ones and never let me down :-)
>
> Is your UART connection to ESP32 working correctly? Can you see the
> boot message and whatever happens next in terminal (cu / minicom)? Are
> RX TX pins not swapped? Power supply
Konstantin, good day!
25.04.2024 0:09, Konstantin Belousov пишет:
On Wed, Apr 24, 2024 at 01:12:39PM +0500, BSD USER wrote:
linking kernel
ld: error: undefined symbol: ktrcapfail
referenced by vfs_lookup.c
vfs_lookup.o:(namei)
referenced by vfs_lookup.c
On Apr 26, 2024, at 18:55, Philip Paeps wrote:
> On 2024-04-18 23:02:30 (+0800), 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.
On 2024-04-18 23:02:30 (+0800), 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 completed build
On Thu, Apr 25, 2024 at 8:51 PM Rick Macklem wrote:
>
> On Thu, Apr 25, 2024 at 8:09 PM Konstantin Belousov wrote:
> >
> > On Thu, Apr 25, 2024 at 07:49:23PM -0700, Rick Macklem wrote:
> > > Hi,
> > >
> > > This week I have been doing active testing as a part of an IETF
> > > bakeathon for
On Thu, Apr 25, 2024 at 8:09 PM Konstantin Belousov wrote:
>
> On Thu, Apr 25, 2024 at 07:49:23PM -0700, Rick Macklem wrote:
> > Hi,
> >
> > This week I have been doing active testing as a part of an IETF
> > bakeathon for NFSv4. During the week I had a NFSv4 client
> > crash. On the surface, it
On Thu, Apr 25, 2024 at 07:49:23PM -0700, Rick Macklem wrote:
> Hi,
>
> This week I have been doing active testing as a part of an IETF
> bakeathon for NFSv4. During the week I had a NFSv4 client
> crash. On the surface, it is straightforward, in that it called
> ncl_doio_directwrite() and the
Hi,
This week I have been doing active testing as a part of an IETF
bakeathon for NFSv4. During the week I had a NFSv4 client
crash. On the surface, it is straightforward, in that it called
ncl_doio_directwrite() and the field called b_caller1 was NULL.
Now, here's the weird part...
Can you isolate out the extraneous stuff and loop tx and rx on a CP2101 board
and send bytes through?
I did a bunch of development on an esp8266 board in the last few weeks and had
no issues, but I’ve no idea if it were the same usb serial chip.
I’ll have a dig around and see if I have
CP2102 are pretty good ones and never let me down :-)
Is your UART connection to ESP32 working correctly? Can you see the
boot message and whatever happens next in terminal (cu / minicom)? Are
RX TX pins not swapped? Power supply okay?
Are boards generic devkits of custom hardware? ESP32 in
Hello,
Host: 15.0-CURRENT FreeBSD 15.0-CURRENT #36 main-n269703-54c3aa02e926: Thu Apr
25 18:48:56
CEST 2024 amd64 or 14-STABLE recently compiled (dmesg/uname not at hand).
Hardware: oldish Z77Pro 4 based Asrock mainboard, a Lenovo T560 notebook,
Fujitsu Esprimo Q5XX
(simple desktop, Pentium
On Wed, Apr 24, 2024 at 01:12:39PM +0500, BSD USER wrote:
> linking kernel
> ld: error: undefined symbol: ktrcapfail
> >>> referenced by vfs_lookup.c
> >>> vfs_lookup.o:(namei)
> >>> referenced by vfs_lookup.c
> >>> vfs_lookup.o:(namei_setup)
> >>> referenced by
Alexander Leidinger writes:
> Gleb Smirnoff writes:
> > I don't have any better idea than ktrace over failing application.
> > Yep, I understand that poudriere will produce a lot.
> Yes, it does. 4.4 GB just for the start of poudriere until the first
> package build fails due to a failed sccache
Am 2024-04-22 18:12, schrieb Gleb Smirnoff:
There were several preparatory commits that were not reverted and one
of them
had a bug. The bug manifested itself as failure to send(2) zero bytes
over
unix/stream. It was fixed with
e6a4b57239dafc6c944473326891d46d966c0264. Can
you please check
Sorry for HTML-trash from previous mail :)
Hi, FreeBSD Community!
I have a teach with FreeBSD and use -CURRENT on my test machine.
And some days ago after
- git pull
- make buildworld
- make buildkernel
There is /etc/src.conf and BSDSERV below, what can cause that error?
Thanks for help!
My
Hi, FreeBSD Community! I have a teach with FreeBSD and use -CURRENT on my test machine.And some days ago after- git pull- make buildworld- make buildkernel There is /etc/src.conf and BSDSERV below, what can cause that error?Thanks for help! kernel building failed with such
On 2024-04-24 02:12:41 (+0800), Mark Millard wrote:
On Apr 19, 2024, at 07:16, Philip Paeps wrote:
On 2024-04-18 23:02:30 (+0800), 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
Hi FreeBSD/main users & developers,
this stabilization week [likely final] status update:
* Netflix testing didn't discover any stability issues with
main-n269602-dd03eafacba9.
* Netflix testing didn't discover any substantial performance
degradations. The data is still being analyzed
On Apr 19, 2024, at 07:16, Philip Paeps wrote:
> On 2024-04-18 23:02:30 (+0800), 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
Hi FreeBSD/main users & developers,
On Mon, Apr 22, 2024 at 01:00:50AM -0700, Gleb Smirnoff wrote:
T> This is an automated email to inform you that the April 2024 stabilization
week
T> started with FreeBSD/main at main-n269602-dd03eafacba9, which was tagged as
T> main-stabweek-2024-Apr.
T>
T>
Thank you.
I updated my current to recent current and confirmed that julia
1.11.0 beta1 builds and runs with the system clang (18.1.4).
On Thu, 18 Apr 2024 00:36:28 +0200
Dimitry Andric wrote:
> On 11 Apr 2024, at 15:07, Hiroo Ono wrote:
> >
> > Hello,
> >
> > I am trying to update the
Alexander,
On Mon, Apr 22, 2024 at 09:26:59AM +0200, Alexander Leidinger wrote:
A> I see a higher failure rate of socket/network related stuff since a while.
A> Those failures are transient. Directly executing the same thing again may
A> or may not result in success/failure. I'm not able to
On Apr 22, 2024, at 3:26 AM, Alexander Leidinger
wrote:
> Hi,
>
> I see a higher failure rate of socket/network related stuff since a while.
> Those failures are transient. Directly executing the same thing again may or
> may not result in success/failure. I'm not able to reproduce this at
Hi FreeBSD/main users & developers:
This is an automated email to inform you that the April 2024 stabilization week
started with FreeBSD/main at main-n269602-dd03eafacba9, which was tagged as
main-stabweek-2024-Apr.
The tag main-stabweek-2024-Apr has been published at
Hi,
I see a higher failure rate of socket/network related stuff since a
while. Those failures are transient. Directly executing the same thing
again may or may not result in success/failure. I'm not able to
reproduce this at will. Sometimes they show up.
Examples:
- poudriere runs with the
On Sun, Apr 21, 2024 at 10:16:55PM +0200, Dag-Erling Smørgrav wrote:
> bob prohaska writes:
> > Apr 20 22:14:37 www su[30398]: in prompt_tty(): caught signal 2
>
> This means someone ran `su` and pressed Ctrl-C instead of entering a
> password when prompted.
Ahh, that would have been me. Thank
I've not managed to track down how yet (ever?), but in two of my upgraded
directory trees the etc/rc.d/nuageinit ended up being missing.
By contrast, the places that were filled in via "installworld distrib-dirs
distribution DB_FROM_SRC=1" usage did have the file. (Installed from the same
In my recent FreeBSD update activity, the following files blocked the "delete
old things" activity from from deleting the related old 17/ subdirectory tree
for clang:
-r--r--r-- 1 root wheel - 8378 Mar 2 19:39:47 2024
bob prohaska writes:
> Apr 20 22:14:37 www su[30398]: in prompt_tty(): caught signal 2
This means someone ran `su` and pressed Ctrl-C instead of entering a
password when prompted.
DES
--
Dag-Erling Smørgrav - d...@freebsd.org
On the serial console on a Pi3 v1.1 (so armv7) I just noticed an
unfamilar message:
Apr 20 22:14:37 www su[30398]: in prompt_tty(): caught signal 2
Several login failures were reported shortly afterward, so
the message seems to have been a console message, not from
the tip session used to
On 2024-04-18 23:02:30 (+0800), 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 completed
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
On Apr 18, 2024, at 08:02, 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
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 completed build
was the one started on Mon, 19 Feb 2024
On 11 Apr 2024, at 15:07, Hiroo Ono wrote:
>
> Hello,
>
> I am trying to update the lang/julia port to 1.11.0 (currently still in beta
> 1).
> I seem to ran across this problem initially reported on MacOS.
> https://github.com/JuliaLang/julia/issues/52067
>
> The llvm team seems to have
Hello,
I am trying to update the lang/julia port to 1.11.0 (currently still in beta 1).
I seem to ran across this problem initially reported on MacOS.
https://github.com/JuliaLang/julia/issues/52067
The llvm team seems to have patched this problem only for Darwin.
(...)
Backup server is https://www.rsync.net/ (free 500GB for FreeBSD
developers).
Nuno Teixeira escreveu (quarta, 10/04/2024 à(s)
13:39):
> With base stack I can complete restic check successfully
> downloading/reading/checking all files from a "big" remote compressed
> backup.
> Changing it
With base stack I can complete restic check successfully
downloading/reading/checking all files from a "big" remote compressed
backup.
Changing it to RACK stack, it fails.
I run this command often because in the past, compression corruption
occured and this is the equivalent of restoring backup
> On 10. Apr 2024, at 13:40, Nuno Teixeira wrote:
>
> Hello all,
>
> @ current 1500018 and fetching torrents with net-p2p/qbittorrent finished
> ~2GB download and connection UP until the end:
>
> ---
> Apr 10 11:26:46 leg kernel: re0: watchdog timeout
> Apr 10 11:26:46 leg kernel: re0:
Hello all,
@ current 1500018 and fetching torrents with net-p2p/qbittorrent finished
~2GB download and connection UP until the end:
---
Apr 10 11:26:46 leg kernel: re0: watchdog timeout
Apr 10 11:26:46 leg kernel: re0: link state changed to DOWN
Apr 10 11:26:49 leg dhclient[58810]: New IP
After the update to main-n269261-1e6db7be6921, head built & booted OK.
FreeBSD 15.0-CURRENT #45 main-n269261-1e6db7be6921: Wed Apr 10 11:11:50 UTC
2024
r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC
amd64 1500018 1500018
Peace,
david
--
David H. Wolfskill
Le 9 avril 2024 18:06:12 GMT+02:00, FreeBSD User a
écrit :
>Am Tue, 9 Apr 2024 17:10:52 +0200
>Rainer Hurling schrieb:
>
>> Am 09.04.24 um 09:20 schrieb Baptiste Daroussin:
>> > On Sat 06 Apr 09:23, Rainer Hurling wrote:
>> >> Am 06.04.24 um 09:05 schrieb FreeBSD User:
>> >>> Hello,
>> >>>
Cy Schubert writes:
> In message , Gleb Smirnoff writes:
> > On Tue, Apr 09, 2024 at 07:02:11PM +0200, FreeBSD User wrote:
> > F> The crash is still present on the most recent checked out sources as of
> mi
> > nutes ago.
> > F> I just checked out on HEAD the latest commits (see below, just for
On Tue, Apr 09, 2024 at 07:02:11PM +0200, FreeBSD User wrote:
F> The crash is still present on the most recent checked out sources as of
minutes ago.
F> I just checked out on HEAD the latest commits (see below, just for the
record and to prevent
F> being wrong here).
F>
F> [...]
F> commit
Am Tue, 9 Apr 2024 09:18:49 -0700
Gleb Smirnoff schrieb:
> On Tue, Apr 09, 2024 at 04:47:07AM -0700, David Wolfskill wrote:
> D> --- trap 0xc, rip = 0x80b208c5, rsp = 0xfe048c204920, rbp =
> 0xfe
> D> 048c204960 ---
> D> __mtx_lock_flags() at __mtx_lock_flags+0x45/frame
On Tue, Apr 09, 2024 at 09:18:49AM -0700, Gleb Smirnoff wrote:
> ...
> D> db>
>
> This should be fixed by just pushed e205fd318a296ffdb7392486cdcec7f660fcffcf.
Thanks! :-)
> Sorry for that!
>
Glad it's idenitfied & addressed.
[Sorry for delay; commute this morning was a bit more
On Tue, Apr 09, 2024 at 04:47:07AM -0700, David Wolfskill wrote:
D> --- trap 0xc, rip = 0x80b208c5, rsp = 0xfe048c204920, rbp =
0xfe
D> 048c204960 ---
D> __mtx_lock_flags() at __mtx_lock_flags+0x45/frame 0xfe048c204960
D> clnt_vc_create() at clnt_vc_create+0x4f4/frame
Am Tue, 9 Apr 2024 17:10:52 +0200
Rainer Hurling schrieb:
> Am 09.04.24 um 09:20 schrieb Baptiste Daroussin:
> > On Sat 06 Apr 09:23, Rainer Hurling wrote:
> >> Am 06.04.24 um 09:05 schrieb FreeBSD User:
> >>> Hello,
> >>>
> >>> after updating (portmaster and make) ports-mgmt/ports from
On Tue, Apr 9, 2024 at 8:04 AM Rick Macklem wrote:
>
> On Tue, Apr 9, 2024 at 7:46 AM Rick Macklem wrote:
> >
> > On Tue, Apr 9, 2024 at 4:47 AM David Wolfskill wrote:
> > >
> > > Machine had been running:
> > >
> > > FreeBSD 15.0-CURRENT #43 main-n269202-4e7aa03b7076: Mon Apr 8 11:19:58
> >
Am 09.04.24 um 09:20 schrieb Baptiste Daroussin:
On Sat 06 Apr 09:23, Rainer Hurling wrote:
Am 06.04.24 um 09:05 schrieb FreeBSD User:
Hello,
after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0
on CURRENT and
14-STABLE, I can't update several ports:
www/apache24
Am 06.04.24 um 09:56 schrieb FreeBSD User:
Am Sat, 6 Apr 2024 09:23:30 +0200
Rainer Hurling schrieb:
Am 06.04.24 um 09:05 schrieb FreeBSD User:
Hello,
after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0
on CURRENT
and 14-STABLE, I can't update several ports:
On Tue, Apr 9, 2024 at 7:46 AM Rick Macklem wrote:
>
> On Tue, Apr 9, 2024 at 4:47 AM David Wolfskill wrote:
> >
> > Machine had been running:
> >
> > FreeBSD 15.0-CURRENT #43 main-n269202-4e7aa03b7076: Mon Apr 8 11:19:58 UTC
> > 2024
> >
On Tue, Apr 9, 2024 at 4:47 AM David Wolfskill wrote:
>
> Machine had been running:
>
> FreeBSD 15.0-CURRENT #43 main-n269202-4e7aa03b7076: Mon Apr 8 11:19:58 UTC
> 2024
> r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC
> amd64 1500018 1500018
>
> This was an
Machine had been running:
FreeBSD 15.0-CURRENT #43 main-n269202-4e7aa03b7076: Mon Apr 8 11:19:58 UTC
2024
r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC
amd64 1500018 1500018
This was an in-place source update, after updating sources to
On Sat 06 Apr 09:23, Rainer Hurling wrote:
> Am 06.04.24 um 09:05 schrieb FreeBSD User:
> > Hello,
> >
> > after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 ->
> > 1.21.0 on CURRENT and
> > 14-STABLE, I can't update several ports:
> >
> > www/apache24
> > databases/redis
> >
On Sat 06 Apr 09:05, FreeBSD User wrote:
> Hello,
>
> after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0
> on CURRENT and
> 14-STABLE, I can't update several ports:
>
> www/apache24
> databases/redis
>
> pkg core dumps while performing installation. apache24 and
Hi,
I have a hunch that no one uses the WebNFS stuff, which is done via exports(5)
using the -public or -webnfs exports options.
I would like to deprecate these exports options, but thought I'd ask
in case anyone
uses them?
rick
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), disabling port 2
>
> Here is my
Am Sat, 6 Apr 2024 09:05:00 +0200
FreeBSD User schrieb:
> Hello,
>
> after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0
> on CURRENT and
> 14-STABLE, I can't update several ports:
>
> www/apache24
> databases/redis
>
> pkg core dumps while performing installation.
Am Thu, 4 Apr 2024 01:14:52 -0500
Kyle Evans schrieb:
> On 4/4/24 00:49, FreeBSD User wrote:
> > Hello,
> >
> > I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1:
> >
> > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094
> >
> > FreeBSD starting with 14-STABLE seems to use
Am 06.04.24 um 09:05 schrieb FreeBSD User:
Hello,
after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0
on CURRENT and
14-STABLE, I can't update several ports:
www/apache24
databases/redis
pkg core dumps while performing installation. apache24 and redis are ports I
Hello,
after updating (portmaster and make) ports-mgmt/ports from 1.20.9_1 -> 1.21.0
on CURRENT and
14-STABLE, I can't update several ports:
www/apache24
databases/redis
pkg core dumps while performing installation. apache24 and redis are ports I
realized this
misbehaviour on ALL 14-STABLE
On April 4, 2024 07:50:55 FreeBSD User wrote:
Hello,
I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094
FreeBSD starting with 14-STABLE seems to use xz 5.6.0, but my limited
skills do not allow me
to judge wether the
On 4/4/24 00:49, FreeBSD User wrote:
Hello,
I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094
FreeBSD starting with 14-STABLE seems to use xz 5.6.0, but my limited skills do
not allow me
to judge wether the described
Am Thu, 04 Apr 2024 08:06:26 +0200 (CEST)
sth...@nethelp.no schrieb:
> >> I have to report to my superiors (we're using 14-STABLE and CURRENT
> >> and I do so in private),
> >> so I would like to welcome any comment on that.
> >
> > No it does not affect FreeBSD.
> >
> > The autoconf script
>> I have to report to my superiors (we're using 14-STABLE and CURRENT
>> and I do so in private),
>> so I would like to welcome any comment on that.
>
> No it does not affect FreeBSD.
>
> The autoconf script checks that it is running in a RedHat or Debian
> package build environment before
On 04-04-24 05:49, FreeBSD User wrote:
Hello,
I just stumbled over this CVE regarding xz 5.6.0 and 5.6.1:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-3094
FreeBSD starting with 14-STABLE seems to use xz 5.6.0, but my limited skills do
not allow me
to judge whether the
Shouldn't be a problem. The socket used for lookup is
AF_UNIX (uses unp_connectat) and the NFS socket
will always be UDP or TCP.
Different sockets imply different socket locks.
At least that's my interpretation, rick
On Wed, Apr 3, 2024 at 11:33 AM Bjoern A. Zeeb
wrote:
>
>
> NFS root boot of
NFS root boot of a Lab machine; calling wpa_cli:
Thilock order reversal:
1st 0x0001d4e1c800 so_snd_sx (so_snd_sx, sx) @
/usr/src/sys/kern/uipc_socket.c:4020
2nd 0xa020cb20e930 nfs (nfs, lockmgr) @ /usr/src/sys/kern/vfs_lookup.c:1083
lock order nfs -> so_snd_sx established at:
#0
On Tue, Apr 2, 2024 at 11:53 AM Tomoaki AOKI
wrote:
> On Tue, 02 Apr 2024 08:53:15 -0700
> Chris wrote:
>
> > On 2024-04-02 04:32, Tomoaki AOKI wrote:
> > > On Tue, 02 Apr 2024 00:42:23 -0700
> > > Chris wrote:
> > >
> > >> On 2024-04-01 22:51, Kevin Oberman wrote:
> > >> > On Mon, Apr 1, 2024
On Tue, 02 Apr 2024 08:53:15 -0700
Chris wrote:
> On 2024-04-02 04:32, Tomoaki AOKI wrote:
> > On Tue, 02 Apr 2024 00:42:23 -0700
> > Chris wrote:
> >
> >> On 2024-04-01 22:51, Kevin Oberman wrote:
> >> > On Mon, Apr 1, 2024 at 3:05 PM Chris wrote:
> >> >
> >> >> I experience challenges
On 2024-04-02 04:32, Tomoaki AOKI wrote:
On Tue, 02 Apr 2024 00:42:23 -0700
Chris wrote:
On 2024-04-01 22:51, Kevin Oberman wrote:
> On Mon, Apr 1, 2024 at 3:05 PM Chris wrote:
>
>> I experience challenges running FreeBSD on my Alder Lake laptop.
>> With some help on the list and Bugzilla, I
On Tue, 02 Apr 2024 00:42:23 -0700
Chris wrote:
> On 2024-04-01 22:51, Kevin Oberman wrote:
> > On Mon, Apr 1, 2024 at 3:05 PM Chris wrote:
> >
> >> I experience challenges running FreeBSD on my Alder Lake laptop.
> >> With some help on the list and Bugzilla, I was able to get Graphics
> >>
On Mon, Apr 01, 2024 at 10:51:10PM -0700, Kevin Oberman wrote:
>
> I have a T16 and ran into that issue. It may be that BIOS changes have
> broken things, but I found that, by default, the F keys control volume,
> screen brightness, and many other things. I can use Fn+F[1-12] to perform
>
On 2024-04-01 22:51, Kevin Oberman wrote:
On Mon, Apr 1, 2024 at 3:05 PM Chris wrote:
I experience challenges running FreeBSD on my Alder Lake laptop.
With some help on the list and Bugzilla, I was able to get Graphics
WiFi at least working. But still wasn't as stable as running on
more dated
On Mon, Apr 1, 2024 at 3:05 PM Chris wrote:
> I experience challenges running FreeBSD on my Alder Lake laptop.
> With some help on the list and Bugzilla, I was able to get Graphics
> WiFi at least working. But still wasn't as stable as running on
> more dated CPU's. As it is; I'm only able to
On 2024-04-01 14:57, Michael Gmelin wrote:
You never responded to my (and T’s) message - so I assume the suggestions
made no
difference?
Right, and thank you for the reply. I (indirectly) answered it here
when I indicated that I had no references to "keyboard settings in
my rc.conf(5)". :) Any
I experience challenges running FreeBSD on my Alder Lake laptop.
With some help on the list and Bugzilla, I was able to get Graphics
WiFi at least working. But still wasn't as stable as running on
more dated CPU's. As it is; I'm only able to use CURRENT. Beginning
of last week, in hopes of
On Mar 30, 2024, at 12:44, Lexi Winter wrote:
> 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
>
(...)
initial_turbo
https://www.raspberrypi.com/documentation/computers/config_txt.html#overclocking
Nuno Teixeira escreveu (domingo, 31/03/2024 à(s)
19:59):
> Hello,
>
> If you got a fan in your rpi4 box, you could try to overclock it.
> If not, there is a funcionality in config.txt to
Hello,
If you got a fan in your rpi4 box, you could try to overclock it.
If not, there is a funcionality in config.txt to overclock it just for a
few seconds at boot time.
I can't remember the funtion but I'm looking at:
https://www.raspberrypi.com/documentation/computers/config_txt.html
Am 2024-03-29 18:21, schrieb Alexander Leidinger:
Am 2024-03-29 18:13, schrieb Mark Johnston:
On Fri, Mar 29, 2024 at 04:52:55PM +0100, Alexander Leidinger wrote:
Hi,
sources from 2024-03-11 work. Sources from 2024-03-25 and today don't
work
(see below for the issue). As the monthly
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
(For the not working Wifi chip, I use at the moment an USB-Wifi dongle,
Realtek RTL8191S WLAN Adapter, which works fine).
I also can't get Xorg plus twm up; it says in /var/log/Xorg.0.log at the end:
..
REDWOOD, ATI Mobility Radeon Graphics, CEDAR, ATI FirePro 2270,
ATI Radeon
On Fri, 29 Mar 2024 19:02:37 -0700
Chris wrote:
> I just poured the dist files onto an earlier 15 (after removing
> the earlier version). After booting into the new install, I no longer
> had any other tty's other than ttyv0. Alt+Fn has no affect, I'm only
> getting ttyv0. getty(8) is running,
1 - 100 of 138154 matches
Mail list logo
