<div dir="ltr"><div><div><div>ok googled a bit around and found this:<br><a href="https://communities.intel.com/thread/28389">https://communities.intel.com/thread/28389</a><br><br></div><div>another one with a P6T Board :D<br></div><div>he's using xen with a better(?) logging<br></div><div><br></div>i've checked aw's post about reserving memory and tried it, but its already reserved?<br><br>[    0.000000] e820: BIOS-provided physical RAM map:<br>[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable<br>[    0.000000] BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved<br>[    0.000000] BIOS-e820: [mem 0x00000000000e4c00-0x00000000000fffff] reserved<br>[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bf77ffff] usable<br>[    0.000000] BIOS-e820: [mem 0x00000000bf780000-0x00000000bf797fff] ACPI data<br>[    0.000000] BIOS-e820: [mem 0x00000000bf798000-0x00000000bf7dbfff] ACPI NVS<br>[    0.000000] BIOS-e820: [mem 0x00000000bf7dc000-0x00000000bfffffff] reserved<br>[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved<br>[    0.000000] BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved<br>[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000063fffffff] usable<br>[    0.000000] debug: ignoring loglevel setting.<br>[    0.000000] NX (Execute Disable) protection: active<br>[    0.000000] e820: user-defined physical RAM map:<br>[    0.000000] user: [mem 0x0000000000000000-0x000000000009d3ff] usable<br>[    0.000000] user: [mem 0x000000000009d400-0x000000000009ffff] reserved<br>[    0.000000] user: [mem 0x00000000000e4c00-0x00000000000fffff] reserved<br>[    0.000000] user: [mem 0x0000000000100000-0x00000000bf77ffff] usable<br>[    0.000000] user: [mem 0x00000000bf780000-0x00000000bf797fff] ACPI data<br>[    0.000000] user: [mem 0x00000000bf798000-0x00000000bf7dbfff] ACPI NVS<br>[    0.000000] user: [mem 0x00000000bf7dc000-0x00000000bfffffff] reserved<br>[    0.000000] user: [mem 0x00000000fee00000-0x00000000fee00fff] reserved<br>[    0.000000] user: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved<br>[    0.000000] user: [mem 0x0000000100000000-0x000000063fffffff] usable<br><br><br></div>btw i've tested if something appear in dmesg if i disable vt-d from the chipset( i thought maybe the cpu will use the built-in feature) buuuuuut no ;(<br><br></div>maybe aw have some more ideas? :)<br></div><div class="gmail_extra"><br><div class="gmail_quote">2016-09-02 20:34 GMT+02:00 Marco Stagge <span dir="ltr"><<a href="mailto:spiritblackdiamont@gmail.com" target="_blank">spiritblackdiamont@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div>Hey,<br><br></div>thanks for your answer, atm im checking my dmesg for that entry .. i've found this so far^^<br><br>[    0.000000] e820: BIOS-provided physical RAM map:<br>[    0.000000] BIOS-e820: [mem 0x0000000000000000-<wbr>0x000000000009d3ff] usable<br>[    0.000000] BIOS-e820: [mem 0x000000000009d400-<wbr>0x000000000009ffff] reserved<br>[    0.000000] BIOS-e820: [mem 0x00000000000e4c00-<wbr>0x00000000000fffff] reserved<br>[    0.000000] BIOS-e820: [mem 0x0000000000100000-<wbr>0x00000000bf77ffff] usable<br>[    0.000000] BIOS-e820: [mem 0x00000000bf780000-<wbr>0x00000000bf797fff] ACPI data<br>[    0.000000] BIOS-e820: [mem 0x00000000bf798000-<wbr>0x00000000bf7dbfff] ACPI NVS<br>[    0.000000] BIOS-e820: [mem 0x00000000bf7dc000-<wbr>0x00000000bfffffff] reserved<br>[    0.000000] BIOS-e820: [mem 0x00000000fee00000-<wbr>0x00000000fee00fff] reserved<br>[    0.000000] BIOS-e820: [mem 0x00000000ffe00000-<wbr>0x00000000ffffffff] reserved<br>[    0.000000] BIOS-e820: [mem 0x0000000100000000-<wbr>0x000000063fffffff] usable<br>[    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved<br>[    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable<br>[    0.000000] e820: last_pfn = 0x640000 max_arch_pfn = 0x400000000<br>[    0.000000] e820: update [mem 0xbf800000-0xffffffff] usable ==> reserved<br>[    0.000000] e820: last_pfn = 0xbf780 max_arch_pfn = 0x400000000<br>[    0.000000] e820: [mem 0xc0000000-0xfedfffff] available for PCI devices<br>[    0.554189] e820: reserve RAM buffer [mem 0x0009d400-0x0009ffff]<br>[    0.554190] e820: reserve RAM buffer [mem 0xbf780000-0xbfffffff]<br><br></div>the interesting part(for me) is that "available for PCI devices" mem ... so at this point all infos about pcidevices are stored in this mem area?<br><br></div>if i grep around for "mem" there is a lot infos ... hmm .... well, i'll attach my dmesg in this mail(hope thats possible)<br></div>maybe there is someone who figure some areas out, i'll test it and report back then :)<br><br></div><div>...and i found something new lol :D<br><br>ACPI: DMAR 0x00000000BF7980C0 000138 (v01 AMI    OEMDMAR  00000001 MSFT 00000097)<br><br></div><div>but, i dont know what this output should tell me?^^<br></div><div><br></div><br></div><div>hmmm maybe this could help<br><br>[    0.090460] dmar: Host address width 39<br>[    0.090509] dmar: DRHD base: 0x000000fbfff000 flags: 0x0<br>[    0.090566] dmar: IOMMU 0: reg_base_addr fbfff000 ver 1:0 cap c9008010e60262 ecap f0207a<br>[    0.090629] dmar: DRHD base: 0x000000fbffe000 flags: 0x1<br>[    0.090680] dmar: IOMMU 1: reg_base_addr fbffe000 ver 1:0 cap c90780106f0462 ecap f020fe<br>[    0.090742] dmar: RMRR base: 0x000000000ec000 end: 0x000000000effff<br>[    0.090790] dmar: RMRR base: 0x000000bf7dc000 end: 0x000000bf7dbfff<br>[    0.090838] dmar: ATSR flags: 0x0<br><br></div><div><br><br></div>btw i wonder why, the xeon(vt-d supported) is not able to override the vt-d tables from the motherboard or something like that<br><br></div>maybe its blocked by bios?<br><br><br><div><div><div><div><div><div><div><div><div><br></div></div></div></div></div></div></div></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2016-09-02 15:36 GMT+02:00 rob e <span dir="ltr"><<a href="mailto:redgerhoo@yahoo.com.au" target="_blank">redgerhoo@yahoo.com.au</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    On 31/08/16 02:00, <a href="mailto:vfio-users-request@redhat.com" target="_blank">vfio-users-request@redhat.com</a> wrote:<br>
    <blockquote type="cite">
      <pre>Date: Tue, 30 Aug 2016 11:52:18 +0200
