From: Maria Ioannidou <mi@eworx.gr>
To: ttencate@gmail.com
Cc: axboe@fb.com, hch@lst.de, kbusch@kernel.org,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
sagi@grimberg.me
Subject: Re: "controller is down; will reset" on SK Hynix NVMe drive in Lenovo IdeaPad Pro 5
Date: Fri, 21 Aug 2026 11:18:31 +0300 [thread overview]
Message-ID: <ab8989c8-0135-47c8-8f22-2fedb9f5cbe5@eworx.gr> (raw)
In-Reply-To: <CACbz5yFi8hiPD0Avg=KVTpdEeJC=3MMSkGtYOBQ=OmB_O0khyQ@mail.gmail.com>
I can confirm this issue on identical hardware, in case a second
report helps move the quirk forward.
Hardware:
Laptop: Lenovo IdeaPad Pro 5 16APH8 (MTM 83AR001MGM)
BIOS: MDCN33WW (2024-01-24)
Drive: SKHynix_HFS001TEJ4X112N
PCI ID: 1c5c:1d59
Kernel: 7.0.0-30-generic (Ubuntu 26.04)
Symptoms match the original report. After some idle time, writes
begin failing with I/O errors, ext4 remounts read-only, and the
system becomes unusable until reboot:
systemd-journald: Failed to write entry to
/var/log/journal/.../system.journal ... Input/output error
The failure is not confined to any userspace component. It
reproduces with no graphical session running (multi-user.target),
with the NVIDIA driver stack fully removed, and on a completely
fresh install of Ubuntu 26.04 onto a wiped disk - in that case
within roughly four minutes of first boot.
Diagnostics that made this misleading:
- SMART self-assessment PASSED, Critical Warning 0x00,
Available Spare 100%, Percentage Used 1%, Media and Data
Integrity Errors 0
- Sequential write throughput is normal (2.7 GB/s) when working
- fsck from external boot media always completes clean, since a
live USB barely touches the internal drive
Since a clean reinstall reproduces the fault, this initially
looked like failing hardware, and I was close to filing a warranty
claim before testing the APST hypothesis.
Booting with nvme_core.default_ps_max_latency_us=0 resolves it
completely. Stable for over 24 hours now, including several
reboots, suspend/resume cycles and repeated 4 GiB direct writes,
with no errors in dmesg.
I have not needed pcie_aspm=off or pcie_port_pm=off; disabling
APST alone has been sufficient here.
Happy to test a patch or provide further logs if useful.
--
Maria Ioannidou
Eworx Technical Team
mi@eworx.gr
prev parent reply other threads:[~2026-08-21 8:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 13:39 Thomas ten Cate
2025-11-18 20:49 ` Keith Busch
2025-11-20 13:52 ` Thomas ten Cate
2025-11-20 21:04 ` Keith Busch
2025-11-21 13:06 ` Thomas ten Cate
2025-11-24 19:52 ` Keith Busch
2025-12-15 12:15 ` Thomas ten Cate
2026-08-21 8:18 ` Maria Ioannidou [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ab8989c8-0135-47c8-8f22-2fedb9f5cbe5@eworx.gr \
--to=mi@eworx.gr \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=ttencate@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®