From: Nikolay Kyx <knv418@gmail.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.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: Sat, 27 Nov 2021 13:34:02 +0300 [thread overview]
Message-ID: <CAMJR_v4_3npqoTkFYW+2OVDHjj4-9WK70xASK6C1Mqn=S5z2Wg@mail.gmail.com> (raw)
In-Reply-To: <8e55f354-0522-de56-2c1e-56557888602f@opensource.wdc.com>
On Tue, Nov 16, 2021 at 2:44 AM Damien Le Moal
<damien.lemoal@opensource.wdc.com> wrote:
> Latest kernel will not even print this warning since not having support for the
> IDENTIFY DEVICE log page with ATA-9 drives is expected. The patch fixing this
> will go to stable too.
While with 5.15.2 + patch there weren't errors from libata, with
vanilla 5.15.5 (in which patch 'libata: core: add missing
ata_identify_page_supported() calls'
was included) there are 2 other (new because it wasn't the case with
5.15.4) error messages:
sd 5:0:0:0: [sda] Asking for cache data failed
sd 5:0:0:0: [sda] Assuming drive cache: write through
With the old warning (twice):
ata6.00: ATA Identify Device Log not supported
To summarize errors:
pre-5.15 kernels: no errors from libata.
5.15 - 5.15.4 (twice): Read log page 0x08 failed, Emask 0x1
5.15.5: Asking for cache data failed; Assuming drive cache: write through
Same hardware, just upgraded kernel to 5.15.5.
I still think that my HDD doesn't deserve error messages in dmesg.
Errors from the storage subsystem can be scary for someone.
next prev parent reply other threads:[~2021-11-27 10:36 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
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 [this message]
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='CAMJR_v4_3npqoTkFYW+2OVDHjj4-9WK70xASK6C1Mqn=S5z2Wg@mail.gmail.com' \
--to=knv418@gmail.com \
--cc=damien.lemoal@opensource.wdc.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).