From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 214789] ehci-hcd.c ISR
Date: Thu, 21 Oct 2021 19:37:56 +0000 [thread overview]
Message-ID: <bug-214789-208809-QZ7MWxoRHT@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 #7 from Scott Arnold (scott.c.arnold@nasa.gov) ---
Anything you want me to try while I have the hardware available?
-----Original Message-----
From: bugzilla-daemon@bugzilla.kernel.org <bugzilla-daemon@bugzilla.kernel.org>
Sent: Thursday, October 21, 2021 2:28 PM
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&data=04%7C01%7Cscott.c.arnold%40nasa.gov%7C551e718474f3400d4b2508d994c8e126%7C7005d45845be48ae8140d43da96dd17b%7C0%7C0%7C637704412758963825%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qrlaDQOIszpc5Q%2BNbQUxzpDh%2FIyBIvCclogFe2OAAm0%3D&reserved=0
--- Comment #5 from Alan Stern (stern@rowland.harvard.edu) --- Okay, but _why_
don't the timing card's interrupts get handled when ehci_irq uses spin_lock?
And _why_ does changing to spin_lock_irqsave make a difference?
Do all of the card's interrupt requests get lost or only some of them?
Are you somehow getting recursive (nested) interrupts for the same IRQ line?
Is ehci_irq somehow getting called with interrupts enabled?
I don't want to make any changes to the driver until we know the answers to
these questions.
--
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.
next prev parent reply other threads:[~2021-10-21 19:38 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 [this message]
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-QZ7MWxoRHT@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 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.