Re: 8139cp misses interrupts during resume

[Pierre Ossman <drzeus-list@drzeus.cx>]

Pierre Ossman wrote:
> Pierre Ossman wrote:
> 
>>I'm having problem with the interrupt getting killed after suspend with
>>my 8139cp controller. The problem only appears if the cable is connected
>>during resume (before suspend is irrelevant) and the interface is down.
>>
>>Both suspend-to-disk and suspend-to-ram exhibit the error. dmesg from
>>suspend-to-ram included.
>>
>>I find it a bit strange that 8139cp's interrupt handler isn't included
>>when it dumps the handlers. Could this be related to the problem?
>>
> 
> 
> Anyone familiar with this driver that can give me some pointers on what
> to look for? I'd prefer not to have to learn how the entire thing works
> just to fix one bug. :)
> 

I've gotten a bit close now at least. The problem is that the IRQ
handler isn't registered until the device is opened (up:ed) but the
hardware triggers interrupt even in a closed state. So either the
hardware needs to be silenced or the handler needs to be installed earlier.

Rgds
Pierre
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/