From: David Rees <dbr@greenhydrant.com>
To: linux-kernel@vger.kernel.org
Subject: Spontaneous Call Trace?
Date: Mon, 4 Nov 2002 10:15:01 -0800 [thread overview]
Message-ID: <20021104101501.A812@greenhydrant.com> (raw)
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...
-Dave
next reply other threads:[~2002-11-04 18:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-04 18:15 David Rees [this message]
2002-11-04 18:44 ` Spontaneous Call Trace? Nathan Straz
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=20021104101501.A812@greenhydrant.com \
--to=dbr@greenhydrant.com \
--cc=linux-kernel@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