Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #80463 > unrolled thread

Bug#1052063: regression: nvme drive not found after kernel upgrade from bookworm-security

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1052063: regression: nvme drive not found after kernel upgrade from bookworm-security Salvatore Bonaccorso <carnil@debian.org> - 2023-09-16 23:20 +0200
    Bug#1052063: regression: nvme drive not found after kernel upgrade from bookworm-security David da Silva Polverari <polverari@debian.org> - 2023-09-19 04:30 +0200
      Bug#1052063: regression: nvme drive not found after kernel upgrade from bookworm-security Salvatore Bonaccorso <carnil@debian.org> - 2023-09-27 15:00 +0200

#80463 — Bug#1052063: regression: nvme drive not found after kernel upgrade from bookworm-security

Control: tags -1 + moreinfo

Hi David,

On Sat, Sep 16, 2023 at 04:42:44PM -0300, David da Silva Polverari wrote:
> Package: src:linux
> Version: 6.1.52-1
> Severity: important
> 
> Dear Maintainer(s),
> 
> After upgrading the kernel from linux-image-6.1.0-11-amd64 (6.1.38-4) to
> linux-image-6.1.0-12-amd64 (6.1.52-1) from bookworm-security on my
> laptop (a Dell XPS 9560), the kernel fails to find the nvme disk, making
> it impossible for the initrd to decrypt the drive using LUKS, and as
> such there are no boot messages. On the previous kernel it boots fine.
> With tha 6.1.0-12 kernel, dmesg shows the following:
> 
> [   42.074878] nvme nvme0: Does your device have a faulty power saving mode enabled?
> [   42.074879] nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
> [   42.120786] nvme 0000:04:00.0: Unable to change power state from D3cold to D0, device inaccessible
> [   42.121007] nvme nvme0: Removing after probe failure status: -19
> [   42.136737] nvme0n1: detected capacity change from 1000215216 to 0
> 
> When I tried using the suggested parameters, I could boot, boot soon
> afterwards the system hung. I also tried some variations, as trying
> either only nvm_core.default_ps_max_latency_us=0 or pcie_aspm=off, but
> neither one worked.
> 
> I attached the dmesg output from the laptop into this email.

Can you verify if it's this issue known upstream?

https://lore.kernel.org/regressions/5DHV0S.D0F751ZF65JA1@gmail.com/

Does reverting the mentioned patch fix the issue?

Regards,
Salvatore

[toc] | [next] | [standalone]

#80474

On Sat, Sep 16, 2023 at 11:15:42PM +0200, Salvatore Bonaccorso wrote:
> 
> Can you verify if it's this issue known upstream?
> 
> https://lore.kernel.org/regressions/5DHV0S.D0F751ZF65JA1@gmail.com/
> 
Yes, it is the same issue. Sorry for taking too long to reply. I was
juggling with low partition space on my /boot to install a upstream
kernel on my laptop.

> Does reverting the mentioned patch fix the issue?
>
Yes, I checked v6.1.46 out from linux stable, built it, and tried to
boot. It presented the same problem as Debian's 6.1.0-12 (6.1.52-1).
After reverting commit 8ee39ec479147e29af704639f8e55fce246ed2d9 and
building it again, booting went fine.  Hope it helps.

Regards,
David

[toc] | [prev] | [next] | [standalone]

#80538

[Multipart message — attachments visible in raw view] — view raw

Hi David,

On Mon, Sep 18, 2023 at 11:19:07PM -0300, David da Silva Polverari wrote:
> On Sat, Sep 16, 2023 at 11:15:42PM +0200, Salvatore Bonaccorso wrote:
> > 
> > Can you verify if it's this issue known upstream?
> > 
> > https://lore.kernel.org/regressions/5DHV0S.D0F751ZF65JA1@gmail.com/
> > 
> Yes, it is the same issue. Sorry for taking too long to reply. I was
> juggling with low partition space on my /boot to install a upstream
> kernel on my laptop.
> 
> > Does reverting the mentioned patch fix the issue?
> >
> Yes, I checked v6.1.46 out from linux stable, built it, and tried to
> boot. It presented the same problem as Debian's 6.1.0-12 (6.1.52-1).
> After reverting commit 8ee39ec479147e29af704639f8e55fce246ed2d9 and
> building it again, booting went fine.  Hope it helps.

Can you confirm if the attached patch fixes the issue as well for you?

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web