From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] [Xen] Check FADT's signature Date: Fri, 10 Aug 2007 14:23:26 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0998697789==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Mime-version: 1.0 Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Stefan Berger Cc: xen-devel List-Id: xen-devel@lists.xenproject.org > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============0998697789== Content-type: multipart/alternative; boundary="B_3269600607_24493114" > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3269600607_24493114 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable On 10/8/07 12:36, "Stefan Berger" wrote: > (XEN) (1) Mapped 0xf601f to ff0f601f > (XEN) Using APIC driver default > (XEN) IN acpi_parse_fadt. > (XEN) (2) Mapped 0x3ffcfec0 to fff9bec0, base =3D 0xfff9b000 > (XEN) ACPI: Invalid FADT signature A_=08_ADR This =8CA__ADR=B9 looks remarkably like the middle of another ACPI table. :-) Perhaps you could scan all physical memory in the range 3ffcd000-3ffd0000, either via /dev/mem in native Linux, or hack some code to map-and-check within Xen, or whatever, and look for that string? It=B9d be interesting to know: a) does it appear at all? b) is it at the same offset in a page as we expect the fadt signature to appear (ie., offset 0xec0)? c) is it in a page we mapped previously via __acpi_map_table()? -- Keir --B_3269600607_24493114 Content-type: text/html; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Re: [Xen-devel] [PATCH] [Xen] Check FADT's signature On 10= /8/07 12:36, "Stefan Berger" <stefanb@us.ibm.com> wrote:

(XEN) (1) Mapped 0xf601f to ff0f601f
(XEN) Using APIC driver default
(XEN) IN acpi_parse_fadt.
(XEN) (2) Mapped 0x3ffcfec0 to fff9bec0, base =3D 0xfff9b000
(XEN) ACPI: Invalid FADT signature A_=08_ADR

This ‘A__ADR’ looks remarkably like the middle of another ACPI = table. :-)

Perhaps you could scan all physical memory in the range 3ffcd000-3ffd0000, = either via /dev/mem in native Linux, or hack some code to map-and-check with= in Xen, or whatever, and look for that string? It’d be interesting to = know:
 a) does it appear at all?
 b) is it at the same offset in a page as we expect the fadt signature= to appear (ie., offset 0xec0)?
 c) is it in a page we mapped previously via __acpi_map_table()?

 -- Keir
 --B_3269600607_24493114-- --===============0998697789== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0998697789==--