[UMD Bump] Automated UMD Bump 09.02.2026

[broskoTT]

Automated UMD bump to latest version

Changes

• Safe read write implementation for SIGBUS tt-umd#1721
• Bump version to 0.9.2 tt-umd#2096
• Update repository reference in GitHub Actions workflow tt-umd#2094
• Some log adjustments tt-umd#2088
• Add Blackhole Loudbox to CI tt-umd#2090
• Capture init. state in TTDevice tt-umd#2028
• Some TopologyDiscovery improvements tt-umd#2089
• Support BDF pattern in TT_VISIBLE_DEVICES tt-umd#2056
• Remove pci_target_devices from PCIDevice tt-umd#2058
• Add setting clock to busy and idle in PCIe DMA perf tests tt-umd#2087
• fix(modernize-deprecated-headers): fix clang-tidy violations tt-umd#2081
• Change external repository for GitHub Pages publish tt-umd#2085
• Enable cross translation unit (CTU) scanning for CodeChecker analysis tt-umd#2076
• fix(readability-redundant-member-init): fix clang-tidy violations tt-umd#2073
• Fix simulator tt-umd#2075
• Cache TLB for DMA transactions in SysmemBuffer tt-umd#2064
• Add NOC NODE ID test from NOC0 to NOC1 and vice-versa tt-umd#2025
• Run benchmarks on PR if benchmarks edited + p150b fix tt-umd#2071
• Expand tests for ARC messenger to cover all chips tt-umd#2059
• Run perf benchmarks on P150 cards tt-umd#2061
• Fix dead store in WormholeSPITTDevice::lock() tt-umd#2069
• Remove GRAYSKULL from ARCH enum tt-umd#1981
• Benchmark CI fixes tt-umd#1944
• (Reverted due to slowdown issues) More work to switch from tile_rd/wr to pci_rd/wr tt-umd#1946
• Fix insecure buffer handling in tt_kmd_lib.c tt-umd#2062
• Refactor NOC tests tt-umd#2024
• fix(clang-tidy): .clang-tidy config had problems tt-umd#2046
• fix(modernize-use-equals-default): fix clang-tidy violations tt-umd#2036
• Disable annoying check in .codechecker.json tt-umd#2055
• fix: Use filter_fixes.py instead of CodeChecker fixit to avoid YAML corruption tt-umd#2050
• fix(modernize-use-override): fix clang-tidy violations tt-umd#2038
• fix(modernize-make-unique): fix clang-tidy violations tt-umd#2034
• fix(modernize-concat-nested-namespaces): fix clang-tidy violations tt-umd#2033
• code-analysis.yaml workflow should analyze simulation code paths tt-umd#1975
• partially fix(misc-include-cleaner): fix clang-tidy violations tt-umd#2009
• Add cluster descriptor for 8xP150 Loudbox config tt-umd#2029

Testing

All the runs also have a corresponding closest run on main branch, for comparing failures.
All the runs have corresponding statuses. The runs will be retried 3 times automatically, after which failures will be reported.

Status	Workflow	Run	Main Run
Success	All post commit	Run	Main
No new failures	Blackhole Post commit	Run	Main
No new failures	Model regression	Run	Main
No new failures	Device performance regression	Run	Main
No new failures	Galaxy quick	Run	Main
No new failures	Galaxy unit tests	Run	Main
No new failures	T3000 unit tests	Run	Main

Overall Test Status: Success

[Copilot]

Pull request overview

Automated bump of the tt-umd submodule to a newer referenced commit.

Changes:

• Updated the tt_metal/third_party/umd git submodule pointer to a new commit SHA.

[broskoTT]

The Galaxy failure can be seen on main https://github.com/tenstorrent/tt-metal/actions/runs/21797746262/job/62888218757

[nbuncicTT]

Galaxy failures for WH are the following on the UMD bump:

• https://github.com/tenstorrent/tt-metal/actions/runs/21825215405/job/63019587583#step:6:419 [quick]
• https://github.com/tenstorrent/tt-metal/actions/runs/21825215405/job/63019587634#step:6:199 [health]

This can be seen on other branches:

• https://github.com/tenstorrent/tt-metal/actions/runs/21839760285/job/63022229817#step:6:209 [quick]
• https://github.com/tenstorrent/tt-metal/actions/runs/21818644195/job/62946762789#step:6:419 [health]

So it seems it does not have to do anything with UMD changes. The problems on main originate on WH galaxies.

[broskoTT]

The failure for galaxy unit tests was Routing FW on 6U unexpectedly enabled on device 87030954646843975 core (x=9,y=0). , which we know what is, and is not tied to any new changes, so ignoring that failure