User-Agent: Cyrus-JMAP/3.5.0-alpha0-1371-g2296cc3491-fm-20211109.003-g2296cc34
Mime-Version: 1.0
Message-Id: <a13f0106-a2b2-430d-8143-86eb03e7a667@www.fastmail.com>
In-Reply-To: <YZREq6jQOhyKIHk0@rocinante>
References: <87h7ccw9qc.fsf@yujinakao.com>
 <8951152e-12d7-0ebe-6f61-7d3de7ef28cb@opensource.wdc.com>
 <YZQ+GhRR+CPbQ5dX@rocinante>
 <26826c5d-2fa6-9719-be2a-5a22d1e9abc0@opensource.wdc.com>
 <YZREq6jQOhyKIHk0@rocinante>
Date:   Wed, 17 Nov 2021 09:24:06 -0700
From:   "Jeremy Soller" <jeremy@system76.com>
To:     =?UTF-8?Q?Krzysztof_Wilczy=C5=84ski?= <kw@linux.com>,
        "Damien Le Moal" <damien.lemoal@opensource.wdc.com>
Cc:     "Yuji Nakao" <contact@yujinakao.com>, linux-kernel@vger.kernel.org,
        "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
        ". Bjorn Helgaas" <bhelgaas@google.com>,
        "Marc Zyngier" <maz@kernel.org>, "Arnd Bergmann" <arnd@arndb.de>,
        "Sasha Levin" <sashal@kernel.org>
Subject: Re: Kernel 5.15 doesn't detect SATA drive on boot
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

We are using 5.15.2 right now on Pop!_OS 21.10 but have not seen SATA is=
sues yet. I'll look into this,
and hope it makes it into a 5.15 release soon!

--=20
  Jeremy Soller
  System76
  Principal Engineer
  jeremy@system76.com

On Tue, Nov 16, 2021, at 4:54 PM, Krzysztof Wilczy=C5=84ski wrote:
> [+CC Adding Jeremy for visibility]
>
> Hi Damien,
>
> [...]
>> > The error in the dmesg output (see [2] where the log file is attach=
ed)
>> > looks similar to the problem reported a week or so ago, as per:
>> >=20
>> >   https://lore.kernel.org/linux-pci/ee3884db-da17-39e3-4010-bcc8f87=
8e2f6@xenosoft.de/
>>=20
>> Thanks. I searched this thread but could not find it in the archive.
>> Early morning, need more coffee :)
>
> No worries!  Got you covered!
>
>      )))
>     (((
>   +-----+
>   |     |]
>   `-----'
>
> Enjoy!
>
>>=20
>> >=20
>> > The problematic commits where reverted by Bjorn and the Pull Reques=
t that
>> > did it was accepted, as per:
>> >=20
>> >   https://lore.kernel.org/linux-pci/20211111195040.GA1345641@bhelga=
as/
>> >=20
>> > Thus, this would made its way into 5.16-rc1, I suppose.  We might h=
ave to
>> > back-port this to the stable and long-term kernels.
>>=20
>> Yes, I think the fix needs to go in 5.15, which is latest stable and =
LTS.
>
> On the plus side, not everyone is on 5.15 yet, but those who are using=
 it would
> have some issues.  Albeit, with it being an LTS release, the adoption =
might
> increase rapidly.
>
> For instance, I believe that Pop!_OS already ships kernels that are ve=
ry close
> to the upstream, which would hit their current user base.
>
> 	Krzysztof