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: <87a6hxs2l4.wl-maz@kernel.org>
Date:   Sun, 21 Nov 2021 19:58:31 +0000
From:   Marc Zyngier <maz@...nel.org>
To:     Maxym Synytsky <synytsky@...rozeba.org.ua>
Cc:     Krzysztof Wilczyński <kw@...ux.com>,
        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 Sun, 21 Nov 2021 15:41:18 +0000,
Maxym Synytsky <synytsky@...rozeba.org.ua> wrote:
> 
> 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?

Are you sure? The dmesg you attached to this email shows otherwise:

[    0.766490] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    0.766634] ata1.00: ATA-10: KINGSTON SA400S37120G, 03150002, max UDMA/133
[    0.766641] ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 32)
[    0.769825] ata6: SATA link down (SStatus 0 SControl 300)
[    0.769845] ata2: SATA link down (SStatus 0 SControl 300)
[    0.769865] ata5: SATA link down (SStatus 0 SControl 300)
[    0.769876] ata3: SATA link down (SStatus 0 SControl 300)
[    0.769894] ata4: SATA link down (SStatus 0 SControl 300)
[    0.772046] ata1.00: configured for UDMA/133
[    0.772218] scsi 0:0:0:0: Direct-Access     ATA      KINGSTON SA400S3 0002 PQ: 0 ANSI: 5
[    0.772503] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/112 GiB)
[    0.772520] sd 0:0:0:0: [sda] Write Protect is off
[    0.772523] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    0.772538] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    0.773190]  sda: sda1 sda2
[    0.789894] sd 0:0:0:0: [sda] Attached SCSI disk

>From the above, I can only conclude that your SATA controller is up
and running.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.