* Re: 8139cp misses interrupts during resume
[not found] <42DD3BA1.7010302@drzeus.cx>
@ 2005-08-04 13:44 ` Pierre Ossman
2005-08-10 11:11 ` Pierre Ossman
0 siblings, 1 reply; 2+ messages in thread
From: Pierre Ossman @ 2005-08-04 13:44 UTC (permalink / raw)
To: netdev; +Cc: Jeff Garzik, LKML
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. :)
Rgds
Pierre
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: 8139cp misses interrupts during resume
2005-08-04 13:44 ` 8139cp misses interrupts during resume Pierre Ossman
@ 2005-08-10 11:11 ` Pierre Ossman
0 siblings, 0 replies; 2+ messages in thread
From: Pierre Ossman @ 2005-08-10 11:11 UTC (permalink / raw)
To: netdev; +Cc: Jeff Garzik, LKML
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-08-10 11:12 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <42DD3BA1.7010302@drzeus.cx>
2005-08-04 13:44 ` 8139cp misses interrupts during resume Pierre Ossman
2005-08-10 11:11 ` Pierre Ossman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox