[Bug 266900] WITHOUT_MACHDEP_OPTIMIZATION build option fails on error: undefined symbol: __stpcpy

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266900 Bug ID: 266900 Summary: WITHOUT_MACHDEP_OPTIMIZATION build option fails on error: undefined symbol: __stpcpy Product: Base System Version: CURRENT Hardware: Any

[Bug 266900] WITHOUT_MACHDEP_OPTIMIZATION build option fails on error: undefined symbol: __stpcpy

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266900 --- Comment #1 from Michael Dexter --- Created attachment 237152 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=237152&action=edit Build output with the resulting error -- You are receiving this mail because: You are the assign

[Bug 266901] Backup gpart script runs even it is disabled in periodic.conf inside jails

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266901 Bug ID: 266901 Summary: Backup gpart script runs even it is disabled in periodic.conf inside jails Product: Base System Version: 13.1-RELEASE Hardware: Any

[Bug 262969] NVMe - Resetting controller due to a timeout and possible hot unplug

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262969 bibi changed: What|Removed |Added CC||gnub...@gmail.com --- Comment #9 from bibi

[Bug 259785] pkgbase installation order is underspecified

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259785 Graham Perrin changed: What|Removed |Added Assignee|b...@freebsd.org|ma...@freebsd.org Severi

[Bug 266891] x11-wm/xfce4: desktop wallpaper and window buttons are no longer apparent; windowed applications can not be closed

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266891 Graham Perrin changed: What|Removed |Added Product|Base System |Ports & Packages UR

[Bug 266900] WITHOUT_MACHDEP_OPTIMIZATION build option fails on error: undefined symbol: __stpcpy

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266900 Xin LI changed: What|Removed |Added Assignee|b...@freebsd.org|arr...@freebsd.org CC|

[Bug 266627] stty -f should be non-blocking

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

[Bug 266145] [Intel Alder Lake] Crashes on CURRENT vfs

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145 --- Comment #7 from rkober...@gmail.com --- Small update on this. I ran the Alder Lake system on only the 2 P cores for at least three days with no panics. I tried switch to only 8 E cores and the system crashed again. I am back to P cores.

[Bug 266145] [Intel Alder Lake] Crashes on CURRENT vfs

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266145 --- Comment #8 from Amar Takhar --- (In reply to rkoberman from comment #7) Every crash I had was UFS/VFS as well. I still have all my coredumps. I'm able to disable my E-cores via the BIOS which is what I have done the system runs very