java/openjdk25: Update to version 25.0.4
Includes the following FreeBSD specific fixes:
- Set wxneeded flag for executables on FreeBSD.
- Fix build with clang 22
Sponsored by: The FreeBSD Foundation
ixgbe: isolate VF reset state
IXGBE_VF_INDEX() selects a 32-VF register bank. PFMBMEM() selects
one mailbox per VF, while ixgbe_toggle_txdctl() calculates queue
offsets from a VF number. Passing the bank index aliases VF1-31 to
VF0 and VF32-63 to VF1. Resetting one VF can therefore clear the peer
mailbox and leave its transmit queues disabled.
The VF raises its reset event before posting its mailbox request. The
PF checks reset events before mailbox messages. If both are pending,
clearing PFMBMEM during generic reset handling can erase the request
before ixgbe_read_mbx() consumes it. Clear the mailbox only from the
reset-message handler after the request has been read.
Use the VF number for queue toggling and document that API contract.
MFC after: 1 week
igc: Disable ASPM L1.2 on I226 to prevent RX stalls
I226 parts advertise support for the PCIe L1.2 link substate, but a
hardware erratum makes the exit latency from that low-power state
longer than the packet buffer can absorb under load. This stalls the
inbound packet stream. Disabling ASPM system-wide (BIOS or OS ASPM
policy) does not fix it. The L1.2 enable bit must be cleared directly
in the device's own PCIe L1 PM extended capability.
Add igc_is_device_id_i226() to identify affected parts and
igc_disable_broken_aspm_l1_2() to clear the ASPM L1.2 enable bit
on attach and after resume, since PCIe config space can be
reset across a suspend/resume cycle.
Adapted from the Linux igc driver:
0325143b59c6 igc: disable L1.2 PCI-E link substate to avoid
performance issue
1468c1f97cf3 igc: fix disabling L1.2 PCI-E link substate on I226
[8 lines not shown]
Mk/Uses/npm.mk: Quote TMPDIR and WRKDIR in shell comparisons
When TMPDIR is unset, the generated shell command becomes:
if [ != ${WRKDIR} ]; then
and /bin/sh reports:
[: !=: unexpected operator
Quoting both variables fixes the issue.
PR: 297181
Reported by: Shin-ichi Nagamura <core at zsc.jp>
e1000: restrict conventional PCI DMA to 32 bits
Some conventional PCI e1000 configurations hang when given DMA
addresses above 4 GB, particularly on systems using AMD
HyperTransport-to-PCI bridges. Linux has restricted e1000 to DMA32 in
PCI mode since 2011 for the same failure class in commit
e508be174ad36b0cf9b324cd04978c2b13c21502.
Set iflib's DMA width after determining the negotiated bus type. This
covers descriptor and packet-buffer mappings while preserving 64-bit
DMA for PCI-X and PCIe devices and providing a conditional tunable.
PR: 297064
Reported by: Alexander Leidinger <netchild at FreeBSD.org>
Tested by: Alexander Leidinger <netchild at FreeBSD.org>
MFC after: 1 week
japanese/ebview-gtk2: Fix crashes immediately after startup
Since japanese/ebview was removed in 2014, remove CONFLICTS.
Switch from REINPLACE_CMD to patchfile.
PR: 297153
Approved by: fluffy (mentor)
Co-authored-by: mce
security/globalprotect-openconnect: Mark DEPRECATED
2.0.0, which fixes the vulnerability, was released in February 2024.
The latest release is 2.6.4.
PR: 296823
Approved by: guru at unixarea.de (maintainer, timeout 2 weeks)
Approved by: fluffy (mentor)
cad/OrcaSlicer: Fix 32-bit build
LayerResult's second field is typed size_t, so std::numeric_limits::max
should also use size_t and not something related to coordinates for the
layer_id.
Reported by: pkg-fallout
Approved by: arrowd (co-mentor)
(cherry picked from commit b403418f4721af9ec4b2158539536e19ee564150)
net-mgmt/netbox: Fix build after 3496c09fda1b
* Switch to the recently created py-social-auth-core4 port, because
NetBox is not compatible with newer versions of py-social-auth-core
due to several breaking changes.
* Bump PORTREVISION due dependency change.
PR: 297152
www/py-dj60-social-auth-app-django: Fix build after 3496c09fda1b
* Although there are already newer releases that are compatible with
py-social-auth-core >= 5, they also introduce quite a few breaking
changes along with py-social-auth-core 4.9.0+, so updating the port
is not an option at this time.
Therefore, switch to the recently created py-social-auth-core4 port
for now to fix the fallout and avoid regressions.
* Bump PORTREVISION due dependency change.
PR: 297152
Reported by: Einar Bjarni Halldórsson, pkg-fallout
www/py-social-auth-app-django: Fix build after 3496c09fda1b
* Although there are already newer releases that are compatible with
py-social-auth-core >= 5, they also introduce quite a few breaking
changes along with py-social-auth-core 4.9.0+, so updating the port
is not an option at this time.
Therefore, switch to the recently created py-social-auth-core4 port
for now to fix the fallout and avoid regressions.
* Bump PORTREVISION due dependency change.
PR: 297152
Reported by: pkg-fallout
security/py-social-auth-core4: New port
This is the core component of the python-social-auth ecosystem, it
implements the common interface to define new authentication backends
to third parties services, implement integrations with web frameworks
and storage solutions.
PR: 297152
