From: "Jeremy Soller" <jeremy@system76.com>
To: "Krzysztof Wilczyński" <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
Date: Wed, 17 Nov 2021 09:24:06 -0700 [thread overview]
Message-ID: <a13f0106-a2b2-430d-8143-86eb03e7a667@www.fastmail.com> (raw)
In-Reply-To: <YZREq6jQOhyKIHk0@rocinante>
We are using 5.15.2 right now on Pop!_OS 21.10 but have not seen SATA issues yet. I'll look into this,
and hope it makes it into a 5.15 release soon!
--
Jeremy Soller
System76
Principal Engineer
jeremy@system76.com
On Tue, Nov 16, 2021, at 4:54 PM, Krzysztof Wilczyński wrote:
> [+CC Adding Jeremy for visibility]
>
> Hi Damien,
>
> [...]
>> > The error in the dmesg output (see [2] where the log file is attached)
>> > looks similar to the problem reported a week or so ago, as per:
>> >
>> > https://lore.kernel.org/linux-pci/ee3884db-da17-39e3-4010-bcc8f878e2f6@xenosoft.de/
>>
>> Thanks. I searched this thread but could not find it in the archive.
>> Early morning, need more coffee :)
>
> No worries! Got you covered!
>
> )))
> (((
> +-----+
> | |]
> `-----'
>
> Enjoy!
>
>>
>> >
>> > The problematic commits where reverted by Bjorn and the Pull Request that
>> > did it was accepted, as per:
>> >
>> > https://lore.kernel.org/linux-pci/20211111195040.GA1345641@bhelgaas/
>> >
>> > Thus, this would made its way into 5.16-rc1, I suppose. We might have to
>> > back-port this to the stable and long-term kernels.
>>
>> 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 very close
> to the upstream, which would hit their current user base.
>
> Krzysztof
next prev parent reply other threads:[~2021-11-17 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 12:44 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 [this message]
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
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=a13f0106-a2b2-430d-8143-86eb03e7a667@www.fastmail.com \
--to=jeremy@system76.com \
--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
all inboxes | Powered by JetHome®