public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Magnus Naeslund\(f\)" <mag@fbab.net>
To: "Jeff Garzik" <jgarzik@pobox.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: lockups with 2.4.20 (tg3? net/core/dev.c|deliver_to_old_ones)
Date: Sat, 8 Mar 2003 00:29:02 +0100	[thread overview]
Message-ID: <048901c2e501$569ef060$f80c0a0a@mnd> (raw)
In-Reply-To: 3E5CE539.60905@pobox.com

Jeff Garzik <jgarzik@pobox.com> wrote:
> Rhodes, Tom wrote:
[snip]
>>
>> 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

I got an hang/oops with the tg3 driver aswell.
I just wanted to make sure that 1.4c+ fixes this bug too:

ftp://ftp.fbab.net/pub/mag/tg3_oops_small.jpg

I've still got it in KDB if you want to find anything out from that
(tell me what to do) ...
Before this hang i had a e1000 card that also stopped working after a
while, so i switched to tg3, and ofcourse i got a hang there too :)

Regards

Magnus


  reply	other threads:[~2003-03-07 23:17 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) [this message]
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='048901c2e501$569ef060$f80c0a0a@mnd' \
    --to=mag@fbab.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox