From owner-freebsd-acpi@FreeBSD.ORG Fri Oct 28 17:56:30 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D615C16A41F for ; Fri, 28 Oct 2005 17:56:30 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68DDA43D48 for ; Fri, 28 Oct 2005 17:56:30 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Fri, 28 Oct 2005 14:13:18 -0400 From: John Baldwin To: Mathieu Prevot Date: Fri, 28 Oct 2005 13:58:04 -0400 User-Agent: KMail/1.8.2 References: <971FCB6690CD0E4898387DBF7552B90E0323D7B6@orsmsx403.amr.corp.intel.com> <435928CA.1010305@root.org> <55E0CA58-AC1E-48E4-A4D0-DDC5829D3690@yahoo.fr> In-Reply-To: <55E0CA58-AC1E-48E4-A4D0-DDC5829D3690@yahoo.fr> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200510281358.06083.jhb@freebsd.org> Cc: freebsd-acpi@freebsd.org Subject: Re: ACPI errors on amd64 (sempron) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2005 17:56:31 -0000 On Thursday 27 October 2005 05:39 pm, Mathieu Prevot wrote: > Le 21 oct. 05 =E0 19:43, Nate Lawson a =E9crit : > > John Baldwin wrote: > >> On Friday 21 October 2005 02:38 am, Mathieu Prevot wrote: > >>>> I think that the generation of the OS for Amd64 needs to set this > >>>> define: > >>>> > >>>> #define ACPI_MISALIGNED_TRANSFERS > >>>> > >>>> I will look into doing this automatically in the actypes.h header > >>> > >>> To confirm, the same output on the same system but with > >>> 6.0RC1i386GENERIC: > >> > >> I think Robert's point is a patch like the following hack would > >> shut up the warnings: > >> Index: actypes.h > >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >> RCS file: /usr/cvs/src/sys/contrib/dev/acpica/actypes.h,v > >> retrieving revision 1.1.1.29 > >> diff -u -r1.1.1.29 actypes.h > >> --- actypes.h 1 Dec 2004 23:13:39 -0000 1.1.1.29 > >> +++ actypes.h 21 Oct 2005 13:52:22 -0000 > >> @@ -194,6 +194,9 @@ > >> typedef UINT64 ACPI_SIZE; > >> #define ALIGNED_ADDRESS_BOUNDARY 0x00000008 /* No > >> hardware alignment support in IA64 */ > >> +#ifdef __amd64__ > >> +#define ACPI_MISALIGNED_TRANSFERS > >> +#endif > >> #define ACPI_USE_NATIVE_DIVIDE /* Native > >> 64-bit integer support */ > >> #define ACPI_MAX_PTR ACPI_UINT64_MAX > >> #define ACPI_SIZE_MAX ACPI_UINT64_MAX > >> The problem is that currently the actypes.h header assumes that > >> the only 64-bit platform it runs on is IA-64, but it also runs on > >> amd64 and amd64 allows for unaligned accesses just like i386. > >> I'm not sure if ALIGNED_ADDRESS_BOUNDARY should be 0x4 for amd64 > >> either, probably not though. > > > > If that works, can you commit it to something off the vendor > > branch? (Perhaps acfreebsd.h or something?) > > > > -- > > Nate > > I simply added > > #define ACPI_MISALIGNED_TRANSFERS > > in /usr/src/sys/amd64/include/acpica_machdep.h so the intel actypes.h > is preserved. > Maybe it is simpler than touching the Robert's / Intel's code. Is it > right ? > If so, someone have to commit it on the CVS sources. Can you do it > before the release ? That's probably a good enough fix for 6.0 for now. HEAD can just wait for = the=20 real fix from Intel and the hack can be removed from acpica_machdep.h in 6.= x=20 after the new Intel code is backported. =2D-=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org