Subject: Re: Are there any known problems with uvm or pmap in -current as of about Oct. 16?
To: Monroe Williams <monroe@criticalpath.com>
From: Chuck Silvers <chuq@chuq.com>
List: port-macppc
Date: 10/26/2001 20:03:11
the bug in the new pmap that people have complained about causes a panic
when some sanity-checking code notices that the internal pmap state
has become inconsistent.

if you haven't had any problems with the old pmap, don't switch to the new one.
these pmap bugs are the sort that seem to only affect some people and not
others.  I've never had any problems with either pmap myself, but then
I don't do much with my powermac.

-Chuck


On Fri, Oct 26, 2001 at 01:24:09PM -0700, Monroe Williams wrote:
> on 10/25/01 9:49 PM, Chuck Silvers at chuq@chuq.com wrote:
> 
> > hi,
> > 
> > the only thing I can suggest at the moment is turning on "options NEWPMAP"
> > in your kernel config file.  the old powerpc pmap module had lots of bugs,
> > one of which you are experiencing now.  so a while back matt thomas
> > rewrote it, but unfortunately the new pmap also has bugs, but they're
> > different bugs.  so if one of them doesn't work for you, try the other one.
> > if you have problems with both of them, you may be out of luck for now.
> 
> That's not a very reassuring statement.  Would you care to be a little more
> specific about the bugs in the new pmap?
> 
> I've had uptimes of many months with a 1.5-branch kernel on macppc.  Did
> something happen to the old pmap between then and -current that broke things
> this badly?
> 
> -- monroe
> ------------------------------------------------------------------------
> Monroe Williams                                  monroe@criticalpath.com