[Bug 278059] Kernel panic in ipfw_chk starting in FreeBSD 14
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278059 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|i...@freebsd.org Keywords||crash, regression -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278063] Add znver4 to 14-STABLE examples
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278063 Bug ID: 278063 Summary: Add znver4 to 14-STABLE examples Product: Documentation Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Manual Pages Assignee: b...@freebsd.org Reporter: ni...@protonmail.com CC: d...@freebsd.org https://github.com/freebsd/freebsd-src/blob/stable/14/share/examples/etc/make.conf -- 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 Bug ID: 278065 Summary: ig4iic0: controller error during attach-1 Product: Base System Version: 14.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: marksh...@aol.com Created attachment 249589 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249589&action=edit dmesg output I am using an old Chromebook that I have flashed with a Coreboot image. Installed FreeBSD 14.0 RELEASE on it with drm-kmod and Gnome. The keyboard works fine. The trackpad does not respond at all. Found the following in dmesg output: 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 -- 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 --- Comment #1 from Mark Shank --- My workaround is to use a USB mouse which works well. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278071] undeclared function 'fbsd_ossl_provider_load' in krb5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278071 Bug ID: 278071 Summary: undeclared function 'fbsd_ossl_provider_load' in krb5 Product: Base System Version: 14.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: br...@freebsd.org Building FreeBSD with OpenSSL without providers fails -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278071] undeclared function 'fbsd_ossl_provider_load' in krb5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278071 Bernard Spil changed: What|Removed |Added Resolution|--- |Not Accepted Status|New |Closed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278072] undeclared function 'fbsd_ossl_provider_load' in krb5
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278072 Bug ID: 278072 Summary: undeclared function 'fbsd_ossl_provider_load' in krb5 Product: Base System Version: 14.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: b...@freebsd.org Reporter: br...@freebsd.org Created attachment 249596 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249596&action=edit git diff for kerberos5 Building FreeBSD with non-default libcrypto/libssl fails on fbsd_ossl_provider_load due to misplaced #ifdef. Both the header kerberos5/include/crypto-headers.h as well as crypto/heimdal/lib/krb5/context.c have ifdefs for OpenSSL 3 and later. fbsd_ossl_provider_load should return 0 when no providers are available. Due to misplaced ifdef in the crypto-headers.h the build fails. > /usr/src/crypto/heimdal/lib/krb5/context.c:395:11: error: call to undeclared > function 'fbsd_ossl_provider_load'; ISO C99 and later do not support implicit > function declarations [-Werror,-Wimplicit-function-declaration] >ret = fbsd_ossl_provider_load(); Not blotting out the fbsd_ossl_provider.h makes the build fail, can't see any issues in consumers of fbsd_ossl_provider_load. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278043] Diskless nfs root BOOTP/DHCP Broken
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278043
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC||b...@freebsd.org,
||gleb...@freebsd.org,
||ma...@freebsd.org,
||tue...@freebsd.org
--- Comment #2 from Mark Johnston ---
Indeed, bootpc_call() does this strange thing to ensure that the src addr of
DHCP requests has address 0.0.0.0:
638 /* Set netmask to 0.0.0.0 */
639 clear_sinaddr(sin);
640 error = ifioctl(bootp_so, SIOCAIFADDR,
(caddr_t)ifra,
641 td);
642 if (error != 0)
643 panic("%s: SIOCAIFADDR, error=%d",
__func__,
644 error);
645
646 error = sosend(bootp_so, (struct sockaddr *) &dst,
647&auio, NULL, NULL, 0, td);
648 if (error != 0)
649 printf("%s: sosend: %d state %08x\n",
__func__,
650 error, (int )bootp_so->so_state);
651
652 /* Set netmask to 255.0.0.0 */
653 sin->sin_addr.s_addr = htonl(0xff00);
654 error = ifioctl(bootp_so, SIOCAIFADDR,
(caddr_t)ifra,
655 td);
656 if (error != 0)
657 panic("%s: SIOCAIFADDR, error=%d",
__func__,
658 error);
The sosend() causes udp_send() to connect the socket, resulting in an error
because the local address is 0.0.0.0. We don't permit that since INADDR_ANY is
used as a sentinel value in the inpcb layer. dhclient doesn't have this
problem since it uses BPF to write packets.
Any opinions on how best to fix this?
--
You are receiving this mail because:
You are the assignee for the bug.
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 278084] qlnxe: multiple panics with WITNESS enabled [PATCH]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278084 Bug ID: 278084 Summary: qlnxe: multiple panics with WITNESS enabled [PATCH] Product: Base System Version: 13.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: keith.reyno...@hpe.com Created attachment 249613 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249613&action=edit patch file that fixes all the panics When enabling WITNESS and booting 13.3 on a system with a qlnxe NIC, multiple panics are reported due to various problems with locking. Fixing each one led to another panic until all of them were fixed. I'll attach the panic output for each panic and a patch file that fixes all of them. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278084] qlnxe: multiple panics with WITNESS enabled [PATCH]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278084 --- Comment #1 from Keith Reynolds --- Created attachment 249614 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249614&action=edit kernel config that enables WITNESS and INVARIANTS -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278084] qlnxe: multiple panics with WITNESS enabled [PATCH]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278084 --- Comment #2 from Keith Reynolds --- Created attachment 249615 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249615&action=edit first panic -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278084] qlnxe: multiple panics with WITNESS enabled [PATCH]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278084 --- Comment #3 from Keith Reynolds --- Created attachment 249616 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249616&action=edit second panic -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278084] qlnxe: multiple panics with WITNESS enabled [PATCH]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278084 --- Comment #4 from Keith Reynolds --- Created attachment 249617 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249617&action=edit third panic -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278084] qlnxe: multiple panics with WITNESS enabled [PATCH]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278084 --- Comment #5 from Keith Reynolds --- Created attachment 249618 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249618&action=edit fourth panic -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278084] qlnxe: multiple panics with WITNESS enabled [PATCH]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278084 --- Comment #6 from Keith Reynolds --- Created attachment 249619 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249619&action=edit fifth panic -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278084] qlnxe: multiple panics with WITNESS enabled [PATCH]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278084 --- Comment #7 from Keith Reynolds --- Created attachment 249620 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249620&action=edit sixth panic -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278084] qlnxe: multiple panics with WITNESS enabled [PATCH]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278084 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278085] qlnxe: setting mac address with ifconfig does not update NIC MAC filter [PATCH]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278085 Bug ID: 278085 Summary: qlnxe: setting mac address with ifconfig does not update NIC MAC filter [PATCH] Product: Base System Version: 13.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: keith.reyno...@hpe.com The qlnxe driver always sets the NIC's rx mac address to the card's default MAC, ignoring any MAC address set via ifconfig. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278085] qlnxe: setting mac address with ifconfig does not update NIC MAC filter [PATCH]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278085 --- Comment #1 from Keith Reynolds --- Created attachment 249621 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249621&action=edit patch that checks for and uses MAC address set by ifconfig -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278087] qlnxe: promiscuous and allmulti modes not handled properly [PATCH]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278087 Bug ID: 278087 Summary: qlnxe: promiscuous and allmulti modes not handled properly [PATCH] Product: Base System Version: 13.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: keith.reyno...@hpe.com The qlnxe_ioctl() function checks whether the IFF_PROMISC or IFF_ALLMULTI bits have changed since the last time the bits were saved, but it only saves the bits when the interface is marked down, so it misses some changes to those bits. Also, when it does detect a change in the bits, it always turns on those modes (promiscuous or allmulti), even if the change was to turn the interface bits off. And, when the interface is reset (such as when the MAC address is changed), it doesn't check those bits, so it always turns those modes off even if the interface bits are set. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278087] qlnxe: promiscuous and allmulti modes not handled properly [PATCH]
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278087 --- Comment #1 from Keith Reynolds --- Created attachment 249622 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=249622&action=edit patch that fixes the bugs -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278088] ipfw missing options for some useful IPv6 features for RFC 4890
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278088 Bug ID: 278088 Summary: ipfw missing options for some useful IPv6 features for RFC 4890 Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: free...@kumba.dev I was reading through RFC 4890 "Recommendations for Filtering ICMPv6 Messages in Firewalls", and it looks like some of the recommendations cannot be implemented using FreeBSD's ipfw(8). Specifically, there isn't an option for IPv6's "hop limit". I at first thought "ipttl" was a synonym for it, and the rule parser doesn't error out if using it with an IPv6-only rule (e.g., 'ip6' or 'ipv6-icmp'). But further digging reveals that it is only applicable for IPv4 (sys/netpfil/ipfw/ip_fw2.c in function ipfw_chk()): >case O_IPID: >case O_IPTTL: >if (!is_ipv4) >break; Support for this option would be necessary for things like this, from Pg 15: > Administrators may also wish to consider providing rules in firewall/ > routers to catch illegal packets sent with hop limit = 1 to avoid > ICMPv6 Time Exceeded messages being generated for these packets. > > Address Configuration and Router Selection messages (must be received > with hop limit = 255): > > o Router Solicitation (Type 133) > o Router Advertisement (Type 134) > o Neighbor Solicitation (Type 135) > o Neighbor Advertisement (Type 136) > o Redirect (Type 137) > o Inverse Neighbor Discovery Solicitation (Type 141) > o Inverse Neighbor Discovery Advertisement (Type 142) If implemented, I proposed that the option be called one of "hoplimit" or "ip6hoplimit" In another case, there is no support for specifying ICMPv6 Codes (similar to Bug #153161, which is for IPv4 ICMP). This would be relevant to limit certain ICMPv6 Type 3 codes, as referenced down in Appendix B using Linux's ip6tables format (Pg 34): > # Allow outgoing time exceeded code 0 messages > for inner_prefix in $INNER_PREFIXES > do > ip6tables -A icmpv6-filter -p icmpv6 -s $inner_prefix \ >--icmpv6-type ttl-zero-during-transit -j ACCEPT > done > > #@POLICY@ > # Allow outgoing time exceeded code 1 messages > for inner_prefix in $INNER_PREFIXES > do > ip6tables -A icmpv6-filter -p icmpv6 -s $inner_prefix \ >--icmpv6-type ttl-zero-during-reassembly -j ACCEPT > done If implemented, the best name for the option should be "icmp6code" and/or "icmp6codes", to align with icmp6type/icmp6types. I also noticed that there isn't support in "tcpflags" for the CWR and ECE flags, which are used for congestion control. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 278088] ipfw missing options for some useful IPv6 features for RFC 4890
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278088 Joshua Kinard changed: What|Removed |Added URL||https://datatracker.ietf.or ||g/doc/html/rfc4890 See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=1531 ||61 -- You are receiving this mail because: You are the assignee for the bug.
