[Bug 201735] zpool export fails after process accesses .zfs/snapshot directory

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201735

Graham Perrin  changed:

   What|Removed |Added

   Severity|Affects Many People |Affects Some People
   Assignee|b...@freebsd.org|f...@freebsd.org
 Status|New |Open

--- Comment #1 from Graham Perrin  ---
Not reproducible for me with OpenZFS in CURRENT. 

Below: 

* a first attempt to export was made very soon after changing directory

* the second attempt, a few seconds later, succeeded.

root@mowa219-gjp4-8570p-freebsd:~ # mount | grep Transcend
Transcend on /media/t1000 (zfs, local, nfsv4acls)
Transcend/VirtualBox on /media/t1000/VirtualBox (zfs, local, nfsv4acls)
root@mowa219-gjp4-8570p-freebsd:~ # cd /media/t1000/.zfs/snapshot
root@mowa219-gjp4-8570p-freebsd:/media/t1000/.zfs/snapshot # cd
root@mowa219-gjp4-8570p-freebsd:~ # time zpool export Transcend
cannot unmount '/media/t1000/VirtualBox': pool or dataset is busy
0.006u 0.006s 0:00.02 0.0%  0+0k 3+0io 3pf+0w
root@mowa219-gjp4-8570p-freebsd:~ # date ; time ; zpool export Transcend
Mon Sep 11 07:49:41 BST 2023
0.394u 1.228s 17:29:44.80 0.0%  389+199k 1304+0io 953pf+0w
root@mowa219-gjp4-8570p-freebsd:~ # 



% zfs version
zfs-2.2.99-FreeBSD_g804414aad
zfs-kmod-2.2.99-FreeBSD_g804414aad
% zpool version
zfs-2.2.99-FreeBSD_g804414aad
zfs-kmod-2.2.99-FreeBSD_g804414aad
% uname -aKU
FreeBSD mowa219-gjp4-8570p-freebsd 15.0-CURRENT FreeBSD 15.0-CURRENT amd64
150 #11 main-n265135-07bc20e4740d-dirty: Sat Sep  2 19:40:08 BST 2023
grahamperrin@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG
amd64 150 150
%

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 201624] BTX halted using 10.x with root on ZFS supermicro AMD

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201624

Graham Perrin  changed:

   What|Removed |Added

 CC||grahamper...@gmail.com
 Status|New |Open

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 201082] gptzfsboot regression, "panic: bd_strategy: 114688 bytes I/O not multiple of block size"

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201082

Graham Perrin  changed:

   What|Removed |Added

 CC||grahamper...@gmail.com
 Status|New |Open

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 207188] gptzfsboot may choose wrong pool

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207188

Graham Perrin  changed:

   What|Removed |Added

 CC||grahamper...@gmail.com
 Status|New |Open

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 210986] Conflict ZFS with GEOM ?

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210986

Graham Perrin  changed:

   What|Removed |Added

 CC||grahamper...@gmail.com
 Status|New |Open

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 211767] boot1.efi probing doesn't find ZFS pool unless delaying execution of boot1 a few seconds after power on

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211767

Graham Perrin  changed:

   What|Removed |Added

 Status|New |Open
 CC||grahamper...@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 221987] ZFS does not validate the sharenfs parameter

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221987

Graham Perrin  changed:

   What|Removed |Added

 Status|New |Open
   Assignee|b...@freebsd.org|f...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 231457] Out of swap space on ZFS

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231457

Graham Perrin  changed:

   What|Removed |Added

 Status|New |Open
   Assignee|b...@freebsd.org|f...@freebsd.org
   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2735
   ||41

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 232021] zfs cannot mount 'dataset': Insufficient privileges

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232021

Graham Perrin  changed:

   What|Removed |Added

 Status|New |Open
   Assignee|b...@freebsd.org|f...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 234741] Loader fails to load from ZFS with strip sets using raw disks

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234741

Graham Perrin  changed:

   What|Removed |Added

 CC||grahamper...@gmail.com
 Status|New |Open

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 235125] Process was killed: out of swap space on gmirror + zfs

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235125

Graham Perrin  changed:

   What|Removed |Added

 Status|New |Open
 CC||grahamper...@gmail.com

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 235388] gptzfsboot does not boot ZFS pool made from whole disks (regression), part two

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235388

Graham Perrin  changed:

   What|Removed |Added

 CC||grahamper...@gmail.com
 Status|New |Open

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 238518] make buildkernel fails due to a symlink (and/or zfs)

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238518

