Re: [Xen-devel] dmidecode doesn't work under xen 4.1.1 on certain hardware

[Anthony Wright <anthony@xxxxxxxxxxxxxxx>]

On 26/09/2011 15:13, Konrad Rzeszutek Wilk wrote:
> On Fri, Sep 23, 2011 at 03:49:47PM +0100, Anthony Wright wrote:
>> On 23/09/2011 14:32, Konrad Rzeszutek Wilk wrote:
>>> On Fri, Sep 23, 2011 at 12:22:04PM +0100, Anthony Wright wrote:
>>>> I have a xen 4.1.1 with a 3.0.4 linux kernel running on a Supermicro
>>>> Supermicro X8DTL-iF motherboard with 16GB of RAM.
>>>>
>>>> If I run the 3.0.4 kernel on the bare metal dmidecode works fine. If I
>>> Can you attach the beginning of the kernel bootup log? It should
>>> have some entry about 1-1 mappings. Make sure to run Linux with "debug 
>>> loglevel=8"
>> Please find attached.
>> 2011 Sep 23 14:45:41 kernel: [    0.000000] 1-1 mapping on 9a->100
>> 2011 Sep 23 14:45:41 kernel: [    0.000000] 1-1 mapping on bf780->100000
>> 2011 Sep 23 14:45:41 kernel: [    0.000000] Set 264422 page(s) to 1-1 
>> mapping.
>> 2011 Sep 23 14:45:41 kernel: [    0.000000] BIOS-provided physical RAM map:
>> 2011 Sep 23 14:45:41 kernel: [    0.000000]  Xen: 0000000000000000 - 
>> 0000000000099000 (usable)
>> 2011 Sep 23 14:45:41 kernel: [    0.000000]  Xen: 0000000000099800 - 
>> 0000000000100000 (reserved)
> .. snip..
>
> So 99C00 is right at cusp of 'usuable' and 'reserved'. Meaning that region
> falls within the 4KB page. And we did not set the 1-1 mapping for 99 (we
> started at 9A).
>
> But now that I think of it - this is Linux E820 which does get modified.
> Can you also provide  the hypervisor E820 output? You can get 'xl dmesg'
> for that. That should provide the "virgin" output of the e820 which we
> use for 1-1 mapping.
I'm not quite sure I understand all that, but I think you would find the
xl dmesg output helpful, so I've attached it.

Attachment: dmidecode-fails-xl-dmesg.log
Description: Text document

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