On Wednesday 20 February 2008, Alan Stern wrote: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. 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); --
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Linus Torvalds | Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series.. |
| Paul Jackson | Re: cpuset-remove-sched-domain-hooks-from-cpusets |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Linus Torvalds | Re: [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [klibc] [patch] import socket defines |
