Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #81438
| Path | csiph.com!1.us.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder8.news.weretis.net!fu-berlin.de!bofh.it!news.nic.it!robomod |
|---|---|
| From | Justin Piszcz <jpiszcz@lucidpixels.com> |
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#1060066: Acknowledgement (linux-image-6.1.0-17-amd64: kernel crash) |
| Date | Fri, 05 Jan 2024 16:00:01 +0100 |
| Message-ID | <HSTPX-ZY2-3@gated-at.bofh.it> (permalink) |
| References | <HST3z-Zzq-1@gated-at.bofh.it> <HSTPX-ZY2-5@gated-at.bofh.it> <HST3z-Zzq-1@gated-at.bofh.it> <HSTPX-ZY2-5@gated-at.bofh.it> |
| X-Mailbox-Line | From debian-bugs-dist-request@lists.debian.org Fri Jan 5 14:54:10 2024 |
| Old-Return-Path | <debbugs@buxtehude.debian.org> |
| X-Spam-Flag | NO |
| X-Spam-Score | 0.441 |
| Reply-To | Justin Piszcz <jpiszcz@lucidpixels.com>, 1060066@bugs.debian.org |
| Resent-To | debian-bugs-dist@lists.debian.org |
| Resent-Cc | Debian Kernel Team <debian-kernel@lists.debian.org> |
| X-Debian-Pr-Message | followup 1060066 |
| X-Debian-Pr-Package | linux-image-6.1.0-17-amd64 |
| X-Debian-Pr-Source | linux-signed-amd64 |
| X-Gm-Message-State | AOJu0YyeZ+88pwXlUwcjapQ2YsLAUmu+ScHq3BbmP4tsq1rEUfVyn36z TsfdDt7mek6ol4ORVYSY+0UeB+Ji0Mi96w4KCLbqIhTRIVFHvO2BQvT7OpL8Nms= |
| X-Google-SMTP-Source | AGHT+IF7ql66vS94M6KymeXNq2aSmIzsYAXSeWFYecz5H6QPIlfUsm9nnaRfI2L0FAUUkkzrSlYwNmRsb0EdWL0DiLs= |
| X-Received | by 2002:a17:90a:b790:b0:28c:ca9d:e58c with SMTP id m16-20020a17090ab79000b0028cca9de58cmr1683099pjr.4.1704466212540; Fri, 05 Jan 2024 06:50:12 -0800 (PST) |
| MIME-Version | 1.0 |
| Content-Type | multipart/alternative; boundary="0000000000002169f8060e33f722" |
| X-Debian-Message | from BTS |
| X-Mailing-List | <debian-bugs-dist@lists.debian.org> archive/latest/1814519 |
| List-ID | <debian-bugs-dist.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-bugs-dist/> |
| Approved | robomod@news.nic.it |
| Lines | 141 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Date | Fri, 5 Jan 2024 09:49:59 -0500 |
| X-Original-Message-ID | <CAO9zADxeygSLVp0ugKec29-HMTkorZLffMU9vmS2dvqYThsd8w@mail.gmail.com> |
| X-Original-References | <CAO9zADyay7UKC6in04LzoRZbbPmLqB7UTLpM--aq2Qg+VjMwiQ@mail.gmail.com> <handler.1060066.B.17044632131182380.ack@bugs.debian.org> <CAO9zADyay7UKC6in04LzoRZbbPmLqB7UTLpM--aq2Qg+VjMwiQ@mail.gmail.com> <handler.1060066.B.17044632131182380.ack@bugs.debian.org> |
| Xref | csiph.com linux.debian.bugs.dist:1181207 linux.debian.kernel:81438 |
Cross-posted to 2 groups.
Show key headers only | View raw
[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 >
Back to linux.debian.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
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
csiph-web