From: <Mario.Limonciello@dell.com>
To: <lukas@wunner.de>
Cc: <mika.westerberg@linux.intel.com>, <linux-kernel@vger.kernel.org>,
<andreas.noever@gmail.com>, <michael.jamet@intel.com>,
<YehezkelShB@gmail.com>, <rjw@rjwysocki.net>, <lenb@kernel.org>,
<anthony.wong@canonical.com>, <rajmohan.mani@intel.com>,
<raanan.avargil@intel.com>, <David.Laight@ACULAB.COM>,
<linux-acpi@vger.kernel.org>
Subject: RE: [PATCH v3 0/8] thunderbolt: Intel Ice Lake support
Date: Tue, 20 Aug 2019 17:00:11 +0000 [thread overview]
Message-ID: <b5db55608d944b95a58cdfc7ccb60b69@AUSX13MPC101.AMER.DELL.COM> (raw)
In-Reply-To: <20190820113404.pm6qvqakdkcwdpat@wunner.de>
> -----Original Message-----
> From: Lukas Wunner <lukas@wunner.de>
> Sent: Tuesday, August 20, 2019 6:34 AM
> To: Limonciello, Mario
> Cc: mika.westerberg@linux.intel.com; linux-kernel@vger.kernel.org;
> andreas.noever@gmail.com; michael.jamet@intel.com;
> YehezkelShB@gmail.com; rjw@rjwysocki.net; lenb@kernel.org;
> anthony.wong@canonical.com; rajmohan.mani@intel.com;
> raanan.avargil@intel.com; David.Laight@ACULAB.COM; linux-
> acpi@vger.kernel.org
> Subject: Re: [PATCH v3 0/8] thunderbolt: Intel Ice Lake support
>
>
> [EXTERNAL EMAIL]
>
> On Mon, Aug 19, 2019 at 04:29:35PM +0000, Mario.Limonciello@dell.com wrote:
> > I've run into a problem when using
> > a WD19TB that after unplugging it will cause the following to spew in dmesg:
> >
> > [ 2198.017003] ============================================
> > [ 2198.017005] WARNING: possible recursive locking detected
> > [ 2198.017008] 5.3.0-rc5+ #75 Not tainted
> > [ 2198.017009] --------------------------------------------
> > [ 2198.017012] irq/122-pciehp/121 is trying to acquire lock:
> > [ 2198.017015] 00000000801d4de8 (&ctrl->reset_lock){.+.+}, at:
> pciehp_check_presence+0x1b/0x80
> > [ 2198.017026]
> > but task is already holding lock:
> > [ 2198.017028] 000000000899e2eb (&ctrl->reset_lock){.+.+}, at:
> pciehp_ist+0xaf/0x1c0
>
> This was first reported by Theodore in April and appears to be a
> false positive:
>
> https://lore.kernel.org/linux-
> pci/20190402083257.kyqmirq4ovzscxsv@wunner.de/
>
> Thanks,
>
> Lukas
Indeed it does actually seem harmless and only comes up once.
I've filed https://bugzilla.kernel.org/show_bug.cgi?id=204639 to track down further
what's going on.
next prev parent reply other threads:[~2019-08-20 17:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 11:22 [PATCH v3 0/8] thunderbolt: Intel Ice Lake support Mika Westerberg
2019-08-19 11:22 ` [PATCH v3 1/8] thunderbolt: Correct path indices for PCIe tunnel Mika Westerberg
2019-08-19 11:22 ` [PATCH v3 2/8] thunderbolt: Move NVM upgrade support flag to struct icm Mika Westerberg
2019-08-19 11:22 ` [PATCH v3 3/8] thunderbolt: Use 32-bit writes when writing ring producer/consumer Mika Westerberg
2019-08-19 11:22 ` [PATCH v3 4/8] thunderbolt: Do not fail adding switch if some port is not implemented Mika Westerberg
2019-08-19 11:22 ` [PATCH v3 5/8] thunderbolt: Hide switch attributes that are not set Mika Westerberg
2019-08-19 11:22 ` [PATCH v3 6/8] thunderbolt: Expose active parts of NVM even if upgrade is not supported Mika Westerberg
2019-08-19 11:22 ` [PATCH v3 7/8] thunderbolt: Add support for Intel Ice Lake Mika Westerberg
2019-08-19 11:22 ` [PATCH v3 8/8] ACPI / property: Add two new Thunderbolt property GUIDs to the list Mika Westerberg
2019-08-19 16:29 ` [PATCH v3 0/8] thunderbolt: Intel Ice Lake support Mario.Limonciello
2019-08-19 17:57 ` Mika Westerberg
2019-08-19 18:22 ` Mario.Limonciello
2019-08-19 19:36 ` Mario.Limonciello
2019-08-20 10:01 ` Mika Westerberg
2019-08-20 11:34 ` Lukas Wunner
2019-08-20 17:00 ` Mario.Limonciello [this message]
2019-08-26 9:20 ` Mika Westerberg
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=b5db55608d944b95a58cdfc7ccb60b69@AUSX13MPC101.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=David.Laight@ACULAB.COM \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=anthony.wong@canonical.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=raanan.avargil@intel.com \
--cc=rajmohan.mani@intel.com \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.