[Bug 275048] System prints "reboot: v_swappgsin" twice when rebooting

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275048 --- Comment #7 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=e6278ae2bd7c59d8057e1dfe8a801b1b46b392d4 commit e6278ae2bd7c59d8057e1dfe8a801b1b46b392d4

[Bug 275048] System prints "reboot: v_swappgsin" twice when rebooting

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275048 --- Comment #6 from commit-h...@freebsd.org --- A commit in branch stable/14 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=071364c85081981b22bbf8651fb5307a543e9de9 commit 071364c85081981b22bbf8651fb5307a543e9de9

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

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

[Bug 275169] Panic: rw_rlock: wlock already held for tcpinp @ /usr/src/sys/netinet/in_pcb.c:2529

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275169 --- Comment #9 from Dani I. --- (In reply to Michael Tuexen from comment #5) Thanks for triaging! As kp@ isn't responsible for ipfw - do you know who could maybe help there? Thanks! (In reply to Gleb Smirnoff from comment #8) For us it's

[Bug 275030] buildworld fails if obj dir is NFS-mounted [patch]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275030 --- Comment #17 from Warner Losh --- (In reply to Martin Birgmeier from comment #16) So we could use tar, with the following super ugly (and likely not very portable) formulation: diff --git a/Makefile.inc1 b/Makefile.inc1 index

[Bug 275044] Missing tab in `netstat -s` output

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275044 --- Comment #5 from commit-h...@freebsd.org --- A commit in branch stable/13 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=0a97a28c6c9f00997733bebd241403097f533404 commit 0a97a28c6c9f00997733bebd241403097f533404

[Bug 275044] Missing tab in `netstat -s` output

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275044 --- Comment #4 from commit-h...@freebsd.org --- A commit in branch stable/14 references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=4595a9e9af827db03b293a9aed72618bc285f54f commit 4595a9e9af827db03b293a9aed72618bc285f54f

[Bug 275115] ig4(4): Intel Ice Lake I2C not recognized

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275115 Vladimir Kondratyev changed: What|Removed |Added Assignee|b...@freebsd.org|w...@freebsd.org

[Bug 275030] buildworld fails if obj dir is NFS-mounted [patch]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275030 --- Comment #16 from Martin Birgmeier --- On the zfs-on-root system I looked for one (of the few) files without uarch not set and used cp to copy it to root's home dir. The copy has uarch set. -- Martin -- You are receiving this mail

[Bug 275030] buildworld fails if obj dir is NFS-mounted [patch]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275030 --- Comment #15 from Martin Birgmeier --- Btw tar does not complain if it cannot set flags, although it does set them if possible (but not on NFS, obviously). -- You are receiving this mail because: You are the assignee for the bug.

[Bug 275030] buildworld fails if obj dir is NFS-mounted [patch]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275030 --- Comment #14 from Martin Birgmeier --- (In reply to Warner Losh from comment #13) On two machines with /usr/bin/basename on UFS, the uarch bit is not set. On one machine with a ZFS root, uarch is set on /usr/bin/basename. Also, to

[Bug 275030] buildworld fails if obj dir is NFS-mounted [patch]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275030 --- Comment #13 from Warner Losh --- (In reply to Martin Birgmeier from comment #12) We still still don't know why the flags are set on /bin/basename... Until I understand where they are coming from, or what environment we see them, I'm

[Bug 275030] buildworld fails if obj dir is NFS-mounted [patch]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275030 --- Comment #12 from Martin Birgmeier --- (In reply to Warner Losh from comment #11) How about doing the copy only if the existing target differs from the source? Something like "cmp -s a b || cp a b". Would that be sufficient to satisfy

[Bug 275030] buildworld fails if obj dir is NFS-mounted [patch]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275030 --- Comment #11 from Warner Losh --- The -p change was to fix meta mode. Now that I've had a chance to sleep on it I remember: it was for metamode. filemon catches EVERYTHING that's used to build a target, including the binaries that are

[Bug 275193] Playing videos with a Linux browser crashes the system

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275193 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|emulat...@freebsd.org

[Bug 275199] ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275199 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@freebsd.org -- You are

[Bug 275200] NFS mounts cannot access ZFS snapshots in //.zfs

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275200 Rick Macklem changed: What|Removed |Added Assignee|b...@freebsd.org|rmack...@freebsd.org

[Bug 275200] NFS mounts cannot access ZFS snapshots in //.zfs

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275200 Bug ID: 275200 Summary: NFS mounts cannot access ZFS snapshots in //.zfs Product: Base System Version: 14.0-RELEASE Hardware: Any OS: Any

[Bug 270409] NVMe: ABORTED - BY REQUEST for TOSHIBA THNSN51T02DUK

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270409 Thierry Thomas changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 275199] ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275199 Thierry Thomas changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 275199] ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275199 Bug ID: 275199 Summary: ZFS: unsupported feature: com.klarasystems:vdev_zaps_v2 Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any

[Bug 270409] NVMe: ABORTED - BY REQUEST for TOSHIBA THNSN51T02DUK

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270409 Thierry Thomas changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 265776] [nvme] Toshiba nvme not always detected on boot

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265776 Thierry Thomas changed: What|Removed |Added CC||thie...@freebsd.org

[Bug 275193] Playing videos with a Linux browser crashes the system

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275193 Bug ID: 275193 Summary: Playing videos with a Linux browser crashes the system Product: Base System Version: 14.0-RELEASE Hardware: amd64 OS: Any Status: New

[Bug 242835] concurrency issue when building kernel with 'make -j8': make[5]: make[5]: don't know how to make opt_global.h. Stop

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242835 --- Comment #3 from Martin Birgmeier --- I also tried adding a sleep of a few seconds after the config which generates opt_global.h, to no avail. It should be noted that all the machines are running ntp, with a few milliseconds of time

[Bug 275030] buildworld fails if obj dir is NFS-mounted [patch]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275030 --- Comment #10 from Martin Birgmeier --- (In reply to Jessica Clarke from comment #4) Could this be related to bug 249957? - There seem to be races in what make is doing when timestamps are either truncated to seconds (over NFS) or

[Bug 275169] Panic: rw_rlock: wlock already held for tcpinp @ /usr/src/sys/netinet/in_pcb.c:2529

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275169 --- Comment #8 from Gleb Smirnoff --- I'd really appreciate if you check out FreeBSD 14.0-RELEASE. The inpcb synchronization has underwent total rewrite in there. I'd be really interested to see if the bug has gone. The ipfw/uid checks