From: Mikael Pettersson <mikpe@user.it.uu.se>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: "Rhodes, Tom" <tom.rhodes@hp.com>,
jbourne@mtroyal.ab.ca, 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 21:54:15 +0100 [thread overview]
Message-ID: <15965.10615.231875.609023@gargle.gargle.HOWL> (raw)
In-Reply-To: <20030226145622.C26604@devserv.devel.redhat.com>
Pete Zaitcev writes:
> > 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.
Which non-AS RH8.0 kernel should one use to not get hangs from tg3?
I had to downgrade our Dell PE2650 from 2.4.18-24 to 2.4.18-17 since
2.4.18-24 and -19 caused bi-weekly hangs, while -17 and earlier never
had any problems. -18 seemed Ok, but the box didn't run it very long.
This is a compile server with very light network load: a couple of
ssh sessions, NFS-mounted home dirs, ntpd, nothing else.
/Mikael
next prev parent reply other threads:[~2003-02-26 20:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 15:29 Rhodes, Tom
2003-02-26 16:03 ` Jeff Garzik
2003-03-07 23:29 ` Magnus Naeslund(f)
2003-02-26 19:56 ` Pete Zaitcev
2003-02-26 20:54 ` Mikael Pettersson [this message]
-- 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=15965.10615.231875.609023@gargle.gargle.HOWL \
--to=mikpe@user.it.uu.se \
--cc=jbourne@mtroyal.ab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.rhodes@hp.com \
--cc=zaitcev@redhat.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
all inboxes | Powered by JetHome®