From: Marc Zyngier <maz@kernel.org>
To: AceLan Kao <acelan.kao@canonical.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>
Subject: Re: There are not enough CPU0 APIC IRQs while doing IRQ migration during S3
Date: Tue, 19 Jul 2022 11:48:36 +0100 [thread overview]
Message-ID: <87fsixz8cb.wl-maz@kernel.org> (raw)
In-Reply-To: <CAFv23QmH4ooXJzX9A0CBObrETZgb9sT4dfh03NZA--fKfZnHDA@mail.gmail.com>
[- Jason]
On Tue, 19 Jul 2022 06:55:21 +0100,
AceLan Kao <acelan.kao@canonical.com> wrote:
>
> HI all,
>
> I encountered an issue while doing S3, it shows below message and then
> failed to enter S3
> [ 106.731140] CPU 31 has 116 vectors, 85 available. Cannot disable CPU
> [ 106.731551] ACPI: \_PR_.C01F: Found 2 idle states
> [ 106.732610] Error taking CPU31 down: -28
> [ 106.732612] Non-boot CPUs are not disabled
>
> CPU: AMD Ryzen Threadripper PRO 3955WX 16-Cores
> Kernel: v5.19-rc7
> There are 5 PCI to 4 type-c ports USB cards on the machine, and It
> wouldn't lead to the issue if only 4 cards are plugged. So, it looks
> like it can't handle 5 cards, and failed on the IRQ migration.
>
> The workaround provided by kaiheng is to release the irq while
> suspending and request irq while resuming.
> I'm wondering do we have a better solution for this kind of issue?
> Thanks.
>
> diff --git a/drivers/usb/host/xhci.c b/drivers/usb/host/xhci.c
> index edc6881c8a1b..91c79b21cb57 100644
> --- a/drivers/usb/host/xhci.c
> +++ b/drivers/usb/host/xhci.c
> @@ -17,6 +17,7 @@
> #include <linux/slab.h>
> #include <linux/dmi.h>
> #include <linux/dma-mapping.h>
> +#include <linux/suspend.h>
>
> #include "xhci.h"
> #include "xhci-trace.h"
> @@ -1079,6 +1080,9 @@ int xhci_suspend(struct xhci_hcd *xhci, bool do_wakeup)
> __func__);
> }
>
> + if (pm_suspend_via_firmware())
> + xhci_cleanup_msix(xhci);
I'm a bit clueless when it comes to the combination of x86 and xhci,
but doesn't this prevent resuming on a xhci interrupt?
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-07-19 10:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 5:55 There are not enough CPU0 APIC IRQs while doing IRQ migration during S3 AceLan Kao
2022-07-19 10:48 ` Marc Zyngier [this message]
2022-07-20 2:53 ` AceLan Kao
2022-07-20 3:16 ` Kai-Heng Feng
2022-07-20 10:11 ` Rafael J. Wysocki
2022-07-21 3:02 ` Kai-Heng Feng
2022-07-28 2:07 ` AceLan Kao
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=87fsixz8cb.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=acelan.kao@canonical.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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