Graham Perrin  changed:

   What|Removed |Added

 Status|New |Open

--- Comment #1 from Graham Perrin  ---
Overcome by events?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 192715] zfs diff does not report accurate file deletion differences

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192715

Graham Perrin  changed:

   What|Removed |Added

 Status|New |Open
   See Also||https://github.com/zfsonlin
   ||ux/zfs/issues/2081
   Assignee|b...@freebsd.org|f...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268393] system always reboots once from a powered off state

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393

--- Comment #72 from Ivan Rozhuk  ---
(In reply to Oleh Hushchenkov from comment #69)

I suggest commit 2 and 3 together to make sure that we never see this panic
again.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 273373] fails to build in POSIX mode due to namespace pollution

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273373

Jan Beich  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|i...@freebsd.org
  Flags||mfc-stable14?

--- Comment #11 from Jan Beich  ---
Landed in base fb5daae920ba but no MFC yet to stable/14 and releng/14.0.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Problem reports for b...@freebsd.org that need special attention

[bugzilla-noreply]

To view an individual PR, use:
  https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).

The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and obsolete releases.

Status  |Bug Id | Description
+---+---
New |197876 | [devfs] an error in devfs leads to data loss and  
New |202362 | ntp: restore refclocks selection (10.2-RELEASE re 
New |202740 | vi/ex string substitution problem when there is m 
New |204097 | witness_initialize() does not perform bound check 
New |206336 | [patch] usr.sbin/freebsd-update allow proxy confi 
New |209213 | UEFI Loader shows only black screen with Nvidia G 
New |210804 | installerconfig - using ZFS create in custom scri 
New |223470 | freebsd-update: Cannot identify running kernel (/ 
New |230620 | "install -d" issue
New |235085 | [PATCH] Option to make rc.d/sysctl more verbose ( 
New |252123 | fetch(3): Fix wrong usage of proxy when request i 
Open|177821 | sysctl: Some security.jail nodes are funky, dupli 
Open|182466 | [headers] [patch] make  self-contained  
Open|183618 | [panic] Dell PowerEdge R620 -- PERC H710 Mini (mf 
Open|192573 | Add ps(1) option: Print process start time in sec 
Open|194925 | [pf] [ifconfig] interface group keywords do not w 
Open|197921 | scheduler: Allow non-migratable threads to bind t 
Open|206528 | Emulex LPe 16002 FC HBA Not Recognized by oce(4)  
Open|206649 | cyapa(4): Add common gestures for Cypress APA I2C 
Open|212608 | sockstat(1) and lsof(8) can not identity the owne 
Open|220246 | syslogd does not send RFC3164-conformant messages 
Open|221305 | Mouse cursor loss when moving cursor while loadin 
Open|221550 | kern.bootfile returns only /kernel on mips64 (ERL 
Open|221854 | makefs: Reject UFS labels that are too long to fi 
Open|226893 | freebsd-update: Support patchlevel argument for f 
Open|231810 | [build] release always fails with "mkimg: partiti 
Open|233578 | Unprivileged local user can prevent other users l 
Open|233988 | freebsd-update: Improve progress output on termin 
Open|236718 | system panics with message: vm_fault_hold: fault  
Open|237287 | moused(8) ignores button release events in virtua 
Open|237924 | Possible infinite loop in function empty_aux_buff 
Open|238183 | cam/scsi/scsi_sa.c: warnings issued by static ana 
Open|238486 | Possible buffer overflow bug in sc_allocate_keybo 
Open|238550 | Touchpad (via SMBus) not working: Synaptics (SYN1 
Open|238638 | mfi: Remove unnecessary pointer printing in mfi.c 
Open|238837 | init: Remove P_SYSTEM flag from PID 1 to allow ea 
Open|241697 | i915kms: Kernel panic loading module on custom ke 
Open|247132 | Fix build error: use of undeclared identifier 'cp 
Open|248352 | mfi(4): Remove RAID map sync functionality
Open|257149 | CFLAGS not passed to whole build  

40 problems total for which you should take action.

[Bug 268393] system always reboots once from a powered off state

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393

--- Comment #71 from Warner Losh  ---
This and Mark's comment lead me to believe we are getting stray interrupts of
various flavors. The 0xfff hack will keep things working while we're
accessing the device in an isr with the card unmapped or asleep.I think this
also suggests some sloppiness with establishing or tearing down interrupts.
Marks case of getting an interrupt before things are complete is another
example.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268393] system always reboots once from a powered off state

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393

--- Comment #70 from Oleh Hushchenkov  ---
(In reply to Mark Johnston from comment #68)
> I'm not particularly sure why my commit would introduce a problem there.

I'm not familiar with the code base, but for me it looks like D34117 added
"intsts != 0x" to "while()" condition and thus changed some timings.

Important part is that removing "intsts != 0x" form "while()" condition
fixes the issue, but suspend stops working again.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 258010] kqueue shortcoming for desktop usage

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258010

Steve Wills  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2736
   ||69

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 213501] Screen blank after sleep/resume

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213501

--- Comment #10 from Graham Perrin ◐  ---
(In reply to Tobias from comment #2 (2016-10-15, not seen in Bugzilla since
then))

I assume that this bug can be closed as either: 

a) overcome by events; or 

b) working as expected (from the attachments, I can't tell which kernel module,
if any, was loaded for the NVIDIA Quadro K2100M). 

Thanks

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 213501] Screen blank after sleep/resume

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213501

