Re: [Xen-devel] Bad FADT and timer going backwards

[Stefan Berger <stefanb@xxxxxxxxxx>]

xen-devel-bounces@xxxxxxxxxxxxxxxxxxx wrote on 08/09/2007
09:05:21 AM:

> 
> Hello! 
> 
>   I am encountering a problem with one of the machines I am using
> and the timer going backwards. It looks like the problem is due to
> to a bad PM-Timer entry being found. Though when debugging further,
> the real source of the problem stems from an ACPI table of type DSDT
> being parsed as an FADT during boot and certainly a bogus PM-Timer
> is found there. 
> 
> Here's the output from 'xm dmesg' with an additional signature check
> of the alleged FADT, which now prevents it from picking the bogus
> PM-Timer port. I am also dumping how the addresses of the tables are
> being mapped. Linux does find the correct PM-Timer port, though (0x2208).
> 
> (XEN) ACPI table at 0xfdfc0 mapped to address ff0fdfc0
> (XEN) ACPI: RSDP (v000 IBM            
                     
) @ 0x000fdfc0
> (XEN) ACPI table at 0x3ffcff80 mapped to address fff9bf80
> (XEN) ACPI table at 0x3ffcff80 mapped to address fff9bf80
> (XEN) ACPI: RSDT (v001 IBM    SERBLADE 0x00001000 IBM  0x45444f43)
@0x3ffcff80
> (XEN) ACPI table at 0x3ffcfec0 mapped to address fff9bec0
> (XEN) ACPI table at 0x3ffcfec0 mapped to address fff9bec0
> (XEN) ACPI: FADT (v002 IBM    SERBLADE 0x00001000 IBM  0x45444f43)
@0x3ffcfec0
> (XEN) ACPI table at 0x3ffcfe00 mapped to address fff9be00
> (XEN) ACPI table at 0x3ffcfe00 mapped to address fff9be00
> (XEN) ACPI: MADT (v001 IBM    SERBLADE 0x00001000 IBM  0x45444f43)
@0x3ffcfe00


> (XEN) ACPI table at 0x3ffcfec0 mapped to address
fff9bec0
> (XEN) ACPI table at 0x3ffcdec0 mapped to address fff9bec0

Is it 'ok' that these two different phys. addresses
get mapped to the same virtual address?

   Stefan
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel