[adding the nvme maintainers and the regressions mailing list to the list of recipients] [TLDR: I'm adding this report to the list of tracked Linux kernel regressions; the text you find below is based on a few templates paragraphs you might have encountered already in similar form. See link in footer if these mails annoy you.] On 11.01.23 23:11, Julian Groß wrote: > Dear Maintainer, > > when running Linux Kernel version 6.0.12, 6.0.10, 6.0-rc7, or 6.1.4, my > system seemingly randomly freezes due to the file system being set to > read-only due to an issue with my NVMe controller. > The issue does *not* appear on Linux Kernel version 5.19.11 or lower. > > Through network logging I am able to catch the issue: > ``` > Jan 8 14:50:16 x299-desktop kernel: [ 1461.259288] nvme nvme0: > controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10 > Jan 8 14:50:16 x299-desktop kernel: [ 1461.259293] nvme nvme0: Does > your device have a faulty power saving mode enabled? > Jan 8 14:50:16 x299-desktop kernel: [ 1461.259293] nvme nvme0: Try > "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug > Jan 8 14:50:16 x299-desktop kernel: [ 1461.331360] nvme 0000:01:00.0: > enabling device (0000 -> 0002) > Jan 8 14:50:16 x299-desktop kernel: [ 1461.331458] nvme nvme0: Removing > after probe failure status: -19 > Jan 8 14:50:16 x299-desktop kernel: [ 1461.371389] nvme0n1: detected > capacity change from 1953525168 to 0 > Jan 8 14:50:16 x299-desktop kernel: [ 1461.371389] BTRFS error (device > nvme0n1p4): bdev /dev/nvme0n1p4 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 > Jan 8 14:50:16 x299-desktop kernel: [ 1461.371389] BTRFS error (device > nvme0n1p4): bdev /dev/nvme0n1p4 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 > Jan 8 14:50:16 x299-desktop kernel: [ 1461.371392] BTRFS error (device > nvme0n1p4): bdev /dev/nvme0n1p4 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 > Jan 8 14:50:16 x299-desktop kernel: [ 1461.371394] BTRFS error (device > nvme0n1p4): bdev /dev/nvme0n1p4 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0 > Jan 8 14:50:16 x299-desktop kernel: [ 1461.371405] BTRFS error (device > nvme0n1p4): bdev /dev/nvme0n1p4 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0 > Jan 8 14:50:16 x299-desktop kernel: [ 1461.371406] BTRFS error (device > nvme0n1p4): bdev /dev/nvme0n1p4 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0 > Jan 8 14:50:16 x299-desktop kernel: [ 1461.371411] BTRFS error (device > nvme0n1p4): bdev /dev/nvme0n1p4 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0 > Jan 8 14:50:16 x299-desktop kernel: [ 1461.371419] BTRFS error (device > nvme0n1p4): bdev /dev/nvme0n1p4 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0 > Jan 8 14:50:16 x299-desktop kernel: [ 1461.371425] BTRFS error (device > nvme0n1p4): bdev /dev/nvme0n1p4 errs: wr 10, rd 0, flush 0, corrupt 0, > gen 0 > Jan 8 14:50:16 x299-desktop kernel: [ 1461.371426] BTRFS error (device > nvme0n1p4): bdev /dev/nvme0n1p4 errs: wr 11, rd 0, flush 0, corrupt 0, > gen 0 > ``` > > I have tried the suggestion in the log without luck. > > Attached is a log that includes two system freezes, as well as a list of > PCI(e) devices created by Debian reportbug. > The first freeze happens at "Jan 8 04:26:28" and the second freeze > happens at "Jan 8 14:50:16". > > Currently, I am using git bisect to narrow down the window of possible > commits, but since the issue appears seemingly random, it will take many > months to identify the offending commit this way. > > The original Debian bug report is here: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028309 Thanks for the report. To be sure the issue doesn't fall through the cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression tracking bot: #regzbot ^introduced v5.19..v6.0-rc7 #regzbot title nvme: system partially freezes with "nvme controller is down" #regzbot ignore-activity This isn't a regression? This issue or a fix for it are already discussed somewhere else? It was fixed already? You want to clarify when the regression started to happen? Or point out I got the title or something else totally wrong? Then just reply and tell me -- ideally while also telling regzbot about it, as explained by the page listed in the footer of this mail. Developers: When fixing the issue, remember to add 'Link:' tags pointing to the report (the parent of this mail). See page linked in footer for details. Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) -- Everything you wanna know about Linux kernel regression tracking: https://linux-regtracking.leemhuis.info/about/#tldr That page also explains what to do if mails like this annoy you.
