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


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

Bug#1137248: linux-image-7.0.7+deb14-amd64: nvme nvme0: Disabling device after reset failure: -19 ,EXT4-fs: Journal has aborted, Kernel panic - not syncing: Attempted to kill init!

Started bySalvatore Bonaccorso <carnil@debian.org>
First post2026-06-03 16:30 +0200
Last post2026-06-03 16:30 +0200
Articles 2 — 2 participants

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#1137248: linux-image-7.0.7+deb14-amd64: nvme nvme0: Disabling device after reset failure: -19 ,EXT4-fs: Journal has aborted, Kernel panic - not syncing: Attempted to kill init! Salvatore Bonaccorso <carnil@debian.org> - 2026-06-03 16:30 +0200
    Processed: Re: Bug#1137248: linux-image-7.0.7+deb14-amd64: nvme  nvme0: Disabling device after reset failure: -19 ,EXT4-fs: Journal has  aborted, Kernel panic - not syncing: Attempted to kill init! "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-06-03 16:30 +0200

#92880 — Bug#1137248: linux-image-7.0.7+deb14-amd64: nvme nvme0: Disabling device after reset failure: -19 ,EXT4-fs: Journal has aborted, Kernel panic - not syncing: Attempted to kill init!

FromSalvatore Bonaccorso <carnil@debian.org>
Date2026-06-03 16:30 +0200
SubjectBug#1137248: linux-image-7.0.7+deb14-amd64: nvme nvme0: Disabling device after reset failure: -19 ,EXT4-fs: Journal has aborted, Kernel panic - not syncing: Attempted to kill init!
Message-ID<N1ULv-a28r-9@gated-at.bofh.it>
Control: tags -1 + upstream moreinfo

Hi,

On Fri, May 22, 2026 at 12:11:09AM +0600, Nahid Hasan wrote:
> Package: src:linux
> Version: 7.0.7-1
> Severity: important
> X-Debbugs-Cc: [debian-amd64@lists.debian.org](mailto:debian-amd64@lists.debian.org), [nhriyaad@gmail.com](mailto:nhriyaad@gmail.com)
> 
> Dear Maintainer,
> 
> After upgrading to kernel 7.0.7+deb14-amd64, the system becomes unstable and
> eventually panics due to NVMe controller reset failures and filesystem I/O
> errors.
> 
> System information:
> 
> * Machine: HP 250 G10 Notebook PC
> * BIOS: F.24 11/20/2025
> * Debian testing amd64
> * Previous kernel 7.0.4+deb14-amd64 works correctly on the same hardware
> 
> What led to the situation:
> After booting into kernel 7.0.7+deb14-amd64 and using the system normally, the
> NVMe controller resets and the root filesystem becomes read-only. Shortly after
> that, systemd crashes and the kernel panics.
> 
> What I did:
> 
> * Reinstalled linux-image-7.0.7+deb14-amd64
> * SMART self-tests were executed and completed without error
> * No NVMe media/data integrity errors are reported
> * Booting back into 7.0.4 restores stability
> 
> Observed result:
> The following messages appear before the panic:
> 
> nvme nvme0: Disabling device after reset failure: -19
> 
> I/O error, dev nvme0n1
> 
> EXT4-fs: Journal has aborted
> 
> Kernel panic - not syncing: Attempted to kill init!
> 
> The filesystem is remounted read-only and the system becomes unusable.
> 
> Expected result:
> The system should remain stable under kernel 7.0.7, as it does under 7.0.4.
> 
> Additional information:
> This may be related to NVMe APST/power-management handling. I am testing the
> following kernel parameter as a workaround:
> 
> nvme_core.default_ps_max_latency_us=0
> 
> The issue appears reproducible on 7.0.7 and not reproducible on 7.0.4.

Sorry for the delay in coming back to you. Can you please confirm if
the issue istill triggerable on 7.0.10-1 as in testing?

If youes, can you:

- Test 7.0.11 upstream? Does this expose the problem as well
- Provide fresh logs including the problem.

Given 7.0.4 was fine but 7.0.7 had the problem in case you can
reproduce the problem with recent kernel still, would you be able to
bisect the issue and we can get the breaking change?

Regards,
Salvatore

[toc] | [next] | [standalone]


#92881 — Processed: Re: Bug#1137248: linux-image-7.0.7+deb14-amd64: nvme nvme0: Disabling device after reset failure: -19 ,EXT4-fs: Journal has aborted, Kernel panic - not syncing: Attempted to kill init!

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2026-06-03 16:30 +0200
SubjectProcessed: Re: Bug#1137248: linux-image-7.0.7+deb14-amd64: nvme nvme0: Disabling device after reset failure: -19 ,EXT4-fs: Journal has aborted, Kernel panic - not syncing: Attempted to kill init!
Message-ID<N1ULv-a28r-15@gated-at.bofh.it>
In reply to#92880
Processing control commands:

> tags -1 + upstream moreinfo
Bug #1137248 [src:linux] linux-image-7.0.7+deb14-amd64: nvme nvme0: Disabling device after reset failure: -19 ,EXT4-fs: Journal has aborted, Kernel panic - not syncing: Attempted to kill init!
Added tag(s) upstream and moreinfo.

-- 
1137248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1137248
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


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


csiph-web