From: Pierre Ossman <drzeus-list@drzeus.cx>
To: netdev@vger.kernel.org
Cc: Jeff Garzik <jgarzik@pobox.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 8139cp misses interrupts during resume
Date: Thu, 04 Aug 2005 15:44:54 +0200 [thread overview]
Message-ID: <42F21BD6.3000807@drzeus.cx> (raw)
In-Reply-To: <42DD3BA1.7010302@drzeus.cx>
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
next parent reply other threads:[~2005-08-04 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42DD3BA1.7010302@drzeus.cx>
2005-08-04 13:44 ` Pierre Ossman [this message]
2005-08-10 11:11 ` 8139cp misses interrupts during resume Pierre Ossman
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=42F21BD6.3000807@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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