From owner-freebsd-hackers  Sun Aug 10 11:48:23 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA06298
          for hackers-outgoing; Sun, 10 Aug 1997 11:48:23 -0700 (PDT)
Received: from sev.mtelecom.ru (gw2.mtelecom.ru [195.90.159.22])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA06292
          for <hackers@freebsd.org>; Sun, 10 Aug 1997 11:48:18 -0700 (PDT)
Received: (from uucp@localhost)
          by sev.mtelecom.ru (8.8.4/8.8.4) with UUCP
	  id WAA29681; Sun, 10 Aug 1997 22:51:58 +0400 (MSD)
Received: from darkstar.da.mtelecom.ru (darkstar.da.mtelecom.ru [192.168.1.37]) by anka.da.mtelecom.ru (8.8.3/8.8.3) with ESMTP id WAA03695; Sun, 10 Aug 1997 22:24:02 +0400 (MSD)
Received: (from seva@localhost)
	by darkstar.da.mtelecom.ru (8.8.5/8.8.5) id WAA05832;
	Sun, 10 Aug 1997 22:37:38 +0400 (MSD)
To: Doug White <dwhite@resnet.uoregon.edu>, hackers@freebsd.org
Subject: Re: vm_fault problem (fwd)
References: <Pine.BSF.3.96.970807123229.252p-100000@localhost>
From: Seva Semenov <seva@darkstar.da.mtelecom.ru>
Date: 10 Aug 1997 22:37:32 +0400
In-Reply-To: Doug White's message of 8 Aug 1997 03:19:14 +0400
Message-ID: <86sowhj34j.fsf@darkstar.da.mtelecom.ru>
Lines: 34
X-Mailer: Gnus v5.3/Emacs 19.34
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



I had the same on different hardware (5 machines P100/P133/486DX4-100
Compex en2000/3Com ) with 2.2.1 and 2.2.2-RELEASE.
Removing by Midnight Commander big nfs directory coz rebooting.
I'm not  hacker to hack kernel code. 
Only solution i found - downgrade to 2.1.7.1-RELEASE.

But the only reason i can't be happy with 2.1.7.1 is  linux quake :).


Doug White <dwhite@gdi.uoregon.edu> writes:
[...]
> Since the upgrade the machine has been rebooting at random intervals
> (anything from 5 minutes to 2 days) and 
> I can find no log trace or core files.
> Then yesterday I caught it doing it and managed to write it down! I THINK
> this is exactly what it said...
> 
> vm_fault: fault on nofault entry: address f296c000
> 
> then it had something about syncing the disks (it failed) and that I could
> press a key to stop the reboot. I did press a key but it rebooted anyway.
> 
> PLEASE help!!! Is it a bad SIMM??? MB Cache? Should I disable the cache?
> 
> This machine is my gateway. My ISDN is connected to it, as are all 5 of my
> dialup lines. This reboot thing is crippling my business! Thank you in
> advance for your help.