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

On Wed, Jul 24, 2002 at 07:02:30PM +0200, Xavier HUMBERT wrote:
> You wrote :
>=20
> > You actually can cause problems that way. It
> > doesn't look like it's causing your problem here, but it's not good.
>=20
> No, it is not the problem. Even with current or 1.6BETA sysinst floppies
> it panics, while everythings fine with 1.5.2, until I mess the whole
> thing with partial nuilds :-)
>=20
> If it's not memory (which is unlikely, checked it with memtest86), the
> only thing that comes in mind is the Compaq SmartArray controller.

That's not convincing --- the only memory test that really detects softer
errors reliably is trying to compile something big with gcc :-).. memory
tester access patterns are often too regular to pick up timing/refresh
problem.

1.6 is more eager to use all the RAM than 1.5.x was... so maybe its sucn
an error in one of your modules (or part of your module, sorry, didn't=20
look close enough at your messages before starting to type).

Regards,
	-is

--=20
seal your e-mail: http://www.gnupg.org/

--WIyZ46R2i8wDzkSu
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

iD8DBQE9Pvn3PCRcZ/VMtk4RAt5mAJ9kTD6dnR0ToFa+SrnKGNq53XRmPQCcD1nW
3tY8t7qsYSV49rQGk6Y0Uo4=
=FsI1
-----END PGP SIGNATURE-----

--WIyZ46R2i8wDzkSu--