lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMJR_v6igrNZMzXpio27PpA6rQvo+efAVd2nM5GNg2+agQa9=A@mail.gmail.com>
Date:   Mon, 15 Nov 2021 11:14:50 +0300
From:   "Nikolas L." <knv418@...il.com>
To:     Damien Le Moal <damien.lemoal@...nsource.wdc.com>
Cc:     linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: [drivers/ata] Read log page failed (boot error message)

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