From: "Gerhard Pircher" <gerhard_pircher@gmx.net>
To: Steffen Klassert <klassert@mathematik.tu-chemnitz.de>
Cc: shemminger@vyatta.com, netdev@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: 3c59x: shared interrupt problem
Date: Thu, 12 Mar 2009 16:12:37 +0100 [thread overview]
Message-ID: <20090312151237.50420@gmx.net> (raw)
In-Reply-To: <20090312143930.GA17955@newton.mathematik.tu-chemnitz.de>
-------- Original-Nachricht --------
> Datum: Thu, 12 Mar 2009 15:39:30 +0100
> Von: Steffen Klassert <klassert@mathematik.tu-chemnitz.de>
> An: Gerhard Pircher <gerhard_pircher@gmx.net>
> CC: akpm@linux-foundation.org, netdev@vger.kernel.org, shemminger@vyatta.com
> Betreff: Re: 3c59x: shared interrupt problem
> On Wed, Mar 11, 2009 at 11:42:40PM +0100, Gerhard Pircher wrote:
> >
> > > Your first report showed dnComplete as a pending interrupt source.
> > > Since the driver uses tx_interrupt_mitigation, this happens just if
> > > the tx ring is full. Could you please test the patch below? This
> > > disables tx_interrupt_mitigation, so the dnComplete interrupt will
> > > be triggered with every packet.
> > I disabled tx_interrupt_mitigation and tested it with and w/o the
> > patch for boomerang_interrupt(). The network transfer stalls in both
> > cases sooner or later.
> >
> > Here are two photos from the kernel output:
> > - no tx_interrupt_mitigation and patch for booomerang_interrupt():
> >
> http://boot.homelinux.org:8080/kernel/oops_boomerang_irq_tx_irq_mitig.jpg
> > - no tx_interrupt_mitigation only:
> > http://boot.homelinux.org:8080/kernel/oops_tx_irq_mitig.jpg
> >
>
> Your pictures show just a message at shutdown. Are there any other
> unusual messages from the 3c59x driver in your logs? In particular I'm
> interested in "transmit timed out" messages.
Unfortunately no. But I had disabled debugging in the driver until now, as
it slows down the network transfer considerably. I'll rerun the test with
debugging enabled.
I'm going to retry 'git bisect' next week. Maybe I find a way to compile a
bootable image for older kernel versions.
Thanks!
Gerhard
--
Nur bis 16.03.! DSL-Komplettanschluss inkl. WLAN-Modem für nur
17,95 ¿/mtl. + 1 Monat gratis!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a
next prev parent reply other threads:[~2009-03-12 15:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 22:42 3c59x: shared interrupt problem Gerhard Pircher
2009-03-12 14:39 ` Steffen Klassert
2009-03-12 15:12 ` Gerhard Pircher [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-09 22:42 Gerhard Pircher
2009-03-09 23:49 ` Stephen Hemminger
2009-03-10 8:16 ` Steffen Klassert
2009-03-10 21:55 ` Andrew Morton
2009-03-11 11:38 ` Steffen Klassert
2009-03-13 22:51 ` David Miller
2009-03-14 14:08 ` Steffen Klassert
2009-03-14 18:40 ` David Miller
2009-03-17 9:37 ` Gerhard Pircher
[not found] ` <20090310090053.322240@gmx.net>
2009-03-11 11:31 ` Steffen Klassert
2009-03-27 7:59 ` Steffen Klassert
2009-03-28 14:17 ` Gerhard Pircher
2009-04-21 18:36 ` Gerhard Pircher
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=20090312151237.50420@gmx.net \
--to=gerhard_pircher@gmx.net \
--cc=akpm@linux-foundation.org \
--cc=klassert@mathematik.tu-chemnitz.de \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).