* src/sonic-utilities ee56d54...cb0e745 (11):
  > sonic_utilities: Support for DOM Threshold values for EEPROM dump
(#545)
  > [portstat] Fix portstat show RX_UTIL over 100% for 100G (#563)
  > sonic_installer: fix read-only filesystem support for firmware
update (#565)
  > Revert "show acl table command output should show binding column
correctly even with single port (#447)" (#589)
  > show acl table command output should show binding column correctly
even with single port (#447)
  > [config] Do no stop or restart dependent services (#582)
  > sfpshow: prevent 'show int trans eeprom --dom' from crashing (#567)
  > [warm-reboot] add docker upgrade --warm option and roll back support
(#559)
  > [ecnconfig] Validate input WRED parameters (#579)
  > [sonic-utilities] Add fstrim to reboot (#535)
  > Fixing the expected neighbor command due to change in output format
under sonic-buildimage/pull/3036 (#584)

…et#567)

When some specific 25G DAC attached to the system, the 'dom_info_dict'
could be a None object, as a result, the 'show int transceiver eeprom --dom'
will crash.

And thus, in this commit, we'll add an additional checker for the None object.

Signed-off-by: Dante (Kuo-Jung) Su <dante.su@broadcom.com>
Change-Id: Ic2b5eb38ddf98b98cce7eddf161595013a19c720

Submodule src/sonic-sairedis aa092506f..c61d15947:
  > [201811][SAI] move SAI sub module head to v1.4.3 (sonic-net#567)
  > [201811][sai] advance SAI submodule (sonic-net#566)

Signed-off-by: Ying Xie <ying.xie@microsoft.com>

Submodule src/sonic-sairedis aa092506f..c61d15947:
  > [201811][SAI] move SAI sub module head to v1.4.3 (#567)
  > [201811][sai] advance SAI submodule (#566)

Signed-off-by: Ying Xie <ying.xie@microsoft.com>

sonic-swss-common:
[ci] Set diff coverage threshold to 50% (#567)
Added NVGRE tunnel related tables (#549)
Add option to suppress logging (#566)
[TableBase] Make channel name from both table name and database ID (#568)
Revert "[TableBase] Make channel name from both table name and database ID (#568)" (#574)

sonic-py-swsssdk:
Add option to suppress warnings when querying Redis (#115)

[202412][Mellanox]Integrate HW-MGMT 7.0040.3005 Changes

…D automatically (#23016)

#### Why I did it
src/sonic-platform-daemons
```
* ea8715f - (HEAD -> master, origin/master, origin/HEAD) [xcvrd] silence port update event warnings (#567) (12 hours ago) [Brad House]
```
#### How I did it
#### How to verify it
#### Description for the changelog

* [xcvrd] silence port update event warnings

Warnings should only be used to alert an administrator that something
could cause issues.  Typically warnings will be evaluated by an
administrator as tagged by their SIEM, so it makes sense to reduce the
workload by not incorrectly tagging these log messages.

Reduced the log level to NOTICE which will still appear at the default
log levels in case anyone is parsing these events in their SIEM.

Signed-off-by: Brad House (@bradh352)

Provide support for SmartSwitch DPU module graceful shutdown.

Description:
Single source of truth for transitions

All components now use sonic_platform_base.module_base.ModuleBase helpers:

set_module_state_transition(db, name, transition_type)
clear_module_state_transition(db, name)
get_module_state_transition(db, name) -> dict
is_module_state_transition_timed_out(db, name, timeout_secs) -> bool
Eliminates duplicated logic and race-prone direct Redis writes.

Correct table everywhere

Standardized on CHASSIS_MODULE_TABLE (replaces CHASSIS_MODULE_INFO_TABLE).
HLD mismatch addressed in code (HLD fix tracked separately).
Ownership & lifecycle

The initiator of an operation (startup/shutdown/reboot) sets:

state_transition_in_progress=True
transition_type=<op>
transition_start_time=<utc-iso8601>
The platform (set_admin_state()) is responsible for clearing:

state_transition_in_progress=False
optionally transition_end_time=<epoch> (or similar end stamp).
CLI pre-clears only when a prior transition is timed out.

Timeouts & policy

Platform JSON path only: /usr/share/sonic/device/{plat}/platform.json; else constants.

Typical production values used:

startup: 180s, shutdown: 180s (≈ graceful_wait 60s + power 120s), reboot: 120s.
Graceful wait (e.g., waiting for “Graceful shutdown complete”) is a platform policy and implemented inside platform set_admin_state()—not in ModuleBase.

Boot behavior

chassisd on start:

Clears stale flags once (centralized sweep).
Runs set_initial_dpu_admin_state() which marks transitions via ModuleBase before calling platform set_admin_state().
Leaves clearing to the platform or to well-defined status transitions (ONLINE/OFFLINE) where appropriate.
gNOI shutdown daemon

Listens on CHASSIS_MODULE_TABLE and triggers only when:

state_transition_in_progress=True and transition_type=shutdown.
Never clears the flag (ownership stays with the platform).

Bounded RPC timeouts and robust Redis access (swsssdk/swsscommon).

CLI (config chassis modules …)

Uses ModuleBase APIs for all set/get/timeout checks.
If a previous transition is stuck, is_module_state_transition_timed_out() → auto-clear then proceed.
Sets transition at the start of startup/shutdown; platform clears on completion.
Fabric card flow retained; edits are surgical.
Redis robustness

Helpers handle both stacks (swsssdk/swsscommon); no hset(mapping=...) usage.
Consistent HGETALL/HSET paths; resilient to connector differences.
Race reduction & consistency

Centralized writes prevent multi-writer races.
All transition writes include transition_start_time; clears may add an end stamp.
Existing PCI/file-lock logic left intact; unrelated behavior unchanged.
Change scope

Minimal, targeted diffs.
No background tasks added, no broad refactors beyond transition handling.
Behavior changes are limited to making transition semantics correct and uniform across repos.
HLD: # 1991 sonic-net/SONiC#1991
sonic-platform-common: sonic-net#567 sonic-net/sonic-platform-common#567
sonic-utilities: sonic-net/sonic-utilities#4031
sonic-platform-daemons: sonic-net/sonic-platform-daemons#667

How to verify it
Issue the "config chassis modules shutdown DPUx" command
Verify the DPU module is gracefully shut by checking the logs in /var/log/syslog on both NPU and DPU