On Sat, May 10, 2025 at 01:14:52PM +0300, Mikko Juhani Korhonen wrote: > ke 7.5.2025 klo 11.56 Damien Le Moal (dlemoal@xxxxxxxxxx) kirjoitti: > > >>>>> On 5/1/25 05:36, Ioannis Barkas wrote: > > >>> I have two WD20EFAX-68FB5N0 and both behave consistently, unusable > > >>> from 6.9.0 on as they just keep resetting the SATA link , but they > > >>> have worked flawlessly with 6.8.x for a year and also now with the > > Can you share a dmesg output for the good case with 6.8.x kernel ? > > We would like to see differences with the non-working case. > > Hello Damien, > here is the dmesg from good 6.8.12. Thanks! Hello Mikko, In the (bad) dmesg that you shared earlier, we saw: touko 05 09:18:59 taavi kernel: ata1: SATA max UDMA/133 abar m131072@0xfc580000 port 0xfc580100 irq 42 lpm-pol 3 touko 05 09:18:59 taavi kernel: ata2: SATA max UDMA/133 abar m131072@0xfc580000 port 0xfc580180 irq 42 lpm-pol 3 touko 05 09:18:59 taavi kernel: ata3: SATA max UDMA/133 abar m131072@0xfc580000 port 0xfc580200 irq 42 lpm-pol 3 touko 05 09:18:59 taavi kernel: ata4: SATA max UDMA/133 abar m131072@0xfc580000 port 0xfc580280 irq 42 lpm-pol 3 touko 05 09:18:59 taavi kernel: ata5: SATA max UDMA/133 abar m131072@0xfc580000 port 0xfc580300 irq 42 lpm-pol 3 touko 05 09:18:59 taavi kernel: ata6: SATA max UDMA/133 abar m131072@0xfc580000 port 0xfc580380 irq 42 lpm-pol 3 In this new (good) dmesg we see: [ 1.839502] ata1: SATA max UDMA/133 abar m131072@0xfc580000 port 0xfc580100 irq 42 lpm-pol 0 [ 1.840186] ata2: SATA max UDMA/133 abar m131072@0xfc580000 port 0xfc580180 irq 42 lpm-pol 0 [ 1.840859] ata3: SATA max UDMA/133 abar m131072@0xfc580000 port 0xfc580200 irq 42 lpm-pol 0 [ 1.841516] ata4: SATA max UDMA/133 abar m131072@0xfc580000 port 0xfc580280 irq 42 lpm-pol 0 [ 1.842166] ata5: SATA max UDMA/133 abar m131072@0xfc580000 port 0xfc580300 irq 42 lpm-pol 0 [ 1.842804] ata6: SATA max UDMA/133 abar m131072@0xfc580000 port 0xfc580380 irq 42 lpm-pol 0 lpm-pol 0 means "keep firmware settings". That we see a difference suggests that the value of the Kconfig CONFIG_SATA_MOBILE_LPM_POLICY of these two kernel builds are not the same. Could you double check this? It is theoretically possible that both kernels were built with the same Kconfig value. If your BIOS marks a port as external / hotplug capable, then libata will force set lpm-pol to 0 (overriding the Kconfig value). However, if you haven't changed any BIOS settings between booting your two different kernels, then this second scenario sounds very unlikely. Kind regards, Niklas
