On 25 August 2025 21:51:58 CEST, Paul Menzel <pmenzel@xxxxxxxxxxxxx> wrote: >Dear Linux folks, > > >On a Dell Precision 3620 with > > $ lspci -nn -s 00:17.0 > 00:17.0 SATA controller [0106]: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] [8086:a102] (rev 31) > >Linux warns about the ATA device and Samsung SSD 870 EVO 1TB. > > $ lsblk -o name,model,serial,rev -S > NAME MODEL SERIAL REV > sda Samsung SSD 870 EVO 1TB S6PUNL0T600648F 2B6Q > $ dmesg --level warn > [ 1.688558] Transient Scheduler Attacks: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. > [ 1.690195] Transient Scheduler Attacks: MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details. > [ 3.165214] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' > [ 3.254639] ata1.00: Model 'Samsung SSD 870 EVO 1TB', rev 'SVT02B6Q', applying quirks: noncqtrim zeroaftertrim noncqonati nolpmonati > [ 3.266623] ata1.00: supports DRM functions and may not be fully accessible > [ 3.304432] ata1.00: supports DRM functions and may not be fully accessible > [ 4.195869] wmi_bus wmi_bus-PNP0C14:01: [Firmware Bug]: WQBC data block query control method not found > [ 651.061135] systemd-journald[164]: File /var/log/journal/95790226b8d0779f4b4797314ca986d4/user-8578.journal corrupted or uncleanly shut down, renaming and replacing. > $ dmesg | grep -e 'Linux version' -e 'DMI: Dell' -e lpm > [ 0.000000] Linux version 6.12.40.mx64.484 (root@xxxxxxxxxxxxxxxxxxxxxxxxx) (gcc (GCC) 12.5.0, GNU ld (GNU Binutils) 2.41) #1 SMP PREEMPT_DYNAMIC Thu Jul 24 15:14:16 CEST 2025 > [ 0.000000] DMI: Dell Inc. Precision Tower 3620/0MWYPT, BIOS 2.23.0 09/14/2022 > [ 2.892973] ata1: SATA max UDMA/133 abar m2048@0xef14b000 port 0xef14b100 irq 124 lpm-pol 0 > [ 2.901327] ata2: SATA max UDMA/133 abar m2048@0xef14b000 port 0xef14b180 irq 124 lpm-pol 0 > [ 2.909685] ata3: SATA max UDMA/133 abar m2048@0xef14b000 port 0xef14b200 irq 124 lpm-pol 0 > [ 2.918042] ata4: SATA max UDMA/133 abar m2048@0xef14b000 port 0xef14b280 irq 124 lpm-pol 0 > [ 3.254639] ata1.00: Model 'Samsung SSD 870 EVO 1TB', rev 'SVT02B6Q', applying quirks: noncqtrim zeroaftertrim noncqonati nolpmonati > >I wonder why the DRM warning is logged twice, and why the LPM policy is 0. (It’s a desktop system, but still.) > >Is there anything I can do about this? Hello Paul, What is your Kconfig CONFIG_SATA_MOBILE_LPM_POLICY set to? If it is 0, try building with CONFIG_SATA_MOBILE_LPM_POLICY set to 3, which is nowadays the default, see: https://github.com/torvalds/linux/blob/v6.17-rc3/drivers/ata/Kconfig#L121 Didn't check about the double prints yet, a bit late here right now. Kind regards, Niklas
