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

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

Bug#1060066: linux-image-6.1.0-17-amd64: kernel crash

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

Contents

  Bug#1060066: linux-image-6.1.0-17-amd64: kernel crash Justin Piszcz <jpiszcz@lucidpixels.com> - 2024-01-05 15:10 +0100
    Bug#1060066: Acknowledgement (linux-image-6.1.0-17-amd64: kernel crash) Justin Piszcz <jpiszcz@lucidpixels.com> - 2024-01-05 16:00 +0100

#81437 — Bug#1060066: linux-image-6.1.0-17-amd64: kernel crash

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

Package: linux-image-6.1.0-17-amd64

Distribution: Debian Stable
Kernel: 6.1.0-17-amd64

I 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/0ClFFOw

Regards,
Justin

[toc] | [next] | [standalone]

#81438 — Bug#1060066: Acknowledgement (linux-image-6.1.0-17-amd64: kernel crash)

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

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

Regards,
Justin

On Fri, Jan 5, 2024 at 9:03 AM Debian Bug Tracking System <
owner@bugs.debian.org> wrote:

> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1060066:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060066.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Kernel Team <debian-kernel@lists.debian.org>
>
> If you wish to submit further information on this problem, please
> send it to 1060066@bugs.debian.org.
>
> Please do not send mail to owner@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1060066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060066
> Debian Bug Tracking System
> Contact owner@bugs.debian.org with problems
>

[toc] | [prev] | [standalone]

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

csiph-web