linux-kernel - Re: Kernel 5.15 doesn't detect SATA drive on boot

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20211121174118.231086eb@refinery>
Date:   Sun, 21 Nov 2021 17:41:18 +0200
From:   Maxym Synytsky <synytsky@...rozeba.org.ua>
To:     Krzysztof Wilczyński <kw@...ux.com>
Cc:     Marc Zyngier <maz@...nel.org>, Yuji Nakao <contact@...inakao.com>,
        Damien Le Moal <damien.lemoal@...nsource.wdc.com>,
        linux-kernel@...r.kernel.org,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        ". Bjorn Helgaas" <bhelgaas@...gle.com>,
        Arnd Bergmann <arnd@...db.de>, Sasha Levin <sashal@...nel.org>
Subject: Re: Kernel 5.15 doesn't detect SATA drive on boot

On Wed, 17 Nov 2021 10:36:08 +0100
Krzysztof Wilczyński <kw@...ux.com> wrote:

> > > > I think that this problem is due to recent PCI subsystem changes which
> > > > broke Mac support. The problem show up as the interrupts not being
> > > > delivered, which in turn result in the kernel assuming that the drive
> > > > is not working (see the timeout error messages in your dmesg output).
> > > > Hence your boot drive detection fails and no rootfs to mount.
> > > > 
> > > > Adding linux-pci list.
> > > > 
> > > > 
> 
> > The issue is instead very close to the one reported at [1], for which
> > we have a very conservative workaround in 5.16-rc1 (commits
> > 2226667a145d and f21082fb20db). Looking at the dmesg log provided by
> > Yugi, you find the following nugget:
> > 
> > [    0.378564] pci 0000:00:0a.0: [10de:0d88] type 00 class 0x010601
> > 
> > Oh look, a NVIDIA AHCI controller, probably similar enough to the one
> > discussed in the issue reported by Rui.  
> 
> Good to know for the future reference that these can be problematic.
> 

Hi.
I am also experiencing this issue on Gigabyte GA-M720-US3 mobo which uses
NVIDIA nForce 720D chipset. As I understand from the quirks patch it does not
fix my controller?

$ bunzip2 -ck dmesg_nForce_720D.txt.bz2 | grep 0x010601
[    0.299980] pci 0000:00:09.0: [10de:0ad4] type 00 class 0x010601

In addition to the absense of devices during boot it takes minutes for this PC
on 5.15 to proceed from loading initramfs image to starting system from it.
I am attaching my dmesg just in case.

Max.

Download attachment "dmesg_nForce_720D.txt.bz2" of type "application/x-bzip" (18303 bytes)