From: Marc Zyngier <maz@kernel.org>
To: Maxym Synytsky <synytsky@dedrozeba.org.ua>
Cc: "Krzysztof Wilczyński" <kw@linux.com>,
"Yuji Nakao" <contact@yujinakao.com>,
"Damien Le Moal" <damien.lemoal@opensource.wdc.com>,
linux-kernel@vger.kernel.org,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
". Bjorn Helgaas" <bhelgaas@google.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Sasha Levin" <sashal@kernel.org>
Subject: Re: Kernel 5.15 doesn't detect SATA drive on boot
Date: Sun, 21 Nov 2021 19:58:31 +0000 [thread overview]
Message-ID: <87a6hxs2l4.wl-maz@kernel.org> (raw)
In-Reply-To: <20211121174118.231086eb@refinery>
On Sun, 21 Nov 2021 15:41:18 +0000,
Maxym Synytsky <synytsky@dedrozeba.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.
next prev parent reply other threads:[~2021-11-21 19:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 12:44 Kernel 5.15 doesn't detect SATA drive on boot Yuji Nakao
2021-11-16 23:05 ` Damien Le Moal
2021-11-16 23:26 ` Krzysztof Wilczyński
2021-11-16 23:40 ` Damien Le Moal
2021-11-16 23:54 ` Krzysztof Wilczyński
2021-11-17 16:24 ` Jeremy Soller
2021-11-17 9:07 ` Marc Zyngier
2021-11-17 9:36 ` Krzysztof Wilczyński
2021-11-21 15:41 ` Maxym Synytsky
2021-11-21 19:58 ` Marc Zyngier [this message]
2021-11-21 20:48 ` Maxym Synytsky
2021-11-21 21:09 ` Marc Zyngier
2021-11-17 13:52 ` Yuji Nakao
2021-11-17 14:20 ` Marc Zyngier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a6hxs2l4.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=contact@yujinakao.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=synytsky@dedrozeba.org.ua \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox