> > My other point still stands though. The IRQ for all HCDs _are_ freed
> > on suspend, and re-requested on resume ... so lack of such free/request
> > calls can't possibly be an issue.
>
> Yes it can. Apparently on my box the call to request_irq() from a USB HCD
> driver (OHCI or EHCI) causes a screaming interrupt to be generated,
> which kills any other driver that shares the IRQ with the USB and has not
> called free_irq() on suspend.
So it's as I said: _lack_ of such calls can't be an issue.
So _which_ device is generating this IRQ??
> Of course this only happens with the patch
> at http://www.ussg.iu.edu/hypermail/linux/kernel/0507.3/2234.html
> unapplied, as it masks the problem.
Hmm, an ACPI patch. With tabs completely trashed; that
mail archive needs to learn about <pre>...</pre. :(
> Actually it also depends on the
> order in which the drivers' resume routines are called, but unfortunately
> on my box the USB drivers' are called first.
Suggesting that the issue comes from the non-USB driver
sharing that IRQ line...
- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |