From: "Mr. Berkley Shands" <berkley@cs.wustl.edu>
To: netdev <netdev@vger.kernel.org>
Cc: "Mark A. Bober" <mark@cts.wustl.edu>, "Lloyd, Dave" <dlloyd@exegy.com>
Subject: 2.6.29 forcedeth hang W/O NAPI enabled
Date: Tue, 24 Mar 2009 10:28:25 -0500 [thread overview]
Message-ID: <49C8FC19.5080201@cs.wustl.edu> (raw)
Another new kernel, another interesting lock up. Centos 5.2, X86_84 on
an opteron 8GB 4 cores (275 X 2).
If CONFIG_FORCEDETH_NAPI is not enabled, then within 60 seconds of the
console login prompt
appearing, the network becomes unresponsive. packets are seen to appear
according to ifconfig eth0
and with ethtool -S eth0, but they go nowhere. NFS stops, ping stops,
logins stop, ldap stops.
My network is class B, netmask 255.255.0.0, and the department router is
directly connected
under this netmask. If I re-compile the forcedeth.ko with NAPI enabled,
then reinstall it,
and depmod -aq then
service network stop; rmmod forcedeth; modprobe forcedeth; service
network start
brings everything back online eventually. This was not an issue with
2.6.28-8 or before.
Berkley
next reply other threads:[~2009-03-24 15:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 15:28 Mr. Berkley Shands [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-25 23:24 2.6.29 forcedeth hang W/O NAPI enabled Adam Richter
2009-03-26 0:05 ` David Miller
2009-03-26 1:20 ` Adam Richter
2009-03-26 3:14 ` David Miller
2009-03-26 3:36 ` Herbert Xu
2009-03-26 5:24 ` Adam Richter
2009-03-26 6:58 ` Herbert Xu
2009-03-26 23:29 ` Adam Richter
2009-03-26 0:06 Adam Richter
2009-03-26 0:08 ` David Miller
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=49C8FC19.5080201@cs.wustl.edu \
--to=berkley@cs.wustl.edu \
--cc=dlloyd@exegy.com \
--cc=mark@cts.wustl.edu \
--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).