Your message dated Fri, 5 Jan 2024 21:00:54 +0100 with message-id <ZZhf9tOeMvIffpJ5@eldamar.lan> and subject line Re: Bug#1060066: Acknowledgement (linux-image-6.1.0-17-amd64: kernel crash) has caused the Debian Bug report #1060066, regarding linux-image-6.1.0-17-amd64: kernel crash to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1060066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060066 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: linux-image-6.1.0-17-amd64: kernel crash
- From: Justin Piszcz <jpiszcz@lucidpixels.com>
- Date: Fri, 5 Jan 2024 08:59:56 -0500
- Message-id: <[🔎] CAO9zADyay7UKC6in04LzoRZbbPmLqB7UTLpM--aq2Qg+VjMwiQ@mail.gmail.com>
Package: linux-image-6.1.0-17-amd64Distribution: Debian StableKernel: 6.1.0-17-amd64I have reverted back to 6.1.0-16-amd64. Currently, I am not using a remote syslog server so the crash dump is in a picture: https://imgur.com/a/0ClFFOwRegards,Justin
--- End Message ---
--- Begin Message ---
- To: Justin Piszcz <jpiszcz@lucidpixels.com>, 1060066-done@bugs.debian.org
- Subject: Re: Bug#1060066: Acknowledgement (linux-image-6.1.0-17-amd64: kernel crash)
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Fri, 5 Jan 2024 21:00:54 +0100
- Message-id: <ZZhf9tOeMvIffpJ5@eldamar.lan>
- In-reply-to: <[🔎] CAO9zADxeygSLVp0ugKec29-HMTkorZLffMU9vmS2dvqYThsd8w@mail.gmail.com>
- References: <[🔎] CAO9zADyay7UKC6in04LzoRZbbPmLqB7UTLpM--aq2Qg+VjMwiQ@mail.gmail.com> <handler.1060066.B.17044632131182380.ack@bugs.debian.org> <[🔎] CAO9zADyay7UKC6in04LzoRZbbPmLqB7UTLpM--aq2Qg+VjMwiQ@mail.gmail.com> <[🔎] CAO9zADxeygSLVp0ugKec29-HMTkorZLffMU9vmS2dvqYThsd8w@mail.gmail.com>
Hi, On Fri, Jan 05, 2024 at 09:49:59AM -0500, Justin Piszcz wrote: > Hello, > > Please close this case, false alarm, the debian/kernel is OK, appears to be > an HW issue that needs a workaround. > I've sent a note to linux-kernel@ > > Jan 5 06:18:52 atom kernel: [295306.524933] pcieport 0000:00:06.0: AER: > Corrected error received: 0000:00:06.0 > Jan 5 06:18:52 atom kernel: [295306.524979] pcieport 0000:00:06.0: PCIe > Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) > Jan 5 06:18:52 atom kernel: [295306.525004] pcieport 0000:00:06.0: > device [8086:a74d] error status/mask=00000001/00002000 > Jan 5 06:18:52 atom kernel: [295306.525027] pcieport 0000:00:06.0: [ 0] > RxErr (First) > Jan 5 06:19:22 atom kernel: [295336.554420] nvme nvme0: controller is > down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff > Jan 5 06:19:22 atom kernel: [295336.554469] nvme nvme0: Does your device > have a faulty power saving mode enabled? > Jan 5 06:19:22 atom kernel: [295336.554489] nvme nvme0: Try > "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug > Jan 5 06:19:22 atom kernel: [295336.614521] nvme 0000:03:00.0: Unable to > change power state from D3cold to D0, device inaccessible > Jan 5 06:19:22 atom kernel: [295336.614898] nvme nvme0: Removing after > probe failure status: -19 > Jan 5 06:19:22 atom kernel: [295336.630497] nvme0n1: detected capacity > change from 7814037168 to 0 > Jan 5 06:19:22 atom kernel: [295336.630502] BTRFS error (device > nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 > Jan 5 06:19:22 atom kernel: [295336.630513] BTRFS error (device > nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 > Jan 5 06:19:22 atom kernel: [295336.630542] BTRFS error (device > nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Thanks for confirming, closing the bug. Regards, Salvatore
--- End Message ---