From: Jeff Garzik <jgarzik@pobox.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, davem@redhat.com
Subject: Re: 2.4.21-pre4: tg3 driver problems with shared interrupts
Date: Sun, 02 Feb 2003 11:49:12 -0500 [thread overview]
Message-ID: <3E3D4C08.2030300@pobox.com> (raw)
In-Reply-To: 20030202161837.010bed14.skraw@ithnet.com
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
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
2) 2.4.20 + tg3 v1.4
I'm interested to know if you can reproduce with the latest driver in
either of these two scenarios...
Jeff
[-- Attachment #2: tg3.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 49437 bytes --]
next prev parent reply other threads:[~2003-02-02 16:40 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 [this message]
2003-02-02 17:09 ` Stephan von Krawczynski
2003-02-02 17:15 ` Jeff Garzik
2003-02-02 17:52 ` Stephan von Krawczynski
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=3E3D4C08.2030300@pobox.com \
--to=jgarzik@pobox.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.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).