Graham Perrin  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2609
   ||94

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 213501] Screen blank after sleep/resume

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213501

Graham Perrin ◐  changed:

   What|Removed |Added

 CC||grahamper...@gmail.com

--- Comment #9 from Graham Perrin ◐  ---
(In reply to miner.ben07 from comment #8)

> … seems to have something to do with the DRM driver, …

Bug 260994 key phrase: Kernel Mode Setting.

 nvidia,
more specfically 
nvidia-modeset and 
x11/nvidia-driver-470.

Re: ,
x11/nvidia-driver-470 lacks what's required for nvidia-drm. 

This HP ZBook 17 G2: 

* does wake from sleep with nvidia-driver-470 _without_ DRM

* failed to wake from sleep when I used the system console frame buffer 
  (an X.Org configuration) instead of nvidia-modeset (the kernel module). 

The failure is consistent with , 

> Features that will not work with the system console frame buffer include:
> 
> sleep and wake (suspend and resume) of the computer.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268393] system always reboots once from a powered off state

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393

--- Comment #69 from Oleh Hushchenkov  ---
(In reply to Mark Johnston from comment #68)
Just moved hdac_irq_alloc() call in hdac_attach() to be after the
hdac_rirb_init() call and rebuilt the kernel.

It fixed the issue for me.

Now I'm wondering which patch should I use?
1. Removing "intsts != 0x" from "while (intsts != 0x && (intsts
& HDAC_INTSTS_GIS) != 0)" in "hdac_intr_handler()".
2. Adding "rirb_base == NULL" and "rirb == NULL" checks in "hdac_rirb_flush()".
3. Moving "hdac_irq_alloc()" to be after "hdac_rirb_init()" in "hdac_attach()".

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 268393] system always reboots once from a powered off state

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268393

--- Comment #68 from Mark Johnston  ---
(In reply to Jonathan Vasquez from comment #18)
Looking at this log, it seems that we're getting an interrupt before hdac2 has
finished initializing itself.  In particular, hdac_attach() allocates an MSI
vector prior to allocating the RIRB DMA buffer.

I'm not particularly sure why my commit would introduce a problem there.  Could
anyone affected by the problem please test moving the hdac_irq_alloc() call in
hdac_attach() to just after the hdac_rirb_init() call?  I can't easily provide
a patch at the moment but it should be easy to do.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 273705] default device.hints prevents booting on modern hardware

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273705

Bug ID: 273705
   Summary: default device.hints prevents booting on modern
hardware
   Product: Base System
   Version: 14.0-CURRENT
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: conf
  Assignee: b...@freebsd.org
  Reporter: free...@darkain.com

/boot/device.hints by default contains information for scanning very old legacy
hardware, such as floppy disk controllers and the ISA bus. One of these items
is also the old AT keyboard interface via the ISA bus.

On modern hardware such as the Steam Deck, these legacy interfaces no longer
exist, preventing FreeBSD from booting properly. Commenting the lines out in
the file allows it to boot properly.

However, it is only a matter of time until more and more systems drop these
legacy interfaces, the Steam Deck is just one of, if not the first device that
we've seen this on.

At least on AMD64, I think it may be time to remove these references to ISA bus
scanning, as its causing real issues with the boot process.

---

