RFC: Using NI_MAXSERV and NI_MAXHOST in the kernel

2023-10-16 Thread Rick Macklem
Hi, I have a patch for a bug identified at last week's testing event, where the FreeBSD NFSv4.1/4.2 client needs to rDNS a DS's address to a FQDN so that it can generate a server principal for Kerberos. (The bug only affects the case of a sec=krb5[ip],pnfs mount, so most will never see it.) Sinc

Re: kernel 100% CPU

2023-10-16 Thread Mateusz Guzik
On 10/14/23, Graham Perrin wrote: > On 03/09/2023 20:25, Mateusz Guzik wrote: > >> … >> >> Sorry mate, neglected to specify: collect sysctl -a once you run into >> the problem. >> >> Once I look at that I'm probably going to ship some debug patches to >> narrow it down. > > > I had what might be t

Re: FreeBSD 14.0-BETA5 Now Available

2023-10-16 Thread Cameron Katri
On 10/16/23 9:54 AM, Ed Maste wrote: On Thu, 12 Oct 2023 at 00:11, Cameron Katri wrote: The FreeBSD-14.0-BETA5-arm64-aarch64-zfs.raw.xz (maybe others, I didn't check) has a rc.conf with a ton of repeated lines. I tried looking at why this would be, but the release scripts to create this image

Re: FreeBSD 14.0-BETA5 Now Available

2023-10-16 Thread Ed Maste
On Thu, 12 Oct 2023 at 00:11, Cameron Katri wrote: > > The FreeBSD-14.0-BETA5-arm64-aarch64-zfs.raw.xz (maybe others, I didn't > check) has a rc.conf with a ton of repeated lines. I tried looking at > why this would be, but the release scripts to create this image went > right over my head. Would

Re: FreeBSD 14.0-BETA5 Now Available

2023-10-16 Thread Ed Maste
On Sat, 7 Oct 2023 at 13:35, György Pásztor wrote: > > Hi Glen, > > The new betas broke the functionality to boot from ventoy. Unfortunately the way Ventoy handles FreeBSD booting is somewhat fragile and this sort of breakage is not surprising. I suspect the Ventoy authors will have to release an

Re: nvme timeout issues with hardware and bhyve vm's

2023-10-16 Thread Chuck Tuffli
On Fri, Oct 13, 2023 at 7:34 PM Warner Losh wrote: ... > Let me now if you see similar messages in stable/14. I think I've fixed all > the > issues with timeouts, though you shouldn't ever seem them in a vm setup > unless something else weird is going on. I'd be interested in a repo case too as