From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: Felipe Balbi <felipe.balbi@linux.intel.com>,
Oliver Neukum <oneukum@suse.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Kent Lin <kent.lin@canonical.com>,
Linux PCI <linux-pci@vger.kernel.org>,
Linux USB List <linux-usb@vger.kernel.org>
Subject: Re: Titan Ridge xHCI may stop to working after re-plugging the dock
Date: Wed, 14 Aug 2019 16:34:34 +0300 [thread overview]
Message-ID: <9f05b78d-7b28-1e8c-bdf9-22d0c148c719@linux.intel.com> (raw)
In-Reply-To: <78466959-E500-4AA0-8440-CBF80DBFE260@canonical.com>
On 13.8.2019 9.50, Kai-Heng Feng wrote:
> Hi Mathias,
>
> at 21:24, Kai-Heng Feng <kai.heng.feng@canonical.com> wrote:
>
>> at 22:45, Mathias Nyman <mathias.nyman@linux.intel.com> wrote:
>
> [snipped]
>
>> Yes, disabling runtime PM can workaround this issue.
>
> What’s next step here? Is it a firmware bug?
>
Can't say.
From xhci driver point of view the 39:00.0 xHC controller isn't accessible after dock
is plugged back in. Looks like PCI side has issues getting the controller back to D3
after it was runtime suspended to D0 at dock unplug:
[ 346.455568] pci_raw_set_power_state: 25 callbacks suppressed
[ 346.455574] xhci_hcd 0000:39:00.0: Refused to change power state, currently in D3
As Mika suggested in the bug take a look at PCI side, especially the PCI status before
a failing dock replug.
-Mathias
prev parent reply other threads:[~2019-08-14 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 13:10 Titan Ridge xHCI may stop to working after re-plugging the dock Kai-Heng Feng
2019-07-10 11:49 ` Oliver Neukum
2019-07-19 7:23 ` Felipe Balbi
2019-07-19 10:29 ` Kai Heng Feng
2019-07-19 10:51 ` Felipe Balbi
2019-07-22 9:44 ` Kai-Heng Feng
2019-07-24 14:45 ` Mathias Nyman
2019-07-25 13:24 ` Kai-Heng Feng
2019-08-13 6:50 ` Kai-Heng Feng
2019-08-14 13:34 ` Mathias Nyman [this message]
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=9f05b78d-7b28-1e8c-bdf9-22d0c148c719@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=felipe.balbi@linux.intel.com \
--cc=kai.heng.feng@canonical.com \
--cc=kent.lin@canonical.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=oneukum@suse.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).