[orc-rt] Add SocketHandle, NativeSocketHandle APIs (#223114)
SocketHandle is an owning wrapper for a NativeSocketHandle value, and
closes the native socket on destruction.
NativeSocketHandle is a typedef for the platform's native socket handle
type.
Only POSIX is implemented in this patch (in sys/posix/SocketHandle.cpp).
Windows support will be added later.
This will be used for an upcoming SimpleRemote-based ControllerAccess
implementation that uses sockets for transport (SocketSimpleRemoteCA).
powerpc/booke: Add a machine check stack
Machine check and critical exceptions are independent of each other, and
can interrupt each other. Since they're asynchronous we cannot trust
that the existing stack pointer (%r1) is correct at time of entry, so
add a private machine check stack separate from the critical exception
stack. As part of this, switch to the STANDARD_CRIT_PROLOG() for
machine check exceptions, and overload the macro to specify the stack to
switch to. Also add a savearea argument to CRIT_SRR_RESTORE() so that
we can restore machine check exception state from the right location.
powerpmac_thermal: Improve thermal regulation on G5 quad models
Add a new "high temp" threshold below the max temp, in order to ramp the
fans (or pump for liquid cooled quads) sooner, and avoid the maximum
temperature. From the PR, this makes older G5 quads louder, but usable,
instead of hitting max temperature and forcing a thermal shutdown.
PR: 209202
Submitted by: gmbroome (PR)
devel/R-cran-shape: Remove duplicate port
Remove the port added in 1f4ad726a01d as it duplicates
graphics/R-cran-shape, which already provides the same package.
Update devel/R-cran-glmnet to depend on graphics/R-cran-shape instead.
Reported by: Antoine Brodin <antoine at freebsd.org>
e1000: Report corrected LAN management FIFO ECC errors
I350 and I354 report a corrected ECC error in the LAN transmit
management FIFO through LANPERRSTS bit 16. Unlike the parity status in
the same register, this condition neither interrupts nor stops traffic.
Poll the latch with the other corrected error status, increment a
dedicated counter, and clear only its RW1C bit. Expose it as
dev.igb.N.memory_errors.corrected_lan_mng_fifo.
Fatal error handling returns before the periodic statistics sweep and
may reset the device. Drain all I350 and I354 corrected-error status in
the admin task before recovery so the reset does not discard pending
indications.
This follows section 6.21.16 of the Intel Atom Processor C2000 Product
Family Integrated GbE Controller Programmer's Reference Manual,
document 537426 revision 1.5.
[3 lines not shown]
e1000: Handle I354 internal memory errors
The Atom C2000 integrated GbE programming reference documents the I354
internal memory error architecture. It shares the I350 PEIND and
ICR.FER routing, DMA and packet-buffer status, LAN parity status, and
required reset recovery.
Extend the existing I350 recovery and corrected error accounting paths
to I354. Keep the PCIe corrected error mask family-specific. C2000
PCIEECCSTS ends at the transmit write-data indication in bit 4 and does
not implement the I350 retry buffer indication in bit 5. Do not expose
the corresponding retry counter on I354.
The PRM overview says a PCIe region failure requires a system reboot,
while the individual PCIEERRSTS fields prescribe CTRL.RST followed by
port reinitialization. Use the register specific recovery, matching the
existing I350 path; failed reinitialization still leaves the port down.
This follows sections 5.6 and 6.21 of the Intel Atom Processor C2000
[6 lines not shown]
[CIR][AMDGPU] Let amdgcn_lerp and ds_swizzle use the generic codegen path (#222204)
__builtin_amdgcn_lerp and __builtin_amdgcn_ds_swizzle both map 1:1 onto
concrete (non-overloaded) intrinsics and carry the ClangBuiltin<> marker
in IntrinsicsAMDGPU.td, so EmitBuiltinExpr already lowers them
automatically by forwarding the arguments to the intrinsic.
tailscale: update to 1.102.4
- Resolved an issue that could cause a loss in connectivity when a
netmap update occurs near the time of reauthentication.
- Resolved an issue that could prevent exit nodes from appearing when
using a custom coordination server on Darwin.
Drive Wi-Fi through wpa_cli, save networks only once they connect
Wireless is now handled through wpa_supplicant's control socket
instead of by editing /etc/wpa_supplicant.conf and restarting the
daemon. Scanning, saving, forgetting, connecting and disconnecting all
go through wpa_cli, and the daemon started by rc is the only one that
ever runs. networkmgr never runs the wpa_supplicant binary, never
restarts a service on the Wi-Fi path, and never uses shell=True.
Connecting
- connect_to_ssid() joins the clicked network with select_network, so
with two saved networks in range the one clicked is the one joined.
wait_for_connection() requires wpa_state=COMPLETED and a matching
ssid; ifconfig's "associated" is not used, since it appears before
the key handshake finishes.
- Save on connect. A new network, or a retyped passphrase, lives in the
daemon only until wait_for_connection() succeeds, then save_config
writes the file. A passphrase that never works never reaches disk,
[108 lines not shown]
