--Signature_Thu__9_Jun_2005_12_29_18_-0400_e=EEXcg9_+9+1RHD
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

> > > > It would be good if NetBSD could use, store, and maintain a "bad pa=
ge=20
> > > > map" so that once a bad page in RAM is identified (through parity/E=
CC=20
> > > > errors), it can be avoided.
> > >=20
> > > Hmm, if a parity error happens, does it mean it's going to happen aga=
in and
> > > again ?
> >=20
> > Most likely. And if ECC can't cover it up you'll get all kinds of nasti=
ness from it.=20
>=20
> Do you have a reference for this? My understanding is that most memory
> errors are transient, not permanent.

I get similar errors on my SPARCbook, always at the same physical address s=
o I'm pretty sure it's a bad memory module. This leads to NMIs, DMA errors,=
 random crashes and so on, marking the memory area unusable would certainly=
 help ( ok, replacing the bad memory module would help even more but for va=
rious reasons I can't do that right now ).

have fun
Michael

--Signature_Thu__9_Jun_2005_12_29_18_-0400_e=EEXcg9_+9+1RHD
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (NetBSD)

iQEVAwUBQqhuYcpnzkX8Yg2nAQKAqQf9E3f8fmaFF5hwFhJgj2tVhKvFlAMP90F1
b7WhVqYgSr1bTVarU5NpJS5UYnowkWkr9LyLdmhiaZ96t/OhluzRAjuaRFpXySYi
3jbNO+26Hqek6jMQQA929twOq0TZ4uFqQ52sxI7+EZjsQ6kthI/QjbhxnXkQ1HO8
fVC3P3EYD7TVLFTWw8dcjTPM0dm9tpbmx2A1THkbwd1jW9yKoPpZFeT+NTA0Jfzd
PYlG9VpAZp6QOWjgRaOhAMMYYQWuj+SzC7kzG5APg091G1QVzE8kJ6qIMzsYDiNZ
b6eIuf0UGELzfx0Mpi9cF+YN7cUlUSINp3ZyNOkRl/Gyxx7uN2LTKA==
=FUVf
-----END PGP SIGNATURE-----

--Signature_Thu__9_Jun_2005_12_29_18_-0400_e=EEXcg9_+9+1RHD--