Date: Wed, 29 Oct 1997 13:36:43 +0300 From: "Mikhail A. Sokolov" <mishania@demos.su> To: Steve Passe <smp@csn.net> Cc: current@FreeBSD.ORG Subject: Re: current/nfs Message-ID: <19971029133643.17087@demos.su> In-Reply-To: <199710281616.JAA23337@Ilsa.StevesCafe.com>; from Steve Passe <smp@csn.net> on Tue, Oct 28, 1997 at 09:16:04AM -0700 References: <19971028104910.43916@demos.su> <199710281616.JAA23337@Ilsa.StevesCafe.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 28, 1997 at 09:16:04AM -0700, Steve Passe wrote: # Hi, # > One machine runs 19971011-current and 'hangs' pretty regularily, then # > tries to reboot, tries to sync and there hangs. The machine has pretty hard # > task to be an nfs server for 5 others with up to 6000 interrupts/second, # > motherboard is intel PR440FX, 2xppro200, there are enough swap/memory space. # # be more specific, what messages come out when it hangs/reboots? 'Cannot switch to CPU 0' \n 'Syncing disks' (or what's that message..) and won't reboot. That's last one I caught yesterday, all other cases were just 'Syncing' and there we stale. Now I made it non-SMP :-(, awaiting ... Btw, what's that when it has 2 cpu's, the average load is _always_ >1,3, where when the second processor is not enabled, it's _always_ (exept when they start some perl :-)) > 0,60 ? It's peer (2.2.2+security fixes) would casually yelp that nfs server is not responding, the find it (in a second or so) and finally hang in a frozen state with a 'nfsbiostat panic'. #> yell it can't start second CPU, - mp_lock 1000005, abort trap. It will do ok #> on 233Mhz with 19971011-current, as well as 970926-SNAP. # this is probably the race fixed by: Thank you. # Steve Passe -- -mishania, stressed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971029133643.17087>