From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>, Mason <slash.tmp@free.fr>
Cc: Niklas <niklas@vividvisions.se>,
linux-pci <linux-pci@vger.kernel.org>,
linux-usb <linux-usb@vger.kernel.org>,
Mathias Nyman <mathias.nyman@intel.com>,
Lukas Wunner <lukas@wunner.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [bugzilla-daemon@bugzilla.kernel.org: [Bug 197159] New: Xhci host controller not responding starting kernel 4.13]
Date: Tue, 10 Oct 2017 11:26:00 +0300 [thread overview]
Message-ID: <59DC8418.2050808@linux.intel.com> (raw)
In-Reply-To: <20171009233852.GO25517@bhelgaas-glaptop.roam.corp.google.com>
On 10.10.2017 02:38, Bjorn Helgaas wrote:
> On Mon, Oct 09, 2017 at 10:45:39PM +0200, Mason wrote:
>> On 09/10/2017 19:01, Bjorn Helgaas wrote:
>> ...
>
>>> In that thread, Mason reported a regression that looks similar, but as
>>> far as I can tell, we never identified a root cause.
>>>
>>> 1) The problem Mason reported was on a Tango platform, which has a
>>> known hardware issue that corrupts data when simultaneous config
>>> and MMIO accesses occur. You're seeing the problem on a
>>> different platform, which is very helpful.
>>
>> As mentioned here:
>> https://www.mail-archive.com/linux-usb@vger.kernel.org/msg94020.html
>>
>> When I disable the AER driver, not a single config space access
>> occurs when a USB drive is unplugged. So I'm 99.99% sure that
>> the issue is NOT caused by tango's bad design. (I got the vibe
>> that nobody cared about tango's issue because it was assumed
>> that the design flaw was responsible for it.)
>
> I agree; I don't think this is Tango's fault.
>
> Can you test fe190ed0d602 and d9f11ba9f107 to determine whether
> d9f11ba9f107 is the culprit? If it is the culprit, can you try reverting
> it on a current kernel to see if that fixes it?
>
> If d9f11ba9f107 is not the culprit, can you bisect to discover exactly
> where it broke?
>
If possible could the bug reporter add the same WARN is Mason to see
when xhci reads 0xffffffff, or if something else triggers xhci_hc_died()
In the Tango case it was the hub thread clearing a port reset change event.
diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
index 82c746e..cd3a420 100644
--- a/drivers/usb/host/xhci-ring.c
+++ b/drivers/usb/host/xhci-ring.c
@@ -908,6 +908,8 @@ void xhci_hc_died(struct xhci_hcd *xhci)
{
int i, j;
+ WARN_ON(1);
if (xhci->xhc_state & XHCI_STATE_DYING)
return;
Thanks
Mathias
next prev parent reply other threads:[~2017-10-10 8:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 17:01 [bugzilla-daemon@bugzilla.kernel.org: [Bug 197159] New: Xhci host controller not responding starting kernel 4.13] Bjorn Helgaas
2017-10-09 20:45 ` Mason
2017-10-09 23:38 ` Bjorn Helgaas
2017-10-10 8:26 ` Mathias Nyman [this message]
2017-10-11 10:34 ` Mason
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=59DC8418.2050808@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mathias.nyman@intel.com \
--cc=niklas@vividvisions.se \
--cc=slash.tmp@free.fr \
--cc=stern@rowland.harvard.edu \
/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.