From: "David S. Miller" <davem@redhat.com>
To: Greg Banks <gnb@sgi.com>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] fix BUG in tg3_tx
Date: Mon, 24 May 2004 00:40:45 -0700 [thread overview]
Message-ID: <20040524004045.58b3eb44.davem@redhat.com> (raw)
In-Reply-To: <20040524072657.GC27177@sgi.com>
On Mon, 24 May 2004 17:26:58 +1000
Greg Banks <gnb@sgi.com> wrote:
> The tg3 transmit code assumes that tg3_tx() will never have to clean
> up part of an skb queued for transmit. This assumption is wrong;
Greg, perhaps my reading of the tg3 chip docs is different
from yours. The hardware is NEVER supposed to do this.
Or is there an errata in some chip versions?
I've never triggered that BUG() assertion on any of my
hardware, ever.
next prev parent reply other threads:[~2004-05-24 7:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 7:26 [PATCH] fix BUG in tg3_tx Greg Banks
2004-05-24 7:40 ` David S. Miller [this message]
2004-05-24 8:04 ` Greg Banks
2004-05-24 17:06 ` David S. Miller
2004-05-25 1:04 ` Greg Banks
2004-05-25 17:51 ` David S. Miller
2004-05-25 19:20 ` [PATCH] tg3 h/w flow control autoneg Arthur Kepner
2004-05-25 20:01 ` David S. Miller
2004-05-26 0:12 ` [PATCH] fix BUG in tg3_tx Greg Banks
2004-05-25 17:52 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2004-05-24 17:26 Michael Chan
2004-05-24 17:33 Michael Chan
2004-05-25 20:04 Michael Chan
2004-05-26 0:54 ` Greg Banks
2004-05-26 16:04 ` Greg Banks
2004-05-26 18:01 ` David S. Miller
2004-05-26 23:47 ` Greg Banks
2004-05-26 23:52 ` David S. Miller
2004-05-27 0:12 ` Greg Banks
2004-05-26 1:22 Michael Chan
2004-05-26 17:43 Michael Chan
2004-05-26 18:47 ` David S. Miller
2004-05-26 23:52 ` Greg Banks
2004-05-26 23:50 ` Greg Banks
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=20040524004045.58b3eb44.davem@redhat.com \
--to=davem@redhat.com \
--cc=gnb@sgi.com \
--cc=netdev@oss.sgi.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).