From owner-acpi-jp@jp.FreeBSD.org Sun Jan 20 02:52:57 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id g0JHqv888905;
	Sun, 20 Jan 2002 02:52:57 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from tao.org.uk (postfix@genius.tao.org.uk [212.135.162.51])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id g0JHqum88900
	for <acpi-jp@jp.FreeBSD.org>; Sun, 20 Jan 2002 02:52:56 +0900 (JST)
	(envelope-from joe@tao.org.uk)
Received: by tao.org.uk (Postfix, from userid 100)
	id EB6C24A7; Sat, 19 Jan 2002 17:52:30 +0000 (GMT)
Date: Sat, 19 Jan 2002 17:52:30 +0000
From: Josef Karthauser <joe@tao.org.uk>
To: acpi-jp@jp.FreeBSD.org
Message-ID: <20020119175230.B975@genius.tao.org.uk>
References: <20020119171459.C71324@genius.tao.org.uk> <200201191736.CAA52689@shidahara1.planet.sci.kobe-u.ac.jp>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-md5;
	protocol="application/pgp-signature"; boundary="lEGEL1/lMxI0MVQ2"
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200201191736.CAA52689@shidahara1.planet.sci.kobe-u.ac.jp>; from takawata@shidahara1.planet.sci.kobe-u.ac.jp on Sun, Jan 20, 2002 at 02:36:12AM +0900
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+011218
X-Sequence: acpi-jp 1561
Subject: [acpi-jp 1561] Re: acpi_alloc_wakeup_handler: unable to allocate wake memory
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: joe@tao.org.uk


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

On Sun, Jan 20, 2002 at 02:36:12AM +0900, Takanori Watanabe wrote:
> >MOV,PAT,PSE36,MMX,FXSR,SSE>
> >    real memory  =3D 536805376 (524224K bytes)
> >    avail memory =3D 516583424 (504476K bytes)
>=20
> If this message raised, the driver failed to allocate conventional memory
> and S2-S4BIOS support cannot be used in your machine.

Is this a bug in the driver, or a bug in my BIOS, or a hardware issue?
What can I do to determine this?

Joe

--lEGEL1/lMxI0MVQ2
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (FreeBSD)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjxJsl4ACgkQXVIcjOaxUBZj+wCeLpc1blyEtakzWWHXaG+iWK1y
dd0AoKYlSrpAYXdFKKGwDN8qkq7/BCrG
=T0MW
-----END PGP SIGNATURE-----

--lEGEL1/lMxI0MVQ2--
