On 2021/11/14 3:19, Nikolay wrote: > 1. While booting system, the following message appears in dmesg twice: > ata6.00: Read log page 0x08 failed, Emask 0x1 > 2. Error comes from libata-core.c:ata_read_log_page() > if called with page = ATA_LOG_SATA_SETTINGS (0x08), > i.e. from functions ata_dev_config_ncq_prio() or ata_dev_config_devslp() This error is not fatal. It simply means that the drive does not support the INDENTIFY DEVICE log page. Nothing to worry about. Attempting to read this log should be avoided in this case though. I will send a patch to fix that. However, the files you attached show that you are using kernel 5.12. That is not an LTS kernel (it is EOL), so this kernel will not get the fix. > (latter is new since v5.14 tag). > 3. drivers/ata > 4. /proc/version, output of scripts/ver_linux and kernel config are > attached > 5. Not appeared in v5.14 > 8. /proc/scsi/scsi is attached > Relevant fragment of dmesg output: > ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > ata2: SATA link down (SStatus 0 SControl 300) > ata6.00: ATA-9: WDC WD5000LPLX-75ZNTT0, 03.01A03, max UDMA/133 > ata6.00: Read log page 0x08 failed, Emask 0x1 > ata6.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 32), AA Your drive is still detected as supporting NCQ, so I think this is all OK. You can ignore the read log error, unless your drive is not functional ? > ata6.00: Read log page 0x08 failed, Emask 0x1 > ata6.00: configured for UDMA/133 > ata1.00: ATAPI: TSSTcorp CDDVDW TS-L633F, TM02, max UDMA/100 > ata1.00: configured for UDMA/100 > -- Damien Le Moal Western Digital Research
