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 obsolete releases. Status |Bug Id | Description +---+--- New |252123 | fetch(3): Fix wrong usage of proxy when request i New |262764 | After DVD1 13.0-R install with ports tree, portsn New |262989 | sys/conf/files, sys/conf/options, sys/conf/NOTES: New |269994 | build options have different kernel and userland Open| 46441 | sh(1): Does not support PS1, PS2, PS4 parameter e Open|165059 | vtnet(4): Networking breaks with a router using v Open|177821 | sysctl: Some security.jail nodes are funky, dupli Open|220246 | syslogd does not send RFC3164-conformant messages Open|232914 | kern/kern_resource: Integer overflow in function Open|250309 | devmatch: panic: general protection fault: sysctl Open|255130 | Issue with rtsx driver Open|256952 | kqueue(2): Improve epoll Linux compatibility (com Open|257149 | CFLAGS not passed to whole build Open|257646 | opensm: rc service is installed by default, but o Open|258665 | lib/libfetch: Add Happy Eyeballs (RFC8305) suppor Open|259292 | vmware/pvscsi: UNMAP fails on VMWare 6.7 thinly p Open|259636 | multiple components: Change "Take Affect" to "Tak Open|259640 | snd_hda(4): Fix sound output in Lenovo Ideapad 33 Open|259655 | periodic: security/security.functions does not re Open|259703 | In sys/dev/pci/pci.c, error in do_power_nodriver Open|260214 | acpi_battery: Should provide current/max battery Open|260245 | swap/vm: Apparent memory leak: 100% swap usage Open|261640 | sysctl: Add -F option to display sysctl format st Open|261641 | drm-kmod: Launch message is written into (possibl Open|261771 | nvme(4): Reports errors every 5 minutes: PRP OFFS Open|261971 | kernel crash launching bhyve guest on ZFS: #15 bu Open|262157 | su+j: Crashes during mmc(4) fsck after timeout: E Open|262192 | Crashes at boot with kern.random.initial_seeding. Open|264028 | loader: Incorrect (32gb) memory reported by BTX l Open|264075 | freebsd-update in 13.1-RELEASE detects an install Open|264188 | kinit(1): Ignores KRB5CCNAME environment variable Open|264226 | setting kern.vty=sc causes hang during UEFI boot Open|264757 | fetch: Show correct port number in -vv output Open|264833 | 12.3-STABLE panic on sync and reboot: panic: slee Open|266419 | mrsas: Corrupts memory (crashes) when reading dat 35 problems total for which you should take action.
[Bug 276500] System hang on loader then build with -fno-semantic-interposition -fno-plt
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276500 --- Comment #2 from Ivan Rozhuk --- (In reply to Mark Johnston from comment #1) World + kernel. CFLAGS+=-O3 -pipe -funroll-loops -fno-semantic-interposition -fno-plt COPTFLAGS+=-O3 -pipe -funroll-loops -fno-semantic-interposition -fno-plt -DSTRIP_FBSDID To improve speed. I expect that OS at least boot or I get some warning/error during build. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276505] On i386 clang asks to "compile with -msse -mfpmath=sse, or equivalent" when "-msse -mfpmath=sse" is already used (port audio/kaldi)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276505 Yuri Victorovich changed: What|Removed |Added Version|15.0-CURRENT|13.2-RELEASE Assignee|b...@freebsd.org|toolch...@freebsd.org URL||https://pkg-status.freebsd. ||org/beefy15/data/132i386-de ||fault/2c606b8e6de6/logs/kal ||di-g20231112_1.log -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276505] On i386 clang asks to "compile with -msse -mfpmath=sse, or equivalent" when "-msse -mfpmath=sse" is already used (port audio/kaldi)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276505 Bug ID: 276505 Summary: On i386 clang asks to "compile with -msse -mfpmath=sse, or equivalent" when "-msse -mfpmath=sse" is already used (port audio/kaldi) Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: y...@freebsd.org See the log URL. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276500] System hang on loader then build with -fno-semantic-interposition -fno-plt
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276500 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #1 from Mark Johnston --- What exactly did you rebuild? All of world? The kernel? How exactly did you set the flags? Why did you try this? What result do you expect? This bug report is extremely vague. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276500] System hang on loader then build with -fno-semantic-interposition -fno-plt
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276500 Ivan Rozhuk changed: What|Removed |Added Hardware|Any |amd64 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276500] System hang on loader then build with -fno-semantic-interposition -fno-plt
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276500 Bug ID: 276500 Summary: System hang on loader then build with -fno-semantic-interposition -fno-plt Product: Base System Version: 14.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: rozhuk...@gmail.com I try to rebuild FreeBSD 14/stable with -fno-semantic-interposition -fno-plt but it hang while trying to start. Probably Makefiles should handle -fno-semantic-interposition -fno-plt like it done with sse/avx flags. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 275912] nfsstat(1): options list is outdated
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275912 Mark Johnston changed: What|Removed |Added Resolution|--- |FIXED Assignee|b...@freebsd.org|asom...@freebsd.org CC||ma...@freebsd.org Status|New |Closed -- You are receiving this mail because: You are the assignee for the bug.
