https://bugzilla.kernel.org/show_bug.cgi?id=213019

            Bug ID: 213019
           Summary: regression: system can not boot with 4b9ee772ea("ACPI:
                    scan: Turn off unused power resources during
                    initialization")
           Product: ACPI
           Version: 2.5
    Kernel Version: 5.13-rc1
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: BIOS
          Assignee: acpi_b...@kernel-bugs.osdl.org
          Reporter: rui.zh...@intel.com
        Regression: No

Shujun Wang <wsj20...@163.com> has reported a regression caused by commit
4b9ee772ea("ACPI: scan: Turn off unused power resources during initialization")
on a Lenovo Thinkpad X1

> > It may cause some NVMe device probes to fail, and the system may get stuck
> > when using an NVMe device as the root filesystem.
> >
> > In the function nvme_pci_enable(struct nvme_dev *dev), as shown below,
> > readl(NVME_REG_CSTS) always returns -1 with the commit, which results in
> > the probe failed.
> >
> >   if (readl(dev->bar + NVME_REG_CSTS) == -1) {
> >       result = -ENODEV;
> >       goto disable;
> >   }
> >
> > dmesg:
> >   [    1.106280] nvme 0000:04:00.0: platform quirk: setting simple suspend
> >   [    1.109111] nvme nvme0: pci function 0000:04:00.0
> >   [    1.113066] nvme 0000:04:00.0: enabling device (0000 -> 0002)
> >   [    1.121040] nvme nvme0: Removing after probe failure status: -19

While I'm experiencing a similar problem and the sata disk fails caused by this
commit.

The root cause of my issue is that BIOS exposes a Power Resource which shows it
is OFF, but actually it is not. Because explicitly power off this power
resource by invoking its _OFF method causes the system failure, which is what
the offending commit does.

This means that the platform firmware implementation doesn't follow the ACPI
specification.

Currently, for me issue, I'm trying to push a BIOS fix.

For the issue reported by Shujun Wang <wsj20...@163.com>, it probably caused by
a similar BIOS issue.

So, Shujun Wang <wsj20...@163.com>, please attach
1. the full acpidump output so that I can verify if it is the same issue
2. the dmidecode output, which we can use to have a quirk for this particular
platform.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to