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

On Thu, Sep 13, 2007 at 03:13:49PM -0500, Peter Eisch wrote:
>=20
> I have this i386 system that doesn't even get close to booting under 3.x =
but
> I was surprise to see boot with 4.0b2.  There's an odd behavior thought t=
hat
> I'd like to understand better.
>=20
> >From the time the boot blocks finish loading the kernel until anything g=
ets
> printed on the console nothing seems to be happening.  For around 2 minut=
es
> the system appears to be dead aside from the drive activity light blinking
> sparsely, sporadically.
>=20
> I've seen acpi info get written back to the console on other P4 systems
> during this period but they also go on to continue booting normally.  Once
> the kernel starts to print, it continues normally and the system otherwise
> behaves fine.
>=20
> Is this a known behavior?  (The kernel is GENERIC.MP plus some other
> features like ipsec.)

I've seen a system wait for 10 solid minutes at that point before the
kernel printed anything.  It was a HP DL series, and in the BIOS there
was a setting about 8042 emulation...  It did the trick.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"You could have made it, spitting out benchmarks
Owe it to yourself not to fail"
Amplifico, Spitting Out Benchmarks, Hometakes Vol. 2, 2005.

--cLQvRfYaHwHCueo/
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iQEVAwUBRuo4sdgoQloHrPnoAQK9HAf/SOHu2Sr/x5qERNd/i05Q2W+Qgzab0GM1
PWyotYhn19MebT4bVreE6jhRqVqUZSYdUvcplY2thCjpHtgpcU41w7ZQOrjqwDGA
4tzuRQW+MNikNZS6Hb1P8N8S9dolvdaojXe2c4C+WJsnwZjjxNL5KQ8eaGNUSqsh
cWpy+VElTvxciCynIwCN/SUs/sy7Sj1cWkEufD0mVaw7Qyjwy6waXguEFTtVcwgO
MiQqkiw4Jdr0fsOnNLx0sQNPhwDONU6K6z/THjU8ZQe3OO/KiZMWolp+6ZSJn6Dz
N80RgP8Nrp7metdwIUnaLJivB0xQ92gLwWjRWXJt+RY0OCgBDLEzCQ==
=UmTQ
-----END PGP SIGNATURE-----

--cLQvRfYaHwHCueo/--