From: Andre Noll <maan@systemlinux.org>
To: mchan@broadcom.com
Cc: linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: 2.6.21.x kernel panic (tg3 and nfs related)
Date: Wed, 27 Jun 2007 12:16:08 +0200 [thread overview]
Message-ID: <20070627101608.GQ22589@skl-net.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
Hi
Our nfs server recently paniced under heavy nfs load. The backtrace
indicates that this might be a problem with the tigon3 network driver
which drives the onboard chips of the machine.
The first crash under 2.6.21.1 happened after about 4 days of uptime,
2.6.21.5 already crashed after 15 Minutes.
Screenshots of the resulting kernel panics are available at
http://www.systemlinux.org/~maan/shots/huangho-crash-2.6.21.1.png
and
http://www.systemlinux.org/~maan/shots/huangho-crash-2.6.21.5.png
We're now running 2.6.18.6 again which happens to be rock solid for our
workload. However, this kernel now spits out zillons of messages like
[55122.674290] RPC: bad TCP reclen 0x00010094 (large)
I'm sure it didn't do that half a year ago when it was running for
several months. The 2.6.21.x kernels did not print these messages
either, but from what I understand this is due to a patch which went
in somewhere between 2.6.18 and 2.6.21 and which just ratelimited
the message.
So something weird seems to be going on in our network and this might
well be related to the 2.6.21.x crashes we are seeing.
Thanks
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-06-27 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 10:16 Andre Noll [this message]
2007-06-27 15:58 ` Chuck Ebbert
2007-06-27 16:12 ` Andre Noll
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=20070627101608.GQ22589@skl-net.de \
--to=maan@systemlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=nfs@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®