From owner-freebsd-current Mon Oct 27 23:49:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA04955 for current-outgoing; Mon, 27 Oct 1997 23:49:50 -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 XAA04942 for ; Mon, 27 Oct 1997 23:49:41 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.8.7/D) id KAA29334; Tue, 28 Oct 1997 10:49:11 +0300 (MSK) Posted-Date: Tue, 28 Oct 1997 10:49:11 +0300 (MSK) Message-ID: <19971028104910.43916@demos.su> Date: Tue, 28 Oct 1997 10:49:10 +0300 From: "Mikhail A. Sokolov" To: current@freebsd.org Subject: current/nfs Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.75 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 Hello, there are two machines here which missbehave in very odd and different way: 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. Yet another missbehaves even funny: there is a jumper G, which will overlock processors to 233Mhz, which we happily did (970926-SNAP there). When we try to start it with 19971011-current kernel and processors at 200Mhz, it will 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. Ideas? -- -mishania