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]

Date:   Wed, 17 Nov 2021 09:24:06 -0700
From:   "Jeremy Soller" <jeremy@...tem76.com>
To:     Krzysztof Wilczyński <kw@...ux.com>,
        "Damien Le Moal" <damien.lemoal@...nsource.wdc.com>
Cc:     "Yuji Nakao" <contact@...inakao.com>, linux-kernel@...r.kernel.org,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        ". Bjorn Helgaas" <bhelgaas@...gle.com>,
        "Marc Zyngier" <maz@...nel.org>, "Arnd Bergmann" <arnd@...db.de>,
        "Sasha Levin" <sashal@...nel.org>
Subject: Re: Kernel 5.15 doesn't detect SATA drive on boot

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@...tem76.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