[Bug 270904] Same Block Device over SATA and USB gpart(8) Broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270904 fgorter changed: What|Removed |Added CC||fgor...@gmail.com --- Comment #1 from fg

[Bug 270904] Same Block Device over SATA and USB gpart(8) Broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270904 --- Comment #2 from Slawomir Wojciech Wojtczak --- Funny ... I used the same Samsung mSATA SSD 850 EVO (250GB) in that test :) -- You are receiving this mail because: You are the assignee for the bug.

[Bug 270903] Black screen and kernel crash after reboot

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270903 fgorter changed: What|Removed |Added CC||fgor...@gmail.com --- Comment #1 from fg

[Bug 270759] [modules] kldload ktls_ocf on FreeBSD/arm64 13.2: link_elf: symbol sysctl___kern_ipc_tls_stats undefined

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270759 --- Comment #2 from ru...@verweg.com --- Thanks, I was under the impression that with exception of certain hardware related differences both amd64/arm64 kernels would have the same options. I’ll compile a custom kernel for now and wait to se

[Bug 270909] find: /.zfs: Invalid argument

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270909 Bug ID: 270909 Summary: find: /.zfs: Invalid argument Product: Base System Version: 13.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affec

[Bug 270909] find: /.zfs: Invalid argument

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270909 Marek Zarychta changed: What|Removed |Added CC||zarych...@plan-b.pwste.edu.

[Bug 270759] [modules] kldload ktls_ocf on FreeBSD/arm64 13.2: link_elf: symbol sysctl___kern_ipc_tls_stats undefined

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270759 --- Comment #3 from Ed Maste --- > I was under the impression that with exception of certain hardware related > differences both amd64/arm64 kernels would have the same options. In general they should. I'll take a look at this one. -- Yo

[Bug 270909] find: /.zfs: Invalid argument

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270909 --- Comment #2 from rx5...@gmail.com --- Sorry I didn't mention that I use mirrored zpool I just fresh installed 13.2-RELEASE on mirrored zpool and: root@fbsd3:~ # zpool status pool: zroot state: ONLINE config: NAMESTAT

[Bug 268005] rsync to FAT32 flash drive gets "Freeing unused sector" errors

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268005 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #2 from

[Bug 270909] find: /.zfs: Invalid argument

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270909 --- Comment #3 from Marek Zarychta --- (In reply to rx5670 from comment #2) Indeed, the error "Invalid argument" appears at the end of the find(1) output. You can redirect stderr if it hurts you. Is it really a bug? I doubt it. -- You a

[Bug 270909] find: /.zfs: Invalid argument

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270909 --- Comment #4 from rx5...@gmail.com --- (In reply to Marek Zarychta from comment #3) Actually these errors emailed from daily security checks from some scripts in /etc/periodic/security/ So I've never seen them before I updated from 12.3 t

[Bug 268005] rsync to FAT32 flash drive gets "Freeing unused sector" errors

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268005 --- Comment #3 from w...@psr.com --- OK, reporting a problem is certainly better than ignoring it, and that explains why it appeared in 13.1, but that leaves the question of why it's happening at all and fixing that. As a user, what I see i

[Bug 270917] Panic on recent -CURRENT: Unread portion of the kernel message buffer: no proper vop_fplookup_vexec

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270917 Bug ID: 270917 Summary: Panic on recent -CURRENT: Unread portion of the kernel message buffer: no proper vop_fplookup_vexec Product: Base System Version: CURRENT Hard

[Bug 131341] makefs (ffs): error "Bad file descriptor" on the mount point of md-presentation makefs image

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=131341 Ed Maste changed: What|Removed |Added Summary|makefs: error "Bad file |makefs (ffs): error "Bad

[Bug 196389] makefs(8): when populating METALOG with symlink information, no default user/group is populated

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196389 --- Comment #2 from Ed Maste --- (In reply to Graham Perrin from comment #1) > Is this still an issue? I have no reason to expect this has changed. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 221854] makefs: Reject UFS labels that are too long to fit

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221854 Ed Maste changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 203937] makefs: Coverity CID 975347, 975348: No provisions for i/o error

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203937 Ed Maste changed: What|Removed |Added Status|New |Open -- You are receiving this mail be

