amdsmu: Hints on what to do if IP block blocking S0i3
Reviewed by: olce
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D59674
amdsmu: Diagnose S0i3 entry after resume
Print out diagnostic information after resuming from suspend-to-idle if
we failed to enter S0i3, i.e. the IP blocks that were blocking entry to
S0i3.
Don't give detailed IP block info for other SMUs than for Phoenix, as I
have not had a chance to test these yet and the SMU seems to be very
quirky.
Reviewed by: olce
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D59673
power: Add power_resume_check eventhandler
This is intended to be used on resuming to check that everything that
happened during suspend was expected.
It is not meant to check for errors we should hard-fail from, rather it
should be used as an opportunity for drivers such as amdsmu(4) to check
e.g. whether the previous suspend-to-idle actually entered a deep sleep
state (S0i3).
Reviewed by: olce
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D59740
acpi: Don't check suspend-to-idle if suspend failed
If we e.g. failed to suspend a device and suspend bounced because of
that, then we're not expected to have entered a deep sleep state in the
first place. In this situation, don't overload the user with irrelevant
information.
Reviewed by: olce
Fixes: 5f68acc931a4 ("acpi: Warn if no amdsmu(4) loaded after suspend-to-idle resume")
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D59731
route/fib_algo: Fix nexthop index collision across families
fib_algo indexes its idx->nhop array by the nexthop index with
assumption of its uniqueness. Which is true except for IPv4 over
IPv6 nexthops.
Give each index space its own segment within the same array and
offset the index by the segment base. Segments are created on demand
and sized independently, so the rib's own family keeps base 0 and
tables without cross-family nexthops index exactly as before.
Reviewed by: melifaro
Discussed with: markj
MFC after: 2 weeks
Differential Revision: https://reviews.freebsd.org/D59552
bhyve: Add an option to prevent automatic restart in monitor mode
Monitor mode will currently unconditionally restart the guest if it
reboots, which can be incovenient in certain situations (e.g., resetting
the guest after a panic).
Address this by introducing a way to prevent automatic guest restarts
in monitor mode.
Reviewed by: markj
Differential Revision: https://reviews.freebsd.org/D59123
db/hash: Harden hash(3) database code
The hash(3) database code does not validate the on-disk database header,
leaving it open to several OOB read and write vulnerabilities.
This change adds basic header validation and array bounds checking to
parts of the hash(3) code that can be manipulated by messing with the
database header.
Reviewed by: kevans
Sponsored by: Klara, Inc.
MFC after: 1 month
Differential Revision: https://reviews.freebsd.org/D58822
man.cgi: remove stale manpage releases
Remove some outdated manual pages releases which are not really
supported by man.cgi: Slackware, SLES, Ubuntu interim releases.
devel/llvm22: fix arm64 and FLANG plists
In the arm64 case, add a missing file. In the FLANG case, delete an
empty directory.
PR: 298493, 298511
Reported by: yuri
net/xrdp: Generate default keys/certs at first startup instead of post-install
Generating keys/certs during post-install leads to duplicate keys when
provisioning multiple hosts from a single VM image.
The default snakeoil certificate has been switched to a 5-year Ed25519
certificate.
Reported by: cperciva (via email)
Obtained from: https://github.com/neutrinolabs/xrdp/pull/3874
Sponsored by: Cybertrust Japan
lang/babashka: Update to 1.13.223
Changes since 1.13.222:
1.13.223 (2026-09-15)
* #2151: An :exec-fn task in the :depends of a task with a :task
body runs, with its own :exec-args and spec defaults
* Dep resolution improvements
- #2152: Read POMs, settings.xml and repository metadata without
XML namespaces, as Maven does, so an element such as
<Xlint:-unchecked/> no longer fails resolution
- Resolve a timestamped snapshot version, such as
1.0-20240101.123456-3, to that build instead of the newest one
- Resolve ${project.name} and ${parent.artifactId} in a POM
- Report a missing artifact with the same message as the Clojure
CLI
- Resolve locally installed -SNAPSHOT artifacts and pick the
snapshot build with the newest metadata, including the local
[42 lines not shown]
