From: Pete Zaitcev <zaitcev@redhat.com>
To: "Rhodes, Tom" <tom.rhodes@hp.com>
Cc: jbourne@mtroyal.ab.ca, zaitcev@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: lockups with 2.4.20 (tg3? net/core/dev.c|deliver_to_old_ones)
Date: Wed, 26 Feb 2003 14:56:22 -0500 [thread overview]
Message-ID: <20030226145622.C26604@devserv.devel.redhat.com> (raw)
In-Reply-To: <DC900CF28D03B745B2859A0E084F044D043506DD@cceexc19.americas.cpqcorp.net>; from tom.rhodes@hp.com on Wed, Feb 26, 2003 at 09:29:56AM -0600
> Date: Wed, 26 Feb 2003 09:29:56 -0600
> From: "Rhodes, Tom" <tom.rhodes@hp.com>
> > there is a deadlock: deliver_to_old_ones()attempts to stop all timers
> Until this is fixed, there are a couple work-arounds:
> - Put the system behind a NAT firewall. [...]
> - Switch to a non-NAPI driver. [...]
I think you are a little late with these workarounds, tg3 1.4c
is available for a week already.
http://people.redhat.com/jgarzik/tg3/tg3-1.4c/
People using ancient non-NAPI kernels better upgrade to 2.4.20.
If they really, really, really cannot upgrade (and this only
happens when they are stuck with binary module crap), they
should say "I will quit this tob tomorrow" three times,
then use RH AS2.1 driver, only make sure to get tg3 1.2e3
from drivers/addon/tg3 in 2.4.9-e.12.
-- Pete
next prev parent reply other threads:[~2003-02-26 19:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 15:29 lockups with 2.4.20 (tg3? net/core/dev.c|deliver_to_old_ones) Rhodes, Tom
2003-02-26 16:03 ` Jeff Garzik
2003-03-07 23:29 ` Magnus Naeslund(f)
2003-02-26 19:56 ` Pete Zaitcev [this message]
2003-02-26 20:54 ` Mikael Pettersson
-- strict thread matches above, loose matches on Subject: below --
2003-02-26 7:00 Rhodes, Tom
2003-02-26 12:45 ` Denis Vlasenko
2003-02-16 16:09 Manfred Spraul
[not found] <mailman.1045255801.17177.linux-kernel2news@redhat.com>
2003-02-14 21:02 ` Pete Zaitcev
2003-02-14 20:39 James Bourne
2003-02-18 2:48 ` David S. Miller
2003-02-18 4:21 ` James Bourne
2003-02-18 5:12 ` David S. Miller
2003-02-18 6:04 ` James Bourne
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=20030226145622.C26604@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=jbourne@mtroyal.ab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.rhodes@hp.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