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
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 [email protected]
sgi, inc http://www.sgi.com/
Linux Test Project http://ltp.sf.net/