From: Ben Greear <greearb@candelatech.com>
To: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: 2.4.21: bug report for tg3: tx lockup when changing MTU
Date: Fri, 01 Aug 2003 15:54:55 -0700 [thread overview]
Message-ID: <3F2AEFBF.3040604@candelatech.com> (raw)
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.
When the tg3 is locked up, I see this on the console:
Aug 1 15:05:44 demo2 kernel: NETDEV WATCHDOG: eth5: transmit timed out
Aug 1 15:05:44 demo2 kernel: tg3: eth5: transmit timed out, resetting
Aug 1 15:05:44 demo2 kernel: tg3: tg3_stop_block timed out, ofs=2400 enable_bit=2
Aug 1 15:05:44 demo2 kernel: tg3: tg3_stop_block timed out, ofs=1400 enable_bit=2
Aug 1 15:05:44 demo2 kernel: tg3: tg3_stop_block timed out, ofs=c00 enable_bit=2
Aug 1 15:05:54 demo2 kernel: NETDEV WATCHDOG: eth5: transmit timed out
Aug 1 15:05:54 demo2 kernel: tg3: eth5: transmit timed out, resetting
Aug 1 15:05:54 demo2 kernel: tg3: tg3_stop_block timed out, ofs=2400 enable_bit=2
Aug 1 15:05:54 demo2 kernel: tg3: tg3_stop_block timed out, ofs=1400 enable_bit=2
...
Kernel is 2.4.21 + custom patches (which should not affect tg3).
lspci says the NIC is: Altima AC9100 (rev 15)
I will be happy to provide more information as needed.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2003-08-01 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 22:54 Ben Greear [this message]
2003-08-01 23:57 ` 2.4.21: bug report for tg3: tx lockup when changing MTU Jeff Garzik
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=3F2AEFBF.3040604@candelatech.com \
--to=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).