linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Nikolay <knv418@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: [drivers/ata] Read log page failed (boot error message)
Date: Mon, 15 Nov 2021 09:03:47 +0900	[thread overview]
Message-ID: <14b22c98-dc4c-fe3b-fa20-b3dd78afd5cc@opensource.wdc.com> (raw)
In-Reply-To: <YZABtvQab/M2CCQd@msi.localdomain>

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

  reply	other threads:[~2021-11-15  0:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13 18:19 PROBLEM: [drivers/ata] Read log page failed (boot error message) Nikolay
2021-11-15  0:03 ` Damien Le Moal [this message]
2021-11-15  8:14   ` Nikolas L.
2021-11-15  9:18     ` Damien Le Moal
2021-11-15 13:27       ` Nikolas L.
2021-11-15 23:44         ` Damien Le Moal
2021-11-27 10:34           ` Nikolay Kyx
2021-11-29  7:39             ` Damien Le Moal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14b22c98-dc4c-fe3b-fa20-b3dd78afd5cc@opensource.wdc.com \
    --to=damien.lemoal@opensource.wdc.com \
    --cc=knv418@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).