From: David Brownell <david-b@pacbell.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andre Tomt <andre@tomt.net>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>
Subject: Re: USB OOPS 2.6.25-rc2-git1
Date: Wed, 20 Feb 2008 13:56:28 -0800 [thread overview]
Message-ID: <200802201356.28723.david-b@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0802201606430.7212-100000@iolanthe.rowland.org>
On Wednesday 20 February 2008, Alan Stern wrote:
> > ehci_hcd 0000:00:1d.7: IAA watchdog, lost IAA: status 8029 cmd 10021
>
> lines in the log brings up some ideas that have been percolating in my
> mind for a while. They have to do with the possibility of a race
> between the watchdog routine and assertion of IAA.
The curious bit IMO being STS_INT (0001), which should also have
triggered an IRQ. Suggesting to me that the race might be lower
level than that ... at the level of a conflict between the various
mechanisms to ack irqs.
See the appended patch (Andre, this is the additional one I meant)
for a tweak at that level.
> In fact, if the timing comes out just wrong then it's possible (on SMP
> systems) for an IAA interrupt to arrive when the watchdog
> routine has already started running. Then end_unlink_async() might get
> called right at the start of a new IAA cycle, or when the reclaim list
> is empty.
The driver's spinlock should prevent that particular problem from
appearing.
- Dave
========= CUT HERE
Modify EHCI irq handling on the theory that at least some of the
"lost" IRQs are caused by goofage between multiple lowlevel IRQ
acking mechanisms: try rescanning before we exit the handler, in
case the EHCI-internal ack (by clearing the irq status) doesn't
always suffice for IRQs triggered nearly back-to-back.
---
drivers/usb/host/ehci-hcd.c | 8 ++++++++
1 file changed, 8 insertions(+)
--- g26.orig/drivers/usb/host/ehci-hcd.c 2008-02-20 13:26:00.000000000 -0800
+++ g26/drivers/usb/host/ehci-hcd.c 2008-02-20 13:54:37.000000000 -0800
@@ -638,6 +638,8 @@ static irqreturn_t ehci_irq (struct usb_
return IRQ_NONE;
}
+retrigger:
+
/* clear (just) interrupts */
ehci_writel(ehci, status, &ehci->regs->status);
cmd = ehci_readl(ehci, &ehci->regs->command);
@@ -725,6 +727,12 @@ dead:
if (bh)
ehci_work (ehci);
+
+ status = ehci_readl(ehci, &ehci->regs->status);
+ status &= INTR_MASK;
+ if (status)
+ goto retrigger;
+
spin_unlock (&ehci->lock);
if (pcd_status & STS_PCD)
usb_hcd_poll_rh_status(hcd);
next prev parent reply other threads:[~2008-02-20 22:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 15:19 USB OOPS 2.6.25-rc2-git1 Andre Tomt
2008-02-19 18:49 ` David Brownell
2008-02-19 23:04 ` Andre Tomt
2008-02-20 0:32 ` David Brownell
2008-02-20 20:33 ` Andre Tomt
2008-02-20 21:16 ` Alan Stern
2008-02-20 21:56 ` David Brownell [this message]
2008-02-20 22:33 ` Alan Stern
2008-02-20 22:54 ` David Brownell
2008-02-21 16:15 ` Alan Stern
2008-03-05 4:15 ` David Brownell
2008-03-05 17:04 ` Alan Stern
2008-03-05 17:39 ` David Brownell
2008-02-21 15:56 ` Alan Stern
2008-02-25 9:13 ` David Brownell
2008-02-20 21:24 ` David Brownell
2008-02-21 0:25 ` Andre Tomt
2008-02-21 0:53 ` David Brownell
2008-02-19 19:31 ` Alan Stern
2008-02-19 21:58 ` Andre Tomt
2008-02-19 22:24 ` David Miller
2008-02-20 0:19 ` David Brownell
2008-02-20 1:40 ` David Miller
2008-02-20 16:10 ` Alan Stern
2008-02-19 22:28 ` Andre Tomt
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=200802201356.28723.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=andre@tomt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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