This bug is awaiting verification that the linux-azure/6.17.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-questing-linux-azure' to 'verification-done- questing-linux-azure'. If the problem still exists, change the tag 'verification-needed-questing-linux-azure' to 'verification-failed- questing-linux-azure'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-questing-linux-azure-v2 verification-needed-questing-linux-azure -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2144060 Title: ADATA SU680 causes repeated SATA resets and I/O errors on Ubuntu unless link power management is forced to max_performance Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Noble: In Progress Status in linux source package in Questing: In Progress Status in linux source package in Resolute: In Progress Bug description: A Dell Vostro 15 3510 running Ubuntu from an ADATA SU680 1TB SATA SSD (/dev/sda, firmware VE1R910D) experienced repeated storage instability that appears tied to Linux SATA link power management. The detailed evidence is attached in the archive file: sata_adata_bugreport_attachments.zip The attached archive contains the main incident report and supporting evidence files, including SMART output, filtered kernel logs from affected and clean boots, hardware/system identification output, storage-layout output, and SATA power-policy evidence. Observed symptoms included: - repeated WRITE/READ FPDMA QUEUED failures - Emask 0x4 (timeout) and Emask 0x10 (ATA bus error) - irq_stat 0x08000000, interface fatal error - SError: { PHYRdyChg CommWake } - SError: { UnrecovData CommWake Handshk } - ata1: hard resetting link - Sense Key : Aborted Command - I/O error, dev sda, sector ... - abnormal SMART Power_Cycle_Count / Lifetime Power-On Resets growth during normal Ubuntu runtime - one Windows-side symptom where the SATA disk appeared as if GPT/partition metadata might need initialization - user-visible effects including OS slowdowns, temporary hangs/freezes, and application instability This did not look like classic SSD media failure: - SMART overall health stayed PASSED - reallocated sectors stayed 0 - reported uncorrectables stayed 0 - UDMA CRC stayed 0 - reserve space stayed 100 - endurance used stayed 0 - SMART error log stayed empty - a full raw-disk read succeeded - a later extended SMART self-test completed successfully Important power-management evidence: Before the workaround, the observed Linux SATA power-related state was: /sys/class/scsi_host/host0/link_power_management_policy:min_power_with_partial /sys/class/scsi_host/host1/link_power_management_policy:min_power_with_partial /sys/class/block/sda/device/power/control:on The strongest evidence is that the issue stopped immediately after forcing: for f in /sys/class/scsi_host/host*/link_power_management_policy; do echo max_performance | sudo tee "$f" done After that: - SMART power/reset counter stabilized - later long boots became clean - extended SMART self-test passed - system responsiveness improved - earlier freeze/hang behavior stopped being observed This strongly suggests a Linux SATA ALPM / DIPM / AHCI / libata incompatibility with this SSD/platform combination rather than classic SSD NAND/media failure. Expected result: Ubuntu should run normally from the ADATA SU680 without repeated SATA transport resets, SMART reset-counter inflation, transient I/O errors, GPT/metadata instability, or broader runtime instability. Actual result: Under the default Linux storage-power behavior on this system, repeated SATA transport resets and I/O errors occurred across multiple boots, and the SMART reset counter increased during runtime without real reboot/shutdown. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.17.0-14-generic 6.17.0-14.14~24.04.1 ProcVersionSignature: Ubuntu 6.17.0-14.14~24.04.1-generic 6.17.9 Uname: Linux 6.17.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: khaled 2391 F.... wireplumber /dev/snd/seq: khaled 2388 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 00:55:34 2026 InstallationDate: Installed on 2026-03-07 (5 days ago) InstallationMedia: Ubuntu 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 17ef:60ac Lenovo Lenovo 300 Wireless Compact Mouse Bus 001 Device 003: ID 0c45:6730 Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Vostro 15 3510 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=06fa0712-9df2-4153-9d2f-abd46d850c25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.17.0-14-generic N/A linux-backports-modules-6.17.0-14-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.25 SourcePackage: linux-hwe-6.17 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/05/2026 dmi.bios.release: 1.44 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.44.0 dmi.board.name: 00NFD7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.44.0:bd01/05/2026:br1.44:svnDellInc.:pnVostro153510:pvr:rvnDellInc.:rn00NFD7:rvrA00:cvnDellInc.:ct10:cvr:sku0ADB: dmi.product.family: Vostro dmi.product.name: Vostro 15 3510 dmi.product.sku: 0ADB dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144060/+subscriptions
Комментариев нет:
Отправить комментарий