From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Rahul Kumar <rahul.kumar1@amd.com>,
Lukas Wunner <lukas@wunner.de>,
Kai-Heng Feng <kai.heng.feng@canonical.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [Bug 215590] New: PCI link is down after suspend after we try to plug device
Date: Tue, 15 Feb 2022 10:39:25 -0600 [thread overview]
Message-ID: <20220215163925.GA116437@bhelgaas> (raw)
In-Reply-To: <bug-215590-41252@https.bugzilla.kernel.org/>
On Fri, Feb 11, 2022 at 02:29:33PM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=215590
>
> Summary: PCI link is down after suspend after we try to plug
> device
> Kernel Version: 5.4 and 5.11
> Hardware: x86-64
> OS: Linux
> Tree: Mainline
> Severity: high
> Priority: P1
> Regression: No
>
> Created attachment 300434
> --> https://bugzilla.kernel.org/attachment.cgi?id=300434&action=edit
> dmesg log
>
> PCI link is not coming up
>
> we have been facing a race condition between AER and hoptplug stack which is
> happening after suspend when device is unplugged, to avoid that we have used
> below three patches.
>
> 1 - To Avoid lockdep
>
> https://lore.kernel.org/linux-pci/908047f7699d9de9ec2efd6b79aa752d73dab4b6.1595329748.git.lukas@wunner.de/
>
> 2 - AER sleep transition patch
> https://lore.kernel.org/linux-pci/20220127025418.1989642-1-kai.heng.feng@canonical.com/
>
> 3 - DPC sleep transition patch
> https://lore.kernel.org/linux-pci/20220127025418.1989642-2-kai.heng.feng@canonical.com/
>
>
> Additional info when we are using unplug using sysfs we dont see the issue
parent reply other threads:[~2022-02-15 16:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-215590-41252@https.bugzilla.kernel.org/>]
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=20220215163925.GA116437@bhelgaas \
--to=helgaas@kernel.org \
--cc=baolu.lu@linux.intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mika.westerberg@linux.intel.com \
--cc=rahul.kumar1@amd.com \
/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