Subject: Re: Will Robinson is back!
To: Haapanen, Tom <tomh@metrics.com>
From: Jason R Thorpe <thorpej@wasabisystems.com>
List: port-alpha
Date: 04/23/2002 08:40:06
On Tue, Apr 23, 2002 at 05:53:17AM -0400, Haapanen, Tom wrote:

 > Two years after I first saw this, Will Robinson appears to be back on our
 > 164SX-based web server:
 > 
 > stratos 137 # grep "WILL ROBINSON" messages* 
 > messages:Apr 22 15:03:15 stratos /netbsd: DANGER WILL ROBINSON: FEN SET IN
 > cpu_fork!
 > messages:Apr 23 00:39:29 stratos /netbsd: DANGER WILL ROBINSON: FEN SET IN
 > cpu_fork!
 > messages:Apr 23 00:39:30 stratos /netbsd: DANGER WILL ROBINSON: FEN SET IN
 > cpu_fork!
 > messages.0:Apr 22 00:43:40 stratos /netbsd: DANGER WILL ROBINSON: FEN SET IN
 > cpu_fork!
 > messages.1:Apr 18 18:43:55 stratos /netbsd: DANGER WILL ROBINSON: FEN SET IN
 > cpu_fork!
 > messages.2:Apr 16 15:44:20 stratos /netbsd: DANGER WILL ROBINSON: FEN SET IN
 > cpu_fork!

Wow, what version of NetBSD are you running?  It must be not very recent,
as that message was removed from the kernel quite some time ago (after
reexamination of the definition of the bit in a structure that it's warning
about).

 > stratos 142 # grep "panic:" messages*
 > messages:Apr 23 00:56:35 stratos /netbsd: panic: uvm_fault_unwire: unwiring
 > non-wired memory
 > messages.0:Apr 22 00:56:24 stratos /netbsd: panic: uvm_fault_unwire:
 > unwiring non-wired memory
 > messages.1:Apr 18 18:36:46 stratos /netbsd: panic: uvm_fault_unwire:
 > unwiring non-wired memory

This problem has been fixed, as well.

I suggest you upgrade to a newer version.

-- 
        -- Jason R. Thorpe <thorpej@wasabisystems.com>