From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 214789] ehci-hcd.c ISR
Date: Sat, 04 Dec 2021 00:02:50 +0000 [thread overview]
Message-ID: <bug-214789-208809-O02Z0lpp2B@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214789-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214789
Sean V Kelley (seanvk.dev@oregontracks.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |seanvk.dev@oregontracks.org
--- Comment #26 from Sean V Kelley (seanvk.dev@oregontracks.org) ---
Hi,
Thanks for reaching out Krzysztof.
So this platform is a Xeon E7-8867. which makes it a broadwell based Xeon.
I don't see it in the logs, what is the reported device ID? Those Xeon have
the capability disable the route to the ICH, which is these quirks are meant to
work with.
It also looks like you are using an out of tree driver? Is that correct?
Are you unable to use MSI with this device?
Sean
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2021-12-04 0:02 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 4:29 [Bug 214789] New: ehci-hcd.c ISR bugzilla-daemon
2021-10-21 5:56 ` Greg KH
2021-10-21 5:56 ` [Bug 214789] " bugzilla-daemon
2021-10-21 15:42 ` bugzilla-daemon
2021-10-21 16:02 ` bugzilla-daemon
2021-10-21 16:13 ` bugzilla-daemon
2021-10-21 19:27 ` bugzilla-daemon
2021-10-21 19:36 ` bugzilla-daemon
2021-10-21 19:37 ` bugzilla-daemon
2021-10-21 19:46 ` bugzilla-daemon
2021-10-21 20:04 ` bugzilla-daemon
2021-10-22 8:53 ` Johan Hovold
2021-10-22 8:53 ` bugzilla-daemon
2021-10-25 13:19 ` Johan Hovold
2021-10-25 13:19 ` bugzilla-daemon
2021-10-26 21:49 ` bugzilla-daemon
2021-10-27 2:05 ` bugzilla-daemon
2021-10-27 17:15 ` bugzilla-daemon
2021-10-27 20:07 ` bugzilla-daemon
2021-10-27 20:39 ` bugzilla-daemon
2021-10-27 21:14 ` bugzilla-daemon
2021-10-29 15:41 ` bugzilla-daemon
2021-11-01 19:07 ` bugzilla-daemon
2021-11-01 19:41 ` bugzilla-daemon
2021-11-01 19:49 ` bugzilla-daemon
2021-11-05 17:10 ` bugzilla-daemon
2021-11-05 19:39 ` Alan Stern
2021-11-16 19:40 ` Krzysztof Wilczyński
2021-11-05 18:56 ` bugzilla-daemon
2021-11-05 19:39 ` bugzilla-daemon
2021-11-16 19:40 ` bugzilla-daemon
2021-12-04 0:02 ` bugzilla-daemon [this message]
2021-12-04 0:05 ` bugzilla-daemon
2021-12-04 0:27 ` bugzilla-daemon
2021-12-04 0:29 ` bugzilla-daemon
2021-12-06 21:44 ` bugzilla-daemon
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=bug-214789-208809-O02Z0lpp2B@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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