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
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
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
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' didn't pull
/usr/src/sys/contrib/dev/
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
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
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
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
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
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
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
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
--
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 mode' for UFS
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
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)
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
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
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
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,
will it have
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
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"
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 ?
--
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.
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'
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
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
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
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
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
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.arc.max
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
--
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
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.
--
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
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
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?
--
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.
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
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
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
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
--
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
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.
--
Maybe the question I need to ask before asking about this is
"what is the best tcp algo to use in the situation where:
1. gigabit fibre on consumer FTTP
2. on a freebsd host whose purpose is hosting bhyve guests"
I expected to load cc_vegas as, from what I've read, it's the
best (most
thanks everyone it's working normally now after full buildworld
kernel then forced rebuild of all ports from their updated
sources
--
On Sun, Jul 09, 2023 at 05:17:38PM +0100, void wrote:
Hi,
On a fresh 14-current install (main-n263444-653738e895ba)
I try to use pkg for anything and this error
happens:
# pkg install doas
The package management tool is not yet installed on your system.
Do you want to fetch and install it now
Hi,
On a fresh 14-current install (main-n263444-653738e895ba)
I try to use pkg for anything and this error
happens:
# pkg install doas
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]: y
Bootstrapping pkg from
On Sat, Apr 15, 2023 at 09:56:34AM +0100, Graham Perrin wrote:
Is the recent situation unusual enough to warrant an entry in UPDATING?
yeah I'd say so.
Also does this affect 13-stable and the recent 13.2-RELEASE or
just -current?
--
On Thu, Mar 30, 2023 at 07:30:15PM -0700, Mark Millard wrote:
Warner Losh wrote on
Date: Thu, 30 Mar 2023 22:15:38 UTC :
On Thu, Mar 30, 2023, 3:45 PM void wrote:
> On Thu, Mar 30, 2023 at 12:56:53PM -0700, Mark Millard wrote:
>
> >To my knowledge, FreeBSD has not actively sup
On Thu, Mar 30, 2023 at 12:56:53PM -0700, Mark Millard wrote:
To my knowledge, FreeBSD has not actively supported newer
FreeBSD building older FreeBSD across versions.
Are you sure? I routinely build & run 12.4 and 12-stable bhyve and
poudriere jail instances on -current.
--
flushed, but I'm glad my warning was able to flag a bug. :-)
If "void" is comfortable with kernel hacking, it would be great to confirm
that the warning is indeed coming from the transmit side not being flushed;
a printf("drain = %d\n", drain); would be sufficient.
And yes, only e
hello freebsd-current@,
this started appearing in dmesg
ns8250: UART FCR is broken
ns8250: UART FCR is broken
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
ns8250: UART FCR is broken
uart0: console (9600,n,8,1)
ns8250: UART FCR is broken
ns8250: UART FCR is broken
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
# pkg bootstrap
The package management tool is not yet installed on your system.
Do you want to
On Thu, Sep 15, 2022 at 01:45:11PM -0300, Ivan Quitschal wrote:
capabilities=68009b
ether 54:af:97:86:be:2c
inet 192.168.0.35 netmask 0xff00 broadcast 192.168.0.255
media: Ethernet 1000baseT
status: active
supported media:
media
On Mon, Oct 23, 2000 at 06:30:29PM -0400, John W. De Boskey wrote:
5. At this time, remove ALL MFS filesystems from /etc/fstab.
They can be hand mounted after bootup or via a local rc
startup script.
You can leave them in, with option "noauto", and mount them later with
"mount -a -t
How does OpenBSD handle this issue? Anyone know?
--
Ben
220 go.ahead.make.my.day ESMTP Postfix
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, Apr 27, 2000 at 01:06:16AM -0500, Michael C . Wu wrote:
On Thu, Apr 27, 2000 at 01:14:02AM +0400, Andrey A. Chernov scribbled:
| I often notice processes hanging forever on exit's ttywait when TCP
| connection dropped. Here is a patch I plan to commit which restrict
| waiting for
57 matches
Mail list logo