[Bug 203938] makefs: Coverity CID 975345, 975346: No provisions for i/o error

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203938 Ed Maste changed: What|Removed |Added Status|New |Open -- You are receiving this mail be

[Bug 203940] makefs: Coverity CID 976847: Delayed error with wrong output file type

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203940 Ed Maste changed: What|Removed |Added Status|New |Open -- You are receiving this mail be

[Bug 240619] makefs (ffs): "ffs_alloccg: map corrupted" error on small filesystem

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240619 Ed Maste changed: What|Removed |Added Summary|makefs: "ffs_alloccg: map |makefs (ffs): "ffs_alloccg:

[Bug 270884] Enable vCD OS Guest Customization Screen

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270884 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org --- Comment #1 from

[Bug 270917] Panic on recent -CURRENT: Unread portion of the kernel message buffer: no proper vop_fplookup_vexec

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270917 --- Comment #1 from commit-h...@freebsd.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=5e954b9216ed94f66c74ef55622e0a8fe18d805a commit 5e954b9216ed94f66c74ef55622e0a8fe18d805a Author:

[Bug 270867] xargs -E is not working properly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270867 Ed Maste changed: What|Removed |Added Status|New |In Progress CC|

[Bug 270917] Panic on recent -CURRENT: Unread portion of the kernel message buffer: no proper vop_fplookup_vexec

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270917 Mateusz Guzik changed: What|Removed |Added Resolution|--- |FIXED CC|

[Bug 270824] [local_unbound] exceeded the maximum number of sends

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270824 Dag-Erling Smørgrav changed: What|Removed |Added Assignee|b...@freebsd.org|d...@freebsd.org

[Bug 270903] Black screen and kernel crash after reboot

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270903 Daniel Toschläger changed: What|Removed |Added Resolution|--- |FIXED Status|New

[Bug 270920] drill: "Error creating socket" with link-local IPv6 nameserver in /etc/resolv.conf

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270920 Bug ID: 270920 Summary: drill: "Error creating socket" with link-local IPv6 nameserver in /etc/resolv.conf Product: Base System Version: 13.2-RELEASE Hardware: Any

[Bug 270922] buildworld should detect noexec on /usr/obj

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270922 Bug ID: 270922 Summary: buildworld should detect noexec on /usr/obj Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New Seve

[Bug 270904] Same Block Device over SATA and USB gpart(8) Broken

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270904 --- Comment #3 from fgorter --- (In reply to Slawomir Wojciech Wojtczak from comment #2) I am unable to reproduce the same problem on my end. My mSATA device is in a simple mSATA-to-USB enclosure. Works as expected here, both with the US

[Bug 270903] Black screen and kernel crash after reboot

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270903 --- Comment #3 from fgorter --- I tend to rely on x11/nvidia-xconfig to write a fully functional working /etc/X11/xorg.conf Might be helpful to you too. You can try building the nvidia-driver from ports with the ACPI_PM switched on/off pe

[Bug 261005] hostname -d is not resolved domain information correctly

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261005 Evan Marshall changed: What|Removed |Added CC||sampsonjohnniemeredith@gmai

[Bug 270928] Blacklistd does not handle SSHD failed logins

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270928 Bug ID: 270928 Summary: Blacklistd does not handle SSHD failed logins Product: Base System Version: 13.1-RELEASE Hardware: Any OS: Any Status: New S

[Bug 270909] find: /.zfs: Invalid argument

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270909 rx5...@gmail.com changed: What|Removed |Added Component|bin |kern -- You are receiving this

[Bug 270929] Intel LAN card I219LM (23) error load when boot

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=270929 Bug ID: 270929 Summary: Intel LAN card I219LM (23) error load when boot Product: Base System Version: 13.1-STABLE Hardware: amd64 OS: Any Status: New