--k+w/mQv8wyuph6w0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 29, 2004 at 07:03:14PM -0400, Pilipovic  Josip wrote:
> I have built kernel with following options
> options         MEMORY_DISK_HOOKS
> options         MEMORY_DISK_IS_ROOT    =20
> options         MEMORY_DISK_SERVER=3D1  =20
> # 4M memory disk, in blocks
> options         MEMORY_DISK_ROOT_SIZE=3D16384      # 8M memory disk, in b=
locks
> options         MEMORY_RBFLAGS=3D0=20
>=20
> The boot process stops after some address display and PC reboots. If I ch=
ange
> options     MEMORY_DISK_ROOT_SIZE=3D8192 4M
> ram disk kernel boots OK. Secondary boot is filing on pread() system call.
> This problem don't exist on PPC. Is there any work aroud  this problem for
> i385. Any hint!!! =20

Note: since you're still in the booter, pread() isn't a system call. At=20
least not in the same sense as after boot.

My first guess is that something about how the kernel gets loaded means=20
you try to write memory that's not there for boot when you get things too=
=20
big.

The reason you don't see this on PPC is that things at this stage are very=
=20
machine-dependant. Note that in the past certain MacPPC systems would have=
=20
an issue with too-big a kernel. Right now MacPPC has "too big" at 13 MB=20
total.

--k+w/mQv8wyuph6w0
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFA4gQPWz+3JHUci9cRAhROAJ9PENwCiCA3bpZxHW8xnb8mut4Q+QCZAS2U
qn8o2ohub9YjCGhapoNcWFg=
=1aJq
-----END PGP SIGNATURE-----

--k+w/mQv8wyuph6w0--