On Wed, 7 Apr 1999 07:34:20 +0200 
 Ignatios Souvatzis <is@jocelyn.rhein.de> wrote:

 > panic: uvmexp.swpgonly botch
 > stopped in pagedaemon at _Debugger+0x6
 > 
 > trace shows:
 > 
 > _Debugger
 > _panic
 > _uvmpd_scan_inactive
 > _uvmpd_scan
 > _uvm_pageout
 > _start_page_daemon
 > _proc_trampoline
 > 
 > with both an April 4 1.4A and yestereves (CET) 1.4_ALPHA kernel (DRACO with
 > only INET but added i4b). From the code snippet below I guess this is either
 > a missed uvmexp.swpgonly--, uvmexp.swpages++, or a real problem.
 > 
 > Anything I can do (besides undefining DIAGNOSTIC and pray?) Chuck, anything
 > you want me to look at from the db> prompt?

Hm... cvs blame shows this to be part of The Other Chuck's swap fixes to
deal with extreme resource shortages better...

"Eeee."

        -- Jason R. Thorpe <thorpej@nas.nasa.gov>