Messages in this thread | | | From | Nikolay Kyx <> | Date | Sat, 27 Nov 2021 13:34:02 +0300 | Subject | Re: PROBLEM: [drivers/ata] Read log page failed (boot error message) |
| |
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.
| |