public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Straz <nstraz@sgi.com>
To: David Rees <dbr@greenhydrant.com>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: Spontaneous Call Trace?
Date: Mon, 4 Nov 2002 12:44:06 -0600	[thread overview]
Message-ID: <20021104184406.GC2030@sgi.com> (raw)
In-Reply-To: <20021104101501.A812@greenhydrant.com>

On Mon, Nov 04, 2002 at 10:15:01AM -0800, David Rees wrote:
> I just encountered a dual CPU machine running 2.4.18 with the NFS_ALL and
> xfs patch which spontaneously generated two complete call traces over the
> weekend.  There was no Oops or kernel bug recorded in the syslog although
> syslog functionality remained intact.  After this point functionality on the
> system was degraded (various processes were not accepting new connections)
> and we rebooted the system.  We're planning on upgrading to 2.4.19 with the
> NFS_ALL and ext3-all patches ASAP.
> 
> I've never seen this type of behavior before in my years of using Linux, has
> anyone else?  BTW, sysrq is disabled on the machine...

Could you post the call traces?  Also, do you see any relevant messages
in your log files?  Perhaps there is a forced shutdown message.

-- 
Nate Straz                                              nstraz@sgi.com
sgi, inc                                           http://www.sgi.com/
Linux Test Project                                  http://ltp.sf.net/

      reply	other threads:[~2002-11-04 18:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04 18:15 Spontaneous Call Trace? David Rees
2002-11-04 18:44 ` Nathan Straz [this message]

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=20021104184406.GC2030@sgi.com \
    --to=nstraz@sgi.com \
    --cc=dbr@greenhydrant.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@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