From: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
To: micklorain <micklorain@protonmail.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"mathias.nyman@intel.com" <mathias.nyman@intel.com>
Subject: Re: [PATCH v1] usb: hcd: Try MSI interrupts on PCI devices
Date: Mon, 28 Feb 2022 22:59:04 +0200 [thread overview]
Message-ID: <Yh03mFSESvwT8Wt0@smile.fi.intel.com> (raw)
In-Reply-To: <PxIByDyBRcsbpcmVhGSNDFAoUcMmb78ctXCkw6fbpx25TGlCHvA6SJjjFkNr1FfQZMntYPTNyvEnblxzAZ8a6jP9ddLpKeCN6Chi_2FuexU=@protonmail.com>
On Mon, Feb 28, 2022 at 08:12:47PM +0000, micklorain wrote:
> Hi,
>
> This patch breaks USB for me. I noticed when I upgraded from debian's 4.19.0-18 (working) to 5.10.0-10 (broken). I git bisect'ed until I found that this patch is the culprit. Upstream 5.17.0-rc2 is still broken, but 5.17.0-rc2 with this patch reverted works.
>
> lsusb when things work :
> https://paste.debian.net/hidden/2a964425/
>
> lsusb when things are broken :
> https://paste.debian.net/hidden/0376920c/
>
> dmesg when things are broken :
> https://paste.debian.net/hidden/780ca112/
>
> dmesg when things work :
> https://paste.debian.net/hidden/4d1bfc0f/
>
> Let me know if you need anything else from me.
Thanks for your report!
Last time I have got something similar it becomes that PCI bridge which is used
to connect USB controller to the PCI Root Bridge was not capable of MSI, while
advertising that capability. I.o.w. HW bug.
To understand if it's something similar, please run (under the root) each of
the following commands:
lspci -nk -vvv
cat /proc/interrupts
in both cases, i.e. working and non-working.
And then share the output (all 4 files).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-02-28 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 20:12 [PATCH v1] usb: hcd: Try MSI interrupts on PCI devices micklorain
2022-02-28 20:27 ` gregkh
2022-03-13 21:53 ` micklorain
2022-02-28 20:59 ` andriy.shevchenko [this message]
2022-03-06 16:09 ` micklorain
2022-03-09 17:47 ` andriy.shevchenko
2022-03-13 21:44 ` micklorain
2022-03-14 9:57 ` andriy.shevchenko
-- strict thread matches above, loose matches on Subject: below --
2020-07-02 14:30 Andy Shevchenko
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=Yh03mFSESvwT8Wt0@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=micklorain@protonmail.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).