linux-kernel - Re: [REGRESSION][BISECTED] 5.15-rc1: Broken AHCI on NVIDIA ION (MCP79)

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]

Date:   Wed, 6 Oct 2021 12:48:05 +0100
From:   Rui Salvaterra <rsalvaterra@...il.com>
To:     tglx@...utronix.de
Cc:     maz@...nel.org, linux-pci@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [REGRESSION][BISECTED] 5.15-rc1: Broken AHCI on NVIDIA ION (MCP79)

On Wed, 6 Oct 2021 at 12:44, Rui Salvaterra <rsalvaterra@...il.com> wrote:
>
> Just for the record (and probably stating the obvious), reverting the
> aforementioned commit fixes this system. Running Linux 5.15-rc4, at
> the moment.

However, reverting the commit, while yielding a working system, causes
these errors in the dmesg…

rui@...der:~$ dmesg | grep ata1
[    0.670087] ata1: SATA max UDMA/133 abar m8192@...ae76000 port
0xfae76100 irq 30
[    1.009734] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.010578] ata1.00: ATA-8: Hitachi HDS721010CLA332, JP4OA3EA, max UDMA/133
[    1.010699] ata1.00: Read log page 0x08 failed, Emask 0x1
[    1.010707] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 32)
[    1.011777] ata1.00: Read log page 0x08 failed, Emask 0x1
[    1.011791] ata1.00: configured for UDMA/133
rui@...der:~$

I don't remember seeing those "Read log page 0x08 failed, Emask 0x1"
errors before.

Thanks,
Rui