From: Marco Stagge <a href="mailto:spiritblackdiamont@gmail.com" target="_blank"><spiritblackdiamont@gmail.com></a>
To: <a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a>
Subject: [vfio-users] Asus P6T Deluxe unofficial BIOS
Message-ID:
        <a href="mailto:CADKDhYex84ArCOctnErAK0sED0hPsCGJ5tEf3UJsz+01yLGCZQ@mail.gmail.com" target="_blank"><CADKDhYex84ArCOctnErAK0sED0hP<wbr>sCGJ5tEf3UJsz+01yLGCZQ@mail.gm<wbr>ail.com></a>
Content-Type: text/plain; charset="utf-8"

Hey there,

i've got two Boards, Asus P6T Deluxe and non-Deluxe Version. Ive running a
Xeon X5650 on it, but
VT-d is routed through bios(dmesg told me), and the DMAR-Table is broken.
On the xen page i've found this "ASUS P6T Deluxe (Intel X58 chipset)
requires (currently non-public) BIOS update to correct DMAR-table issue".

Does anyone know if there is a unofficial bios with corrected DMAR-Table?
google is not my friend^^
didnt find anything useful :(

greet Spirit

</pre>
    </blockquote>
    I have the same motherboard and also sought that bios, without
    success. There is however someone else who may have tried it<br>
    <a href="https://bbs.archlinux.org/viewtopic.php?pid=1487138#p1487138" target="_blank">https://bbs.archlinux.org/view<wbr>topic.php?pid=1487138#p1487138</a><br>
    See Alex's response suggesting use of <br>
    <pre><code>        memmap=nn[KMG]$ss[KMG]
                        [KNL,ACPI] Mark specific memory as reserved.
                        Region of memory to be reserved is from ss to ss+nn.
                        Example: Exclude memory from 0x18690000-0x1869ffff
                                 memmap=64K$0x18690000
                                 or
                                 memmap=0x10000$0x18690000</code></pre>
    I haven't tried this myself so would be interested in your feedback
    :)<br>
  </div>

</blockquote></div><br></div>
</div></div></blockquote></div><br></div>