From: "Mr. Berkley Shands" <bshands@exegy.com>
To: Net Dev <netdev@vger.kernel.org>
Subject: forcedeth lockup in 2.6.21.5 and 2.6.22-rc6
Date: Tue, 26 Jun 2007 09:45:47 -0500 [thread overview]
Message-ID: <4681269B.8090208@exegy.com> (raw)
With Centos-5.0/Redhat 5.0 on multiple motherboards (Tyan 2995/
SuperMicro H8DCE)
The forcedeth network driver locks up under heavy NFS traffic (32KB frames)
such as linking shared libraries. It either gives a register dump
on a lock up in the transmit side, or loops complaining about
eth0: too many iterations (6) in nv_nic_irq
The system is hung. I cannot get to /var/log/messages, and only dmesg gives
information. "service network restart" or even reloading the
forcedeth.ko module
does not restore the link. The only fix is "reboot -f".
These machines are 4GB or 8GB opteron workstations. There is no problem
when using 2.6.20. The error counts reported by ifconfig usually show
framing errors, sometimes > 10 digits worth concurrent with this issue
(after being up 5 minutes). I can reproduce this 100% of the time with
2.6.21.5 and 2.6.22-rc6.
Any clues on what to try next?
berkley
--
// E. F. Berkley Shands, MSc//
** Exegy Inc.**
349 Marshall Road, Suite 100
St. Louis , MO 63119
Direct: (314) 218-3600 X450
Cell: (314) 303-2546
Office: (314) 218-3600
Fax: (314) 218-3601
The Usual Disclaimer follows...
This e-mail and any documents accompanying it may contain legally privileged and/or confidential information belonging to Exegy, Inc. Such information may be protected from disclosure by law. The information is intended for use by only the addressee. If you are not the intended recipient, you are hereby notified that any disclosure or use of the information is strictly prohibited. If you have received this e-mail in error, please immediately contact the sender by e-mail or phone regarding instructions for return or destruction and do not use or disclose the content to others.
reply other threads:[~2007-06-26 14:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4681269B.8090208@exegy.com \
--to=bshands@exegy.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).