From: Maurice Volaski <mvolaski@aecom.yu.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SMP Netfinity 340 hangs under 2.4.19
Date: Fri, 23 Aug 2002 04:47:57 -0400 [thread overview]
Message-ID: <a05111609b98ba20903b0@[129.98.90.227]> (raw)
In-Reply-To: <1030090864.5932.5.camel@irongate.swansea.linux.org.uk>
> > A single processor Netfinity 340 running RedHat 7.1 and kernel 2.4.18
>> was recently upgraded to
>>
>> 1) 1 GB RAM
>> 2) second processor (1 Ghz Xeon)
>> 3) 2.4.19 for SMP with bigmem and added NFS server patches and
>> ext3-related patches.
>
>Exactly what patches ? and does unpatched 2.4.19 behave ?
These from Neil Brown:
patch-A-UmemWarn Fix the compile warning ....
patch-B-0-9-18 Latest Ext3 patches
patch-C-Ext3Fixes Fix some problems with ext3
patch-D-NfsdLookupTidy Tidy up code in nfsd_lookup
patch-E-NfsdInit Tidyup init/exit fof nfsd module
patch-F-NfsdFsid Support fsid= export option to be device
number independent
patch-G-NfsdLocksExplock Change export table lock to (SMP
safe) rwsemaphore
patch-H-NfsdLocksCachelock Lock reply cache with SMP safety.
patch-I-NfsdLocksNfssvc Tidy up locking in nfssvc - preparing for BKL removal
patch-J-NfsdLocksRename protect rename and related operations by kernel_lock
patch-K-NfsdFhLock protect file handle lookup by kernel lock
patch-L-NfsdLocksRacache protect read-ahead cache with SMP safe locking
patch-M-NfsdBKLgone Remove last unneeded bit of BKL from knfsd
patch-N-RpcLists Change sunrpc to use more list.h lists
patch-O-RpcInit Get sunrpc to use module_init properly
patch-P-RpcSvcLocking Tidy up SMP locking for svc_sock
patch-Q-RpcTcpCloseBad Detect and close tcp connections that we
cannot work with.
patch-R-RpcTcpCloseIdle Close idle rpc/tcp sockets
patch-S-RpcTcpReserve Make sure there is alway adequate sndbuf
space for replies.
patch-T-RpcSvcTcpLimit Limit number of active tcp connections to an
RPC service
patch-U-NfsdTcpEnable Enable NFS over TCP via config option
patch-c-NfsfhErrFix Correct some error codes reutrned in nfsfh.c
I haven't tried plain 2.4.19 yet. Should I have reason to not trust
these patches?
> > Is there significance to the fact that keyboard and mouse are frozen
>> but apparently some processes are still up?
>
>Interrupts are running but its stuck looping in kernel space I suspect.
So could this be taken to mean the issue is most likely software
(presumably kernel)-related?
--
Maurice Volaski, mvolaski@aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University
next prev parent reply other threads:[~2002-08-23 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 7:58 Maurice Volaski
2002-08-23 8:21 ` Alan Cox
2002-08-23 8:47 ` Maurice Volaski [this message]
2002-08-23 8:57 ` Alan Cox
2002-09-03 17:24 ` Maurice Volaski
2002-08-23 14:16 ` Martin J. Bligh
2002-09-04 20:18 ` Bill Davidsen
2002-09-05 15:56 Maurice Volaski
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='a05111609b98ba20903b0@[129.98.90.227]' \
--to=mvolaski@aecom.yu.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®