FreeBSD-stable-14-amd64-test - Build #1120 - Still Unstable

From: <jenkins-admin_at_FreeBSD.org>
Date: Tue, 29 Apr 2025 20:52:54 UTC
FreeBSD-stable-14-amd64-test - Build #1120 (14cb4636358f1d54c2e0d843164c0dc9afcf012b) - Still Unstable

Build information: https://ci.FreeBSD.org/job/FreeBSD-stable-14-amd64-test/1120/
Full change log: https://ci.FreeBSD.org/job/FreeBSD-stable-14-amd64-test/1120/changes
Full build log: https://ci.FreeBSD.org/job/FreeBSD-stable-14-amd64-test/1120/console

Status explanation:
"Unstable" - some tests are suspected being broken by the following changes
"Still Unstable" - the failing test cases have not been fixed by these
                   following changes and this is a notification to note that
                   these changes have not been fully tested by the CI system

Change summaries:
(Those commits are likely but not certainly responsible)

7bc852d94dbf01d4feacd4f2a23b1ac22aea694c by jhb:
pci: propagate vpd read error

34f9dca1917b7837f7d1f5475b2e0d7be2ced717 by jhb:
pci: avoid accidental clobbering of regs on some fdt platforms

cbaa32c28a05bbc0e8ae5c37dcad4ffd6dc18f8f by jhb:
pci_host_generic: Use SYS_RES_MEMORY for the parent of I/O resource

14749f40c19341fc6935d619500331fa036a9a54 by jhb:
pci: Cosmetic cleanups to MSI/MSI-X routines

0a515a8d36ad41e21c4af00f9d97a32ae9fa61e0 by jhb:
pci: Don't cache the count of MSI/MSI-X messages before allocation

3a54ca5e28d847ab46168d3ea866259e806338fe by jhb:
new-bus: Add taskqueue_bus to process hot-plug device events

50c1d075dc8edf43af95e29b1664d8d7e8db5528 by jhb:
pcib: Use taskqueue_bus for hot-plug events instead of a private

ee08e8455170b65b85e85aa44374494b95fc5f0c by jhb:
mmc: Use bus_topo_lock and taskqueue_bus while adding/removing child

207e58ce8a6dfdce44f4d5e1607dc98551d15eaa by jhb:
sdhci: Use bus_topo_lock and taskqueue_bus for hotplug events

ab9e7d209ac58e9c4d0a0ebd4bdb6f96f303e8df by jhb:
hdaa: Don't hold a mutex while creating child devices

27fb895f9e81c57378f39d705e8a34caffaa9e93 by jhb:
mtx: Avoid nested panics on lock class mismatch assertions

7a7a7cd85090784070de36771e0ceae9427cc092 by jhb:
mtx: Make idle thread assertions more robust

d9ce37179a2f738feacf5eb9af0d394fc5882543 by jhb:
mtx: Include the mutex pointer in the panic message for destroyed locks

33bf58fbd8e53c0313f7e8ada014a53527011c4f by jhb:
lockmgr/rmlock/rwlock/sx: Make various assertions more robust

6fb471682aa9198fb187f2718dd291f09d96cf2b by jhb:
rwmlock/rwlock/sx: Print the pointer of destroyed locks in panic

b5bc47f1e1ab31086c1bf2e68944ea0331059c2c by jhb:
pci: Clear active PME# and disable PME# generation

b8b5dbdb93f871948651828c4cee7d733e649ff2 by jhb:
pci: Add helper routines to manage PME in device drivers

6f27822152e46c1890db0a17737517c1beba8ea3 by jhb:
dev: Use recently added improvements to PME# support to simplify drivers

a2de254b2007856d987556102806dc7b5bb9729e by jhb:
acpi_pci: Use pci_has_pm and pci_clear_pme

7485e6a867ab2f7db87536af4f44fcae34c0f6de by jhb:
telnet: Prevent buffer overflow in the user prompt for SRA

4373c15f1fa2afe9e7a24f3d1be9a3582874f48d by jhb:
pcib: Ignore power fault detected if a power controller is not present

14cb4636358f1d54c2e0d843164c0dc9afcf012b by jhb:
pcib: Clear any pending slot status events during attach



The failed test cases:

2 tests failed.
FAILED:  sys.netinet.fibs_test.same_ip_multiple_ifaces_fib0

Error Message:
atf-check failed; see the output of the test for details

FAILED:  sys.netlink.test_netlink_message_writer.py.__test_cases_list__

Error Message:
Test program did not exit cleanly