linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxym Synytsky <synytsky@dedrozeba.org.ua>
To: "Krzysztof Wilczyński" <kw@linux.com>
Cc: Marc Zyngier <maz@kernel.org>, 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 17:41:18 +0200	[thread overview]
Message-ID: <20211121174118.231086eb@refinery> (raw)
In-Reply-To: <YZTNCO4OBUrVkCuA@rocinante>

[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]

On Wed, 17 Nov 2021 10:36:08 +0100
Krzysztof Wilczyński <kw@linux.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.

[-- Attachment #2: dmesg_nForce_720D.txt.bz2 --]
[-- Type: application/x-bzip, Size: 18303 bytes --]

  reply	other threads:[~2021-11-21 15:48 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 [this message]
2021-11-21 19:58           ` Marc Zyngier
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=20211121174118.231086eb@refinery \
    --to=synytsky@dedrozeba.org.ua \
    --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=maz@kernel.org \
    --cc=sashal@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).