2 Replies Latest reply on Oct 9, 2012 3:40 PM by Ricardo Jesus

    Possible DQ77MK ACPI bug

    Ricardo Jesus

      Hi,

       

      I'm using a DQ77MK desktop board with BIOS MKQ7710H.86A.0050.2012.0830.1022 08/30/2012 alongside an i7-3770 CPU.

       

      While loading Xen I came across the following:

      # xm dmesg | grep ACPI

      (XEN)  000000008e2d6000 - 000000008e2e6000 (ACPI data)

      (XEN)  000000008e2e6000 - 000000008e40b000 (ACPI NVS)

      (XEN)  000000008e6b0000 - 000000008e6f3000 (ACPI NVS)

      (XEN) ACPI: RSDP 000F0490, 0024 (r2  INTEL)

      (XEN) ACPI: XSDT 8E2DA080, 007C (r1 INTEL  DQ77MK         32 AMI     10013)

      (XEN) ACPI: FACP 8E2E41F0, 010C (r5 INTEL  DQ77MK         32 AMI     10013)

      (XEN) ACPI Warning (tbfadt-0232): FADT (revision 5) is longer than ACPI 2.0 version, truncating length 0x10C to 0xF4 [20070126]

      (XEN) ACPI: DSDT 8E2DA188, A061 (r2 INTEL  DQ77MK         32 INTL 20051117)

      (XEN) ACPI: FACS 8E409080, 0040

      (XEN) ACPI: APIC 8E2E4300, 0092 (r3 INTEL  DQ77MK         32 AMI     10013)

      (XEN) ACPI: FPDT 8E2E4398, 0044 (r1 INTEL  DQ77MK         32 AMI     10013)

      (XEN) ACPI: TCPA 8E2E43E0, 0032 (r2 INTEL  DQ77MK         32 MSFT  1000013)

      (XEN) ACPI: MCFG 8E2E4418, 003C (r1 INTEL  DQ77MK         32 MSFT       97)

      (XEN) ACPI: HPET 8E2E4458, 0038 (r1 INTEL  DQ77MK         32 AMI.        5)

      (XEN) ACPI: SSDT 8E2E4490, 036D (r1 INTEL  DQ77MK         32 INTL 20091112)

      (XEN) ACPI: SSDT 8E2E4800, 09AA (r1 INTEL  DQ77MK         32 INTL 20051117)

      (XEN) ACPI: SSDT 8E2E51B0, 0A92 (r1 INTEL  DQ77MK         32 INTL 20051117)

      (XEN) ACPI: DMAR 8E2E5C48, 00B8 (r1 INTEL  DQ77MK         32 INTL        1)

      (XEN) ACPI: ASF! 8E2E5D00, 00A5 (r32 INTEL  DQ77MK         32 TFSM    F4240)

      (XEN) ACPI: 32/64X FACS address mismatch in FADT - 8e409080/0000000000000000, using 32

       

      I've highlighted has seems to me a bug on the BIOS implementation of ACPI. Looking around intel.com website I couldn't find a reasonable technical support e-mail or bug reporting tool.

       

      Can someone provide a valid Intel contact to expose the bug and hopefully correct it the next BIOS version?

       

      Thanks!