0 Replies Latest reply on Dec 22, 2010 4:31 PM by elemc

    kerneloops Intel DH55HC Fedora Linux 14

    elemc
      I've recently bought an Intel DH55HC motherboard with Intel Core i5 760. I've upgraded BIOS to latest (TCIBX10H.86A.0040.2010.1018.1100).
      Booted my lovely OS Fedora Linux 14 and saw this warning in dmesg:
      [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
      [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
      [    0.000000] ------------[ cut here ]------------
      [    0.000000] WARNING: at drivers/pci/dmar.c:633 warn_invalid_dmar+0x7d/0x8d()
      [    0.000000] Hardware name:        
      [    0.000000] Your BIOS is broken; DMAR reported at address fed90000 returns all ones!
      [    0.000000] BIOS vendor: Intel Corp.; Ver: TCIBX10H.86A.0040.2010.1018.1100; Product Version:        
      [    0.000000] Modules linked in:
      [    0.000000] Pid: 0, comm: swapper Not tainted 2.6.35.10-72.fc14.x86_64 #1
      [    0.000000] Call Trace:
      [    0.000000]  [<ffffffff8104d999>] warn_slowpath_common+0x85/0x9d
      [    0.000000]  [<ffffffff8102baae>] ? _paravirt_ident_64+0x9/0xe
      [    0.000000]  [<ffffffff8104da0c>] warn_slowpath_fmt_taint+0x3f/0x41
      [    0.000000]  [<ffffffff81bb7551>] ? __early_set_fixmap+0x93/0x99
      [    0.000000]  [<ffffffff8102baae>] ? _paravirt_ident_64+0x9/0xe
      [    0.000000]  [<ffffffff81245bd7>] warn_invalid_dmar+0x7d/0x8d
      [    0.000000]  [<ffffffff81bb7972>] ? early_iounmap+0xd8/0x120
      [    0.000000]  [<ffffffff81bcf2b7>] check_zero_address+0xb9/0xf9
      [    0.000000]  [<ffffffff81471c73>] ? _etext+0x0/0x1
      [    0.000000]  [<ffffffff81bcf309>] detect_intel_iommu+0x12/0x95
      [    0.000000]  [<ffffffff81ba8367>] pci_iommu_alloc+0x1c/0x28
      [    0.000000]  [<ffffffff81bb7243>] mem_init+0x19/0xec
      [    0.000000]  [<ffffffff81ba1a63>] start_kernel+0x225/0x416
      [    0.000000]  [<ffffffff81ba12c6>] x86_64_start_reservations+0xb1/0xb5
      [    0.000000]  [<ffffffff81ba13c2>] x86_64_start_kernel+0xf8/0x107
      [    0.000000] ---[ end trace a7919e7f17c0a725 ]---
      [    0.000000] Disabling lock debugging due to kernel taint

      When will you make new BIOS version correcting this warning?
      Linux kernel: 2.6.35.10-72.fc14.x86_64 , 2.6.35.9-64.fc14.x86_64

       

      P.S. I don't like a workaround: Disable VT-d direct I/O in BIOS settings.