Subject: Re: uvmpg.swpgonly botch
To: Chuck Silvers , Ignatios Souvatzis <firstname.lastname@example.org>
From: I. Souvatzis <email@example.com>
Date: 04/07/1999 11:27:01
On Wed, Apr 07, 1999 at 12:05:45AM -0700, Chuck Silvers wrote:
> Ignatios Souvatzis writes:
> > Hello,
> > I tried a low-memory boot, (4 MB DraCo / 68060 cpu / GENERIC + ISDN kernel)
> > and shortly after starting sshd (and before xdm
> > was really visible), I got
> > 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?
> scott was having the same problem on mac68k, but it went away
> when he pulled in the fixes jason had made to the hp300 pmap.
> maybe the amiga needs the same fixes?
What I had read about those commits sounded like "performance optimization"...
well, I'll try.
> if that doesn't help, I'd start with "call uvm_dump".
err, yes. Sounds reasonable.
* Progress (n.): The process through which Usenet has evolved from
smart people in front of dumb terminals to dumb people in front of
smart terminals. -- firstname.lastname@example.org (obscurity)