[Bug 279542] mandoc emits error after exiting pager
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279542 Alexander Ziaee changed: What|Removed |Added CC||concussious.bugzilla@runbox ||.com --- Comment #1 from Alexander Ziaee --- I have proposed a fix for this. [0] https://github.com/freebsd/freebsd-src/pull/1283 Thanks @emaste! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279618] getnameinfo - IPv6 problem
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279618
Bug ID: 279618
Summary: getnameinfo - IPv6 problem
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Keywords: ipv6
Severity: Affects Some People
Priority: ---
Component: bin
Assignee: b...@freebsd.org
Reporter: b...@freebsd.org
6cb9418289f90 introduced a special check on the first nibble of an in6_addr:
+ switch (sin6->sin6_addr.s6_addr[0]) {
+ case 0x00:
If it doesn't fall into any of the two categories it will not attempt to do
name resolution and lookup the PTR because it sets NI_NUMERICHOST.
I cannot see why this "else" case was ever added (and someone should dig into
the KAME archives to understand). Also someone should check if POSIX says
anything beyond the RFC and fully understand what is supposed to go on.
Addresses with the IPv6 DNS64 default prefix 64:ff9b::/96 such as
64:ff9b::4007:8d09 (zoo) will not be resolved and that does indeed break
software (e.g. postfix in an ipv6-only setup behind a NAT64).
Manually calling
hp = getipnodebyaddr(_addr, sizeof(struct in6_addr), AF_INET6,
_error);
will result in the correct answer from an accordingly setup resolver.
--
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 New |276985 | crash in LinuxKPI/drm New |279203 | killpg(): Forking fast leads to livelock 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|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 37 problems total for which you should take action.
[Bug 277783] libc fma() doesn't not return the correct zero sign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277783 Ed Maste changed: What|Removed |Added Status|New |In Progress -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276724] 'man 8 glabel': add extra content
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276724 --- Comment #5 from Mark Linimon --- ^Triage: committed. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 276724] 'man 8 glabel': add extra content
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276724 --- Comment #4 from Chris Moerz --- If anyone sees this - we can close this, since we committed an update. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 219070] vm_radix_remove: invalid key found panic
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219070 Jeroen Ruigrok van der Werven changed: What|Removed |Added Resolution|--- |Unable to Reproduce Status|New |Closed --- Comment #6 from Jeroen Ruigrok van der Werven --- Closing this. The box runs 12-STABLE nowadays. About to move to 13-STABLE. Have not seen it happen again since reporting back in the day. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279603] ig4 break after suspend/resume cycle on MateBook X Pro 2023(controller error during attach-2)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279603 Bug ID: 279603 Summary: ig4 break after suspend/resume cycle on MateBook X Pro 2023(controller error during attach-2) Product: Base System Version: 14.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: huang...@gmail.com Created attachment 251308 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251308=edit verbose log I have a MateBook X Pro 2023 running 14.1-RELEASE, ig4 is not work after resume: # boot in single user kldload ig4 kldunload ig4 kldload ig4 works after go into wayland/sway kldload ig4 sysctl debug.acpi.suspend_bounce=1 acpiconf -s 3 kldunload ig4 kldload ig4 after resume, not work in wayland/sway: Jun 9 12:22:29 mbxp kernel: ig4iic0: controller error during attach-2 Jun 9 12:22:29 mbxp kernel: device_attach: ig4iic0 attach returned 6 -- You are receiving this mail because: You are the assignee for the bug.
