From: Jeff Garzik <jgarzik@pobox.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 11:03:05 -0500 [thread overview]
Message-ID: <3E5CE539.60905@pobox.com> (raw)
In-Reply-To: <DC900CF28D03B745B2859A0E084F044D043506DD@cceexc19.americas.cpqcorp.net>
[-- Attachment #1: Type: text/plain, Size: 631 bytes --]
Rhodes, Tom wrote:
>>Here is the call stack of the deadlocked CPUs on a RH8.0 system with a
>>2.4.18-24.8.0 smp kernel:
>>CPU 2:
>>deliver_to_old_ones+45
>>netif_receive_skb
>>tg3_rx+27b
>>tg3_poll+81
>>net_rx_action
>>do_softirq
>>do_IRQ
>>call_do_IRQ
>>
>>CPU 6:
>>tg3_timer (tg3+9fc4)
>>run_timer_list+0x112
>>bh_action+55
>>tasklet_hi_action+67
>>do_softirq+d9
>>do_IRQ
>>call_do_IRQ+5
>>
>
> Until this is fixed, there are a couple work-arounds:
It's fixed in tg3 version 1.4c, which is attached. James Bourne also
put up tg3 2.4.20 patches containing the needed fixes, at
http://www.hardrock.org/kernel/2.4.20
Jeff
[-- Attachment #2: tg3.tar.bz2 --]
[-- Type: application/octet-stream, Size: 63488 bytes --]
next prev parent reply other threads:[~2003-02-26 15:53 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 [this message]
2003-03-07 23:29 ` Magnus Naeslund(f)
2003-02-26 19:56 ` Pete Zaitcev
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=3E5CE539.60905@pobox.com \
--to=jgarzik@pobox.com \
--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