public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 214789] ehci-hcd.c ISR
Date: Thu, 21 Oct 2021 15:42:33 +0000	[thread overview]
Message-ID: <bug-214789-208809-seqwIf3kil@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214789-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=214789

--- Comment #2 from Scott Arnold (scott.c.arnold@nasa.gov) ---
Hello,
The driver is for a Symmetricom bc635pcie Time and Frequency Processor. Driver
developed in house for ISS simulations.
Works fine on 5.3 and prior kernels.
Works fine with 5.11 if not using shared IRQ's. No interrupts with shared
IRQ's.
Machine is a HP dl580 G9 w/ 72 Intel(R) Xeon(R) CPU E7-8867 v4 @ 2.40GHz.
We only have a few of these machines the rest are G10's and work fine (not
sharing IRQ's with timing cards).
I am having the card moved to another slot to try and get a unshared IRQ.
Unfortunately MSI does not seem possible with this card.
Thanks
Scott

-----Original Message-----
From: bugzilla-daemon@bugzilla.kernel.org <bugzilla-daemon@bugzilla.kernel.org> 
Sent: Thursday, October 21, 2021 12:56 AM
To: Arnold, Scott C. (JSC-CD13)[SGT, INC] <scott.c.arnold@nasa.gov>
Subject: [EXTERNAL] [Bug 214789] ehci-hcd.c ISR

https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.kernel.org%2Fshow_bug.cgi%3Fid%3D214789&amp;data=04%7C01%7Cscott.c.arnold%40nasa.gov%7C149886803eb94e8808d708d994577fa2%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637703925801703360%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=gCbZYRYzD3U0wbZswfjv%2FGeEe3Y3VEua%2BmqL1opeCOM%3D&amp;reserved=0

--- Comment #1 from Greg Kroah-Hartman (greg@kroah.com) --- On Thu, Oct 21,
2021 at 04:29:42AM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> 
> Change in ehci_irq from spin_lock_irqsave/irqrestore to 
> spin_lock/unlock broke shared IRQ's

What shared irq broke exactly?  For what hardware platform?  And what kernel
version worked for you and now does not work?

thanks,

greg k-h

--
You may reply to this email to add a comment.

You are receiving this mail because:
You reported the bug.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2021-10-21 15:42 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 [this message]
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
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-seqwIf3kil@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