From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Bjorn Helgaas <helgaas@kernel.org>, Rob Herring <robh@kernel.org>
Cc: Donald Hunter <donald.hunter@gmail.com>,
Binbin Zhou <zhoubinbin@loongson.cn>,
Liu Peibao <liupeibao@loongson.cn>,
Huacai Chen <chenhuacai@loongson.cn>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev, mstowe@redhat.com
Subject: Re: [PATCH] PCI: Restrict device disabled status check to DT
Date: Thu, 20 Apr 2023 11:30:04 +0200 [thread overview]
Message-ID: <87leimnboj.fsf@redhat.com> (raw)
In-Reply-To: <20230419202042.GA223738@bhelgaas>
Bjorn Helgaas <helgaas@kernel.org> writes:
> [+cc Vitaly, Jesse, Tony, Andy, regressions, regarding reports of
> hang or crash during boot in igb driver, some with AWS Xen]
>
> On Wed, Apr 19, 2023 at 02:35:13PM -0500, Rob Herring wrote:
>> Commit 6fffbc7ae137 ("PCI: Honor firmware's device disabled status")
>> checked the firmware device status for both DT and ACPI devices. That
>> caused a regression in some ACPI systems. The exact reason isn't clear.
>> It's possibly a firmware bug. For now, at least, refactor the check to
>> be for DT based systems only.
>>
>> Note that the original implementation leaked a refcount which is now
>> correctly handled.
>>
>> Fixes: 6fffbc7ae137 ("PCI: Honor firmware's device disabled status")
>> Link: https://lore.kernel.org/all/m2fs9lgndw.fsf@gmail.com/
>> Reported-by: Donald Hunter <donald.hunter@gmail.com>
>> Cc: Binbin Zhou <zhoubinbin@loongson.cn>
>> Cc: Liu Peibao <liupeibao@loongson.cn>
>> Cc: Huacai Chen <chenhuacai@loongson.cn>
>> Signed-off-by: Rob Herring <robh@kernel.org>
>
> Applied to for-linus for (hopefully) v6.3. I added:
>
> [bhelgaas: Per ACPI r6.5, sec 6.3.7, for devices on an enumerable
> bus, _STA must return with bit[0] ("device is present") set]
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=217317
>
> It would be really great if anybody who has seen this issue could test
> and report whether this patch solves it.
>
[Cc: Myron]
I can confirm the patch fixes the issue I've reported with AWS Xen
instances, so:
Tested-by: Vitaly Kuznetsov <vkuznets@redhat.com>
--
Vitaly
next prev parent reply other threads:[~2023-04-20 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 19:35 [PATCH] PCI: Restrict device disabled status check to DT Rob Herring
2023-04-19 20:20 ` Bjorn Helgaas
2023-04-20 9:30 ` Vitaly Kuznetsov [this message]
2023-04-20 7:14 ` Donald Hunter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87leimnboj.fsf@redhat.com \
--to=vkuznets@redhat.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=chenhuacai@loongson.cn \
--cc=donald.hunter@gmail.com \
--cc=helgaas@kernel.org \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liupeibao@loongson.cn \
--cc=mstowe@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=robh@kernel.org \
--cc=zhoubinbin@loongson.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox