Subject: Re: DIAGNOSTIC seems to trigger fault in oea_init()
To: David P. Reese, Jr. <daver@siginfo.org>
From: Michael <macallan18@earthlink.net>
List: port-macppc
Date: 01/30/2006 06:40:33
--Signature_Mon__30_Jan_2006_06_40_33_-0500_IpFQDX.aFyHn02Mq
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hello,

> I'm surprised that other people haven't seen this problem so I'm=20
> wondering if it is specific to my hardware (early Aluminum PowerBook
> G4).

It happens on all my macppc boxes ( S900 with G3, iMac G3, iBook G4 ),
it went over the list a few times but I didn't find time yet to
investigate any further. Symptoms differ slightly - on the S900 it's
just a DEFAULT CATCH right after loading, the iBook behaves like your
PowerBook.

> Kernels built with DIAGNOSTIC seem to fault in
> oea_machdep.c:oea_init() on line 175 where memcpy() is called to
> populate the trap vector at address 0.
>=20
> What I don't understand is that addresses 0x0-0x100 are zeroed
> on line 166 which doesn't cause a trap.  Also, changing the for loop
> to start populating trap vectors at address EXC_RST instead of 0
> allows kernels with DIAGNOSTIC to boot.

Whatever caused this must be a fairly recent change, a 3.99.14 kernel
didn't have this problem IIRC.

have fun
Michael

--Signature_Mon__30_Jan_2006_06_40_33_-0500_IpFQDX.aFyHn02Mq
Content-Type: application/pgp-signature

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

iQEVAwUBQ937McpnzkX8Yg2nAQIOcggAm1Ma4EEk22lgiDaztg5i3ZZBMvXsD48g
Tt20BAbK/ZObxsm4ECcgbwZNsSjCNmYpmLJH7QKabMJKlH3ZRUTUZNB7z+xlr6T0
t5oUo8pgckhL75rackHofiodz3/Qj961pvAXac782Mq7aPwSFWxBscmB5Ik4JM4L
Q/PABnCdflFzxTBYT9RipIqHHCvEWdnp6CV3WUoY+r/cD1b7EWwNz43OojIKDg0J
DJcLlQRfpRcahT8fFIZDYMKc5KS8YBdsqEoGLupOnzuWWrEIKL3csakJNqnwcrKY
dQzL3TsniUbEsrLsv3gN1s/YEtU8fSscIjYuNWdT6l7ZEZOLPcKNcA==
=4/+H
-----END PGP SIGNATURE-----

--Signature_Mon__30_Jan_2006_06_40_33_-0500_IpFQDX.aFyHn02Mq--