netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Ben Greear <greearb@candelatech.com>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: 2.4.21: bug report for tg3:  tx lockup when changing MTU
Date: Fri, 01 Aug 2003 19:57:46 -0400	[thread overview]
Message-ID: <3F2AFE7A.10203@pobox.com> (raw)
In-Reply-To: <3F2AEFBF.3040604@candelatech.com>

Ben Greear wrote:
> I just noticed that if you change the MTU of a tg3 NIC, it will not work
> untill you ifdown/ifup it.  This problem is repeatable on tg3, and does not
> happen with the e1000 driver/cards.
> 
> I am setting the MTU via an ioctl call, not via ifconfig or something like
> that.


Can you provide the ioctl call info, so I can reproduce?

And, are you changing MTU when the interface is up or down?

  reply	other threads:[~2003-08-01 23:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 22:54 2.4.21: bug report for tg3: tx lockup when changing MTU Ben Greear
2003-08-01 23:57 ` Jeff Garzik [this message]
2003-08-02  0:24   ` Ben Greear
2003-08-02  9:44 ` Sascha Schumann
2003-08-03  3:48   ` Ben Greear

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=3F2AFE7A.10203@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=greearb@candelatech.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).