And before anyone jumps in with some harsh comment about testing FreeBSD on the
Steam Deck because it is a "game console" - the hardware inside is essentially
an AMD APU based laptop. It acts and functions almost identically to any other
laptop device. The only major difference is the physical form factor. The
changes seen on this device to remove legacy interfaces from the APU most
likely will also hit mainline APUs before long, so in my opinion it is better
to tackle this now rather than later.

---

Reference:
https://wiki.freebsd.org/Laptops/Steam_Deck

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 273085] clock_gettime(CLOCK_MONOTONIC_COARSE, *struct timespec) fails with 32bit program on 64bit machine

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273085

Minsoo Choo  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|In Progress |Closed

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 273694] [patch] _bus_dmamap_count_pages() may miscount

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273694

Mina Galić  changed:

   What|Removed |Added

 CC||free...@igalic.co
 Status|New |Open

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 273414] linuxulator regression in symlinks under zfs

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273414

Dmitry Chagin  changed:

   What|Removed |Added

 Status|New |In Progress

--- Comment #3 from Dmitry Chagin  ---
https://people.freebsd.org/~dchagin/nc.patch

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 273664] ovpn(4) DCO module doesn't support "multihome" option

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273664

--- Comment #2 from Marek Zarychta  ---
In other words, the outgoing interface for encrypted traffic is chosen on the
basis of the FIB lookup instead of preserving the IP address for the VPN
connection and sending the traffic from the same interface it was received on.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 273694] [patch] _bus_dmamap_count_pages() may miscount

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273694

Daniel Engberg  changed:

   What|Removed |Added

 CC||dii...@freebsd.org,
   ||mho...@freebsd.org

--- Comment #1 from Daniel Engberg  ---
Mitchell, is this something you can have a look at?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 273694] [patch] _bus_dmamap_count_pages() may miscount

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273694

Bug ID: 273694
   Summary: [patch] _bus_dmamap_count_pages() may miscount
   Product: Base System
   Version: 14.0-CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: js...@gmx.com

Created attachment 244746
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=244746&action=edit
patch files for different architectures

While debugging jh7110 board's MMC driver I found out that the problem had been
a faulty algorithm in DMA code.

_bus_dmamap_count_pages() in sys/riscv/riscv/busdma_bounce.c is called to count
a number of new bounce pages needed in order to complete the DMA transfer (this
happens at least when physical addresses used for data segments go out of DMA
address range). However, unlike a function bounce_bus_dmapmap_load_buffer()
which calls it, _bus_dmamap_count_pages() does not take into account that
segment size may be limited by dmat->common.maxsegsz which is set when creating
bus_dma_tag_t in the driver code. This may lead to a wrong number of pages
counted and thus some needed bounce pages will not be created.

In my case the consequence was that some addresses outside of device's 32-bit
DMA range were assigned to descriptors (IO data structures read by DMA
controller) which nevertheless can only contain first 32 bits of those
addresses. This causes the whole booting process to halt. After a failed
transfer MMC driver code stays waiting for a next interrupt that never arrives.

I found that the _bus_dmamap_count_pages() is similarly deficient in other
architectures though it's possible this bug hasn't surfaced previously. My
actual case is related to charcteristics of Designware's MMC devices (see
comments on file dwmmc.c, line 140) which imply maximum size for data segments.

I don't see any reason why this issue couldn't affect other architectures as
well if circumstances are right, so I've supplied patches for each architecture
in an attachment file. ARM and powerpc have the _bus_dmamap_count_pages()
function in file busdma_machdep.c while other archs (including ARM64) have it
in busdma_bounce.c

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 273693] download.freebsd.org README updates

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273693

Bug ID: 273693
   Summary: download.freebsd.org README updates
   Product: Documentation
   Version: Latest
  Hardware: Any
   URL: https://download.freebsd.org/
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: Manual Pages
  Assignee: b...@freebsd.org
  Reporter: grahamper...@gmail.com
CC: d...@freebsd.org, g...@freebsd.org

 is outdated in a few areas. 

Much more easily patched: 
includes 14.0-CURRENT as an example, might be updated to 15.0-CURRENT.

Cc gjb@ only because he was to thank for an August 2023 update to the latter.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 273690] mdoc .Fx macro: Unknown FreeBSD version

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273690

Wolfram Schneider  changed:

   What|Removed |Added

 Depends on||273599
   Assignee|b...@freebsd.org|wo...@freebsd.org
 Status|New |Open


