linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: "Nikolas L." <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 18:18:22 +0900	[thread overview]
Message-ID: <b386bdc4-db27-3160-80ac-ecd9d8d69c9f@opensource.wdc.com> (raw)
In-Reply-To: <CAMJR_v6igrNZMzXpio27PpA6rQvo+efAVd2nM5GNg2+agQa9=A@mail.gmail.com>

On 2021/11/15 17:14, Nikolas L. wrote:
>> This error is not fatal. It simply means that the drive does not support the
>> INDENTIFY DEVICE log page. Nothing to worry about.
> I suppose it's not the reason to log error, maybe warn or notice.
>> Attempting to read this log should be avoided in this case though. I will send a
>> patch to fix that.
> Thank you! Got it.
>> However, the files you attached show that you are using
>> kernel 5.12
> According to almost any file in attachment, I'm using 5.15.2.
> Error happens only since 5.15, tested on 5.14.16.

I posted a patch:

https://lore.kernel.org/linux-ide/20211115060559.232835-3-damien.lemoal@opensource.wdc.com/

Can you try it please ?

>> You can ignore the read log error, unless your drive is not functional ?
> Yes I can and I will. Entire problem is just about redundant noise
> with error level in kernel log.
> 


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2021-11-15  9:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13 18:19 Nikolay
2021-11-15  0:03 ` Damien Le Moal
2021-11-15  8:14   ` Nikolas L.
2021-11-15  9:18     ` Damien Le Moal [this message]
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=b386bdc4-db27-3160-80ac-ecd9d8d69c9f@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 \
    --subject='Re: PROBLEM: [drivers/ata] Read log page failed (boot error message)' \
    /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

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).