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: gabriel rosenkoetter <gr@eclipsed.net>
List: port-macppc
Date: 10/27/2001 02:19:16
--++alDQ2ROsODg1x+
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 26, 2001 at 01:24:09PM -0700, Monroe Williams wrote:
> 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 thi=
ngs
> this badly?

Chuq could obviously say more about this, but in general a whole lot
changed about UVM between 1.4 and 1.5 that could well change how
everything interacts with pmap making what was okay in it before
panic-causing.

I don't know the details, but the pmap is definitely not code
isolated from UVM enough (nor should it be) to mean that changes in
UVM don't tickle it in bad ways.

--=20
       ~ g r @ eclipsed.net

--++alDQ2ROsODg1x+
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (NetBSD)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjvaUeQACgkQ9ehacAz5CRqolwCfQWq5X1lsHJqJGfJpV12Q2558
voMAoI8BIaiDuj37Xg59TmAmJvRmm4Qv
=HnoU
-----END PGP SIGNATURE-----

--++alDQ2ROsODg1x+--