From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: micklorain <micklorain@protonmail.com>
Cc: "andriy.shevchenko@linux.intel.com"
<andriy.shevchenko@linux.intel.com>,
"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 21:27:12 +0100 [thread overview]
Message-ID: <Yh0wIGmoCjzKPTej@kroah.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/
This dmesg says:
[ 1.049161] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
have you tried that?
>
> dmesg when things work :
> https://paste.debian.net/hidden/4d1bfc0f/
The messages here look different for PCI, can you diff them?
I see:
[ 0.342113] PCI: PCI BIOS area is rw and x. Use pci=nobios if you want it NX.
[ 0.342178] PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=3
[ 0.342180] PCI: Using configuration type 1 for base access
That's not in the "failing" system, are you sure that's the only change
here?
thanks,
greg k-h
next prev parent reply other threads:[~2022-02-28 20:27 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 [this message]
2022-03-13 21:53 ` micklorain
2022-02-28 20:59 ` andriy.shevchenko
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=Yh0wIGmoCjzKPTej@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--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 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.