--/NkBOFFp2J2Af1nK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, May 07, 2002 at 03:35:27PM +0200, Thomas Runge wrote:
> > On Tue, May 07, 2002 at 07:46:28PM +1000, Murray Armfield wrote:
>=20
> > Although, can anybody explain why those kernels usually fail?
>=20
> Smells a bit like the mystical Sig11 problem:
>=20
> http://www.bitwizard.nl/sig11/

Gggrrr can't connect.

> The problem gets even worse now that we have UBC
> integrated. We are now using all available memory
> to cache data and faulty memory shows up quite
> early.

Mmmm... I've passed memtest86 several times and the memory looks perfect.
And the thing is that when I reboot into NetBSD, even with the GENERIC
kernel (which differs from the installation one) everything works
perfectly, and even better when I compile my own kernel.

>=20
> A reboot might help, as this will clear the memory
> and further actions might not touch the faulty region.

If memory was faulty, it should fail more usually... and my -current system
is quite stable (despite some problems with X).

>=20
> --=20
> Tom, who recently had to replace his memory module
> because of that...
>=20

--=20
Of course it runs NetBSD - http://www.netbsd.org
HispaBSD member - http://www.hispabsd.org
Julio Merino <jmmv@hispabsd.org>

--/NkBOFFp2J2Af1nK
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

iD8DBQE81/Jpzz00ZOPKycwRAuiPAJ9zjkKhRqanDHP2UljDBjrdYnUtjACfen+p
ksN+3AAkZOlEQSpg7TaXvu0=
=D42x
-----END PGP SIGNATURE-----

--/NkBOFFp2J2Af1nK--