Referenced Bugs:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273599
[Bug 273599] outdated textproc/groff/files/mdoc.local
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 273690] mdoc .Fx macro: Unknown FreeBSD version

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273690

Bug ID: 273690
   Summary: mdoc .Fx macro: Unknown FreeBSD version
   Product: Documentation
   Version: Latest
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: Manual Pages
  Assignee: b...@freebsd.org
  Reporter: wo...@freebsd.org
CC: d...@freebsd.org

Some of our manual pages use arguments unknown to the groff configuration. E.g.

1. trailing dot ("."):
mdoc warning: .Fx: Unknown FreeBSD version '13.0.'

2. a version which is missing in mdoc.local, see PR 273599
mdoc warning: .Fx: Unknown FreeBSD version '14.0'

3. wrong usage of the .Fx macro
mdoc warning: .Fx: Unknown FreeBSD version 'imposes'

How to repeat:

printf '#!/bin/sh\nzcat "$1" | nroff -mandoc\n' > m.sh
find /usr/share/man -name  '*.gz' -type f -print0 | xargs -0 -n1 sh m.sh >
/dev/null 2> m.log

 109 mdoc warning: .Fx: Unknown FreeBSD version '14.0' 
  40 mdoc warning: .Fx: Unknown FreeBSD version '13' 
  17 mdoc warning: .Fx: Unknown FreeBSD version '14' 
  14 mdoc warning: .Fx: Unknown FreeBSD version '13.2' 
  10 mdoc warning: .Fx: Unknown FreeBSD version '13.0.' 
  10 mdoc warning: .Fx: Unknown FreeBSD version '11' 
   9 mdoc warning: .Fx: Unknown FreeBSD version '12' 
   6 mdoc warning: .Fx: Unknown FreeBSD version '13.1' 
   3 mdoc warning: .Fx: Unknown FreeBSD version '15.0' 
   3 mdoc warning: .Fx: Unknown FreeBSD version '12.2' 
   2 mdoc warning: .Fx: Unknown FreeBSD version 'version' 
   2 mdoc warning: .Fx: Unknown FreeBSD version 'imposes' 
   2 mdoc warning: .Fx: Unknown FreeBSD version '9.x' 
   2 mdoc warning: .Fx: Unknown FreeBSD version '9' 
   2 mdoc warning: .Fx: Unknown FreeBSD version '12.3' 
   2 mdoc warning: .Fx: Unknown FreeBSD version '10.0.' 
   1 mdoc warning: .Fx: Unknown FreeBSD version 'v5' 
   1 mdoc warning: .Fx: Unknown FreeBSD version 'v3.' 
   1 mdoc warning: .Fx: Unknown FreeBSD version 'units' 
   1 mdoc warning: .Fx: Unknown FreeBSD version 'provides' 
   1 mdoc warning: .Fx: Unknown FreeBSD version 'implementation' 
   1 mdoc warning: .Fx: Unknown FreeBSD version 'extensions,' 
   1 mdoc warning: .Fx: Unknown FreeBSD version 'STABLE' 
   1 mdoc warning: .Fx: Unknown FreeBSD version 'Foundation.' 
   1 mdoc warning: .Fx: Unknown FreeBSD version 'CURRENT' 
   1 mdoc warning: .Fx: Unknown FreeBSD version '2.2.0' 
   1 mdoc warning: .Fx: Unknown FreeBSD version '14.0.' 
   1 mdoc warning: .Fx: Unknown FreeBSD version '14.0-CURRENT' 
   1 mdoc warning: .Fx: Unknown FreeBSD version '13.3' 
   1 mdoc warning: .Fx: Unknown FreeBSD version '13.1-STABLE' 
   1 mdoc warning: .Fx: Unknown FreeBSD version '13.1-RELEASE' 
   1 mdoc warning: .Fx: Unknown FreeBSD version '13.1-RC1' 
   1 mdoc warning: .Fx: Unknown FreeBSD version '13.1-BETA2' 
   1 mdoc warning: .Fx: Unknown FreeBSD version '13.1-ALPHA3' 
   1 mdoc warning: .Fx: Unknown FreeBSD version '13.0-PRERELEASE' 
   1 mdoc warning: .Fx: Unknown FreeBSD version '12.x' 
   1 mdoc warning: .Fx: Unknown FreeBSD version '10'

-- 
You are receiving this mail because:
You are the assignee for the bug.