FULL AI ANALYSIS

NVMe SSD sustained write throughput collapses under Linux when PCIe ASPM is enabled

Generated Oct 3, 2026, 12:35:03 AM

Analysis summary

ASPM (Active State Power Management) reduces PCIe link power by transitioning into low-power link states (L0s/L1). Some NVMe controllers, host chipsets, or BIOS implementations have buggy ASPM/L1 or L1 Substates (L1SS) behavior that causes frequent link retraining or adds large wake-latency, which drastically reduces sustained throughput. The fact throughput returns when ASPM is disabled indicates a link power management interaction rather than a pure NVMe media issue. Fixes may require BIOS/firmware/kernel quirk updates from vendor.

Possible causes

NVMe controller or drive firmware implements ASPM/L1 incorrectly, causing frequent link retrain or excessive wake latencies.

80%

Motherboard/BIOS aggressiveness in enabling L1/L0s or L1SS features the drive does not fully support, producing instability.

65%

Kernel PCIe power management bug or missing platform quirk leading to incorrect negotiation of link power states.

55%

PCIe lane reconfiguration on the platform under power management that reduces effective bandwidth during low-power transitions.

25%

Suggested fixes

Diagnostic step 1

Reproduce and document the issue reliably: run fio with logging while toggling ASPM (BIOS vs pcie_aspm=off/force) and capture dmesg, lspci -vv, and nvme-cli get-log outputs showing timestamps of link state changes and throughput drop. These artifacts are required when filing vendor bugs.

Diagnostic step 2

If sustained throughput is required for your workload, keep ASPM disabled (BIOS or kernel parameter pcie_aspm=off) — this is reversible and the safest short-term mitigation. Note the power trade-off (higher idle power draw) and document which systems need this profile.

Diagnostic step 3

Test with alternate BIOS settings that selectively disable L1/L0s/L1SS rather than blanket ASPM off to find the minimal change that restores throughput; try disabling L1SS first if BIOS exposes it.

Diagnostic step 4

File bug reports with motherboard vendor and NVMe vendor including the collected logs (dmesg, lspci -vv, nvme-cli logs, fio job files) and reproduction steps. Do not perform firmware updates on production drives without a verified backup; if attempting firmware changes, take a complete backup first and schedule a maintenance window.

Diagnostic step 5

If comfortable, test newer or older kernel versions on a non-production system to determine whether a kernel regression/quirk mitigates the issue; include kernel bisect artifacts if you plan to open a kernel bug. Escalate to hardware vendor support for firmware/BIOS fixes if disabling ASPM is not acceptable long-term.

Contact • Help • API Docs • Careers • Terms • Privacy • Cookies • Ads