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 New |276571 | makefs(8) creates broken UFS images with sectorsi Open| 46441 | sh(1): Does not support PS1, PS2, PS4 parameter e 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|259655 | periodic: security/security.functions does not re Open|259703 | In sys/dev/pci/pci.c, error in do_power_nodriver Open|259808 | etc/periodic/daily/100.clean-disks: Fix error (Di 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 278399] GENERIC kernel fails to compile
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278399 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org Resolution|--- |Unable to Reproduce Status|New |Closed --- Comment #1 from Ed Maste --- There is no attachment, and in any case PRs are not very effective at addressing build problems. Please follow up on the freebsd-stable mailing list with details of the error you encountered. https://lists.freebsd.org/subscription/freebsd-stable -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278489] dtrace; pid probe; unable to match constructor functions
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278489
--- Comment #2 from martin ---
Indeed evaltime works in that scenario.
The issue was originally shared on forums here:
https://forums.freebsd.org/threads/tracing-shared-library-functions-using-dtrace.93172/
I tried to simplified is as much as possible before opening PR. I didn't test
it with the evaltime for my simplified version.
Original issue is that these constructors are not matched on custom libraries.
Simple "mylib" demo lib:
#include
#include "mylib.h"
static int rc;
void __attribute__((constructor)) mysetup(void) {
printf("*** %s exec\n", __func__);
rc = 666;
}
void __attribute__((destructor)) leave(void) {
rc = 0;
}
int hello(char* s) {
printf("%s: %s\n", __func__, s);
return rc;
}
Still lists the functions as expected:
# dtrace -ln 'pid$target:mylib.so::entry' -c ./test
*** mysetup exec
hidden stuff
ID PROVIDERMODULE FUNCTION NAME
82966pid1096 mylib.so __do_global_dtors_aux entry
82967pid1096 mylib.so register_classes entry
82968pid1096 mylib.so __do_global_ctors_aux entry
82969pid1096 mylib.so mysetup entry
82970pid1096 mylib.so leave entry
82971pid1096 mylib.so hello entry
But doesn't match it:
# dtrace -n 'pid$target:mylib.so::entry' -c ./test
*** mysetup exec
hidden stuff
dtrace: description 'pid$target:mylib.so::entry' matched 6 probes
hello: my hello program
return value: 666
dtrace: pid 1098 has exited
CPU IDFUNCTION:NAME
7 82971 hello:entry
7 82970 leave:entry
7 82966 __do_global_dtors_aux:entry
Specifying evaltime fails to match any probes:
# dtrace -x evaltime=exec -n 'pid$target:mylib.so::entry' -c ./test
dtrace: invalid probe specifier pid$target:mylib.so::entry: probe description
pid1100:mylib.so::entry does not match any probes
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 260161] usb enumeration stalls on a framework laptop
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260161 Stephen Hurd changed: What|Removed |Added CC||sh...@freebsd.org --- Comment #7 from Stephen Hurd --- Work to support AX210 is in https://reviews.freebsd.org/D44861 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278319] filemon(4) panics with KASAN enabled
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278319 Christos Margiolis changed: What|Removed |Added Resolution|--- |FIXED Status|In Progress |Closed --- Comment #2 from Christos Margiolis --- Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278489] dtrace; pid probe; unable to match constructor functions
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278489 Mark Johnston changed: What|Removed |Added Status|New |Open CC||ma...@freebsd.org --- Comment #1 from Mark Johnston --- Adding `-x evaltime=exec` to the dtrace arguments fixes the problem for me, but I can't say offhand what the implications of that option are. I suspect it might break USDT, since drti.o uses a constructor to register probes with the kernel before main() is called. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278065] ig4iic0: controller error during attach-1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278065 Pierre-Alain TORET changed: What|Removed |Added CC||pierre-alain+freebsd@toret. ||fr --- Comment #2 from Pierre-Alain TORET --- I'm having the same issue on a Dell Chromebook 13 - 7310 (namecode LULU it seems). It also has been flashed with a Coreboot distribution (mrchromebox's). dmesg reports the following : driver bug: Unable to set devclass (class: ppc devname: (unknown)) driver bug: Unable to set devclass (class: ppc devname: (unknown)) ig4iic0: iomem 0x91122000-0x91122fff irq 7 on acpi0 ig4iic0: controller error during attach-1 device_attach: ig4iic0 attach returned 6 driver bug: Unable to set devclass (class: ppc devname: (unknown)) ig4iic0: iomem 0x91124000-0x91124fff irq 7 on acpi0 ig4iic0: controller error during attach-1 device_attach: ig4iic0 attach returned 6 Full dmesg at https://dmesgd.nycbug.org/index.cgi?do=view=7700 As Mark reported, in my case the keyboard also works fine. Only no touchpad. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278494] Hang during boot after recent ZFS update in CURRENT
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278494 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|f...@freebsd.org Keywords||regression -- You are receiving this mail because: You are the assignee for the bug.
