From: Bjorn Helgaas <helgaas@kernel.org>
To: linux-pci@vger.kernel.org
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Lukas Wunner <lukas@wunner.de>,
Mario Limonciello <mario_limonciello@dell.com>
Subject: [bugzilla-daemon@bugzilla.kernel.org: [Bug 204639] New: PCIEHP deadlock w/ Thunderbolt on ICL hardware]
Date: Tue, 20 Aug 2019 17:36:35 -0500 [thread overview]
Message-ID: <20190820223635.GE14450@google.com> (raw)
[Mario, the lspci attached to the bugzilla looks truncated]
----- Forwarded message from bugzilla-daemon@bugzilla.kernel.org -----
Date: Tue, 20 Aug 2019 16:50:09 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: bugzilla.pci@gmail.com
Subject: [Bug 204639] New: PCIEHP deadlock w/ Thunderbolt on ICL hardware
Message-ID: <bug-204639-193951@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204639
Bug ID: 204639
Summary: PCIEHP deadlock w/ Thunderbolt on ICL hardware
Product: Drivers
Version: 2.5
Kernel Version: v5.3-rc5
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: PCI
Assignee: drivers_pci@kernel-bugs.osdl.org
Reporter: mario_limonciello@dell.com
Regression: No
Created attachment 284535
--> https://bugzilla.kernel.org/attachment.cgi?id=284535&action=edit
lspci
w/ 5.3rc5 I find that plugging in or unplugging a Thunderbolt dock (WD19TB)
into this ICL system will cause a deadlock. At that point it's not possible to
use the dock anymore.
As a debugging tactic I did test applying
https://lore.kernel.org/patchwork/patch/1113961/ but it did not help the
behavior.
--
You are receiving this mail because:
You are watching the assignee of the bug.
----- End forwarded message -----
reply other threads:[~2019-08-20 22:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190820223635.GE14450@google.com \
--to=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mario_limonciello@dell.com \
--cc=mika.westerberg@linux.intel.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;
as well as URLs for NNTP newsgroup(s).