From owner-freebsd-current Wed Oct 29 02:38:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA07900 for current-outgoing; Wed, 29 Oct 1997 02:38:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA07886 for ; Wed, 29 Oct 1997 02:38:09 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.8.7/D) id NAA19182; Wed, 29 Oct 1997 13:36:44 +0300 (MSK) Posted-Date: Wed, 29 Oct 1997 13:36:44 +0300 (MSK) Message-ID: <19971029133643.17087@demos.su> Date: Wed, 29 Oct 1997 13:36:43 +0300 From: "Mikhail A. Sokolov" To: Steve Passe Cc: current@FreeBSD.ORG Subject: Re: current/nfs References: <19971028104910.43916@demos.su> <199710281616.JAA23337@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75 In-Reply-To: <199710281616.JAA23337@Ilsa.StevesCafe.com>; from Steve Passe on Tue, Oct 28, 1997 at 09:16:04AM -0700 Organization: Demos Company, Ltd., Moscow, Russian Federation. X-Point-of-View: Gravity is myth, - the earth sucks. Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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.