[BUG] libata: WD Green 480GB (firmware 42059100) disconnects unless booted with libata.force=nolpm
Ronald Garcia Vazquez <[email protected]> Tue, 21 Jul 2026 11:33:07 -0400
| Newsgroups | org.kernel.vger.linux-ide,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <CAGiKK17Fg4SgS+y0GzD3new44QzD_yPZU5V3ZeHdUr9mFnfn1Q@mail.gmail.com> |
[BUG] libata: WD Green 480GB (firmware 42059100) disconnects unless booted with libata.force=nolpm Hardware ======== Laptop: Dell Latitude 3420 CPU Platform: Intel Tiger Lake SATA Controller: 00:17.0 SATA controller [0106]: Intel Corporation Tiger Lake-LP SATA Controller [8086:a0d3] (rev 20) SSD: WD Green 2.5 480GB Firmware: 42059100 Kernel Versions Tested ====================== - 7.0.0-28-generic (Ubuntu) - 7.0.0-14-generic (Ubuntu) Problem Description =================== The SATA SSD disconnects after approximately 2-3 minutes of normal system operation under default LPM settings. Kernel log excerpt: [ 120.456789] ata1.00: qc timeout after 5000 msecs [ 120.456795] ata1.00: failed to disable DIPM [ 120.456800] ata1.00: failed to disable DEVSLP [ 120.456805] ata1: SATA link down [ 120.456810] ata1.00: detaching After these messages, /dev/sda disappears completely from the system until reboot. Reproduction Steps ================== 1. Boot Linux normally without extra kernel parameters. 2. Idle or perform light I/O operations for 2-3 minutes. 3. The SSD drops off the bus. Workaround & Stability ====================== Modified GRUB configuration (/etc/default/grub): From: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" To: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash libata.force=nolpm" Observed behavior with workaround: - Sustained stability (>15 hours uptime tested). - Multiple file operations and heavy I/O completed without issue. - No SATA bus resets or disconnects recorded. - No device removal. SMART Information ================= Model: WD Green 2.5 480GB Firmware: 42059100 SMART enabled and reporting HEALTHY status (no pending sectors or reallocated counts). Questions ========= 1. Is this a known incompatibility between libata Link Power Management and this SSD firmware? 2. Should a quirk entry be added to libata for this specific drive model/firmware pair? 3. Would additional debugging information be useful? Atte.: Ronald Garcia Vazquez Teléfono +56 9 2601 1681 *"Mas Dios muestra su amor para con nosotros en que aun siendo pecadores Cristo murió por nosotros Romanos 5:8"*
dmesg_failure.txt
(text/plain, 100 KB) - not displayed