Re: What to do about a few lines in vfs_domount() never executed?

2022-12-14 Thread Rick Macklem
On Wed, Dec 14, 2022 at 2:04 PM Rick Macklem wrote: > > > On Wed, Dec 14, 2022 at 9:15 AM Tomoaki AOKI > wrote: > >> Tracking the commits, it was originally introduced to >> sys/kern/vfs_syscalls.c at r22521 [1][2] (Mon Feb 10 02:22:35 1997 by >> dyson, submitted by h...@freebsd.org) and later c

[2 WEEKS LEFT REMINDER] Call for 2022Q4 quarterly status reports

2022-12-14 Thread Lorenzo Salvadore
Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is December, 31st 2022 for work done since the last round of Quarterly Reports: October 2022 - December 2022. I would like to remind you that reports are collected during the last month of every quarter. Status repo

Re: What to do about a few lines in vfs_domount() never executed?

2022-12-14 Thread Rick Macklem
On Wed, Dec 14, 2022 at 9:15 AM Tomoaki AOKI wrote: > Tracking the commits, it was originally introduced to > sys/kern/vfs_syscalls.c at r22521 [1][2] (Mon Feb 10 02:22:35 1997 by > dyson, submitted by h...@freebsd.org) and later centralized into > sys/kern/vfs_mount.c at r99264 [2]. > > But acco

Re: Status of Intel Hybrid CPU support (Alder Lake/Raptor Lake) support

2022-12-14 Thread Amar Takhar
On 2022-11-14 09:09 +0200, Konstantin Belousov wrote: > > You might use this patch meantime > https://kib.kiev.ua/git/gitweb.cgi?p=deviant3.git;a=commit;h=5d72240a8777b26d5e0a7d2d26bb919d05f60002 Thank you for this patch. On my 13.1 machine it fixed all the panics with a i9-12900KF. It's nice to

Re: What to do about a few lines in vfs_domount() never executed?

2022-12-14 Thread Tomoaki AOKI
Tracking the commits, it was originally introduced to sys/kern/vfs_syscalls.c at r22521 [1][2] (Mon Feb 10 02:22:35 1997 by dyson, submitted by h...@freebsd.org) and later centralized into sys/kern/vfs_mount.c at r99264 [2]. But according to the comment above the codes, maybe it would be intended

Re: Problem compiling CURRENT

2022-12-14 Thread Filippo Moretti
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 sam

Re: Problem compiling CURRENT

2022-12-14 Thread Filippo Moretti
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

2022-12-14 Thread Herbert J. Skuhra
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 Sir I had the following error while try

Problem compiling CURRENT

2022-12-14 Thread Filippo Moretti
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/amd64.amd64