[BUG][5.18rc5] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10

[Mikhail Gavrilov]

On Wed, Feb 22, 2023 at 8:37 PM Keith Busch <kbusch at kernel.org> wrote:
>
> Those are just the most readily available things we can tune at
> this level that has helped on *some* platform/device combinations.
> Certainly not going to solve every problem.
>
> You are showing that the driver can't read from the device's memory,
> and there's nothing the driver can do about that. This is usually
> some platform bios breakage well below the visibility of the nvme
> driver.
>
> Perhaps your platform's bridge windows are screwed up. One other
> thing you can try is adding param "pci=nocrs" to have the kernel
> ignore ACPI when setting these up.

Hi,
with parameter "pci=nocrs" not working WiFi (mt7921e) and after some
time nvme again downed.
So I must say with regret that this did not help. I attached here the
kerner log and lspci which are maided with "pci=nocrs".
No more ideas?

-- 
Best Regards,
Mike Gavrilov.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lspci.zip
Type: application/zip
Size: 3186 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20231217/f59f6e9a/attachment-0002.zip>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg-nvme-down-4.zip
Type: application/zip
Size: 40253 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-nvme/attachments/20231217/f59f6e9a/attachment-0003.zip>