From: Jeff Garzik <jgarzik@pobox.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: netdev@oss.sgi.com
Subject: Re: 8390.c workaround for interrupt storm
Date: Fri, 13 Aug 2004 16:17:34 -0400 [thread overview]
Message-ID: <411D21DE.2050804@pobox.com> (raw)
In-Reply-To: <20040813153047.GC28640@logos.cnet>
Marcelo Tosatti wrote:
> Hi netdev,
>
> We've been seeing an interrupt storm on our
> embedded PowerPC systems with Linksys PCMLM56 (network+modem)
> PCMCIA cards (network part of it driven by pcnet_cs.c) as soon as the network
> cable is pluged/unpluged and after some activity on the serial
> line.
>
> The card goes nuts, and doesnt stop sending interrupts.
>
> So I hacked up this patch which resets the 8390 chip
> as soon as 256 empty interrupts are triggered. Works fine,
> the card comes back to sanity after resetting.
>
> Not sure if its specific to our boards, but I believe
> it might happen on other archs also, so I'm posting it
> here in the hope it might be useful for someone with the
> same problem.
>
> Not likely to be included in mainline driver, but hey, why not,
> its protection against hardware insanity.
You have stumbled on a common class of problems, I think.
IMO interrupt storms are almost always caused by the platform or bus. I
see tons of bug reports for ethernet drivers which turn out to be
interrupt routing, interrupt handling, or interrupt storms unrelated to
the ethernet driver itself.
Yes, you can sometimes work around this in the driver, but that tends to
wind up hiding the problem.
PCMCIA debugging isn't fun, to be sure, maybe RMK has some ideas?
Jeff
next prev parent reply other threads:[~2004-08-13 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 15:30 8390.c workaround for interrupt storm Marcelo Tosatti
2004-08-13 20:17 ` Jeff Garzik [this message]
2004-08-13 20:07 ` Marcelo Tosatti
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=411D21DE.2050804@pobox.com \
--to=jgarzik@pobox.com \
--cc=marcelo.tosatti@cyclades.com \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).