From: Chuck Ebbert <cebbert@redhat.com>
To: Andre Noll <maan@systemlinux.org>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org,
mchan@broadcom.com
Subject: Re: 2.6.21.x kernel panic (tg3 and nfs related)
Date: Wed, 27 Jun 2007 11:58:18 -0400 [thread overview]
Message-ID: <4682891A.2070900@redhat.com> (raw)
In-Reply-To: <20070627101608.GQ22589@skl-net.de>
On 06/27/2007 06:16 AM, Andre Noll wrote:
> 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
>
Looks the the known oops in show_mem(); patch is queued for 2.6.21.6.
But it is hard to tell when the screen shot doesn't show the whole
message...
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
WARNING: multiple messages have this Message-ID (diff)
From: Chuck Ebbert <cebbert@redhat.com>
To: Andre Noll <maan@systemlinux.org>
Cc: mchan@broadcom.com, linux-kernel@vger.kernel.org,
nfs@lists.sourceforge.net
Subject: Re: 2.6.21.x kernel panic (tg3 and nfs related)
Date: Wed, 27 Jun 2007 11:58:18 -0400 [thread overview]
Message-ID: <4682891A.2070900@redhat.com> (raw)
In-Reply-To: <20070627101608.GQ22589@skl-net.de>
On 06/27/2007 06:16 AM, Andre Noll wrote:
> 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
>
Looks the the known oops in show_mem(); patch is queued for 2.6.21.6.
But it is hard to tell when the screen shot doesn't show the whole
message...
next prev parent reply other threads:[~2007-06-27 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 10:16 2.6.21.x kernel panic (tg3 and nfs related) Andre Noll
2007-06-27 10:16 ` Andre Noll
2007-06-27 15:58 ` Chuck Ebbert [this message]
2007-06-27 15:58 ` Chuck Ebbert
2007-06-27 16:12 ` Andre Noll
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=4682891A.2070900@redhat.com \
--to=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maan@systemlinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.