From: Stephan von Krawczynski <skraw@ithnet.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org, davem@redhat.com
Subject: Re: 2.4.21-pre4: tg3 driver problems with shared interrupts
Date: Sun, 2 Feb 2003 18:52:05 +0100 [thread overview]
Message-ID: <20030202185205.261a45ce.skraw@ithnet.com> (raw)
In-Reply-To: <3E3D4C08.2030300@pobox.com>
On Sun, 02 Feb 2003 11:49:12 -0500
Jeff Garzik <jgarzik@pobox.com> wrote:
> Stephan von Krawczynski wrote:
> > I found out within minutes that this setup does not survive if you let the
> > Broadcom cards share interrupts with anything else. It works ok now like
> > this (eth2 is tg3):
>
> [...]
> > But horribly failed in such a setup:
>
> [...]
> > I cannot even produce a "cat /proc/interrupts" for this because I am not
> > fast enough at login (the network at eth2 is heavy loaded). I sometimes
> > read about problems here with tg3-drivers, and I just wanted to point you
> > to the shared case, maybe it has to do with this special case rather than
> > with the drivers internals itself.
> > (PS: its not the ide2-3, I checked that out)
>
>
>
> hmmm. I've attached the latest tg3, version 1.4, which I just sent off
> to Marcelo. It includes some fixes that may affect your 5701.
>
> Can you try two things?
>
> 1) 2.4.21-pre4 + tg3 v1.4
Ok. With the latest version you sent I got it compiled and working. As far as I
can tell from short tests it looks good (eth2 is tg3):
CPU0
0: 79344 XT-PIC timer
1: 2428 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 0 XT-PIC EMU10K1
7: 81 XT-PIC HiSax
9: 387286 XT-PIC aic7xxx, aic7xxx, eth0, eth1, eth2
11: 75780 XT-PIC ide2, ide3
12: 17740 XT-PIC PS/2 Mouse
15: 2 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0
To make sure I will let it stress-test overnight and send you the results in
about 15 hours from now on. If everything does fine I will redo with ide2,ide3
on same interrupt, too. Just to see what happens with these Promise things...
--
Thanks a lot, I'll be back,
Stephan
next prev parent reply other threads:[~2003-02-02 17:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-02 15:18 2.4.21-pre4: tg3 driver problems with shared interrupts Stephan von Krawczynski
2003-02-02 16:49 ` Jeff Garzik
2003-02-02 17:09 ` Stephan von Krawczynski
2003-02-02 17:15 ` Jeff Garzik
2003-02-02 17:52 ` Stephan von Krawczynski [this message]
2003-02-02 18:28 ` Jeff Garzik
2003-02-02 18:31 ` Stephan von Krawczynski
2003-02-03 10:25 ` Stephan von Krawczynski
2003-02-05 9:48 ` 2.4.21-pre4: PDC ide " Stephan von Krawczynski
2003-02-05 11:16 ` Benjamin Herrenschmidt
2003-02-05 11:39 ` Stephan von Krawczynski
2003-02-05 12:21 ` Alan Cox
2003-02-05 12:22 ` Benjamin Herrenschmidt
2003-02-05 12:50 ` Alan Cox
2003-02-05 13:19 ` Stephan von Krawczynski
2003-02-05 12:24 ` Alan Cox
2003-02-05 16:56 ` Ross Biro
2003-02-05 17:12 ` Benjamin Herrenschmidt
2003-02-05 17:19 ` Ross Biro
2003-02-05 17:34 ` Benjamin Herrenschmidt
2003-02-05 17:38 ` Stephan von Krawczynski
[not found] ` <1044467091.685.155.camel@zion.wanadoo.fr>
2003-02-05 17:58 ` Stephan von Krawczynski
2003-02-05 20:00 ` Bryan Andersen
2003-02-05 19:10 ` Alan Cox
2003-02-06 12:20 ` Stephan von Krawczynski
2003-02-06 23:04 ` Benjamin Herrenschmidt
2003-02-07 9:10 ` Stephan von Krawczynski
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=20030202185205.261a45ce.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.