* VT-d warnings on Intel DQ35JO
@ 2008-06-05 7:30 Neo Jia
2008-06-05 7:34 ` Jean Guyader
0 siblings, 1 reply; 2+ messages in thread
From: Neo Jia @ 2008-06-05 7:30 UTC (permalink / raw)
To: xen-devel; +Cc: Han, Weidong
hi,
This is what I get on the Intel DQ35JO. Is it critical?
(XEN) Brought up 2 CPUs
(XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found
(XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found
(XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found
(XEN) I/O virtualisation enabled
(XEN) I/O virtualisation for PV guests disabled
(XEN) [VT-D]iommu.c:764: iommu_page_fault: iommu->reg = ffff828bfff57000
(XEN) [VT-D]iommu.c:733: iommu_fault_status: Fault Overflow
(XEN) [VT-D]iommu.c:720: iommu_fault:DMA Write: 0:2.0 addr f00000000
REASON 5 iommu->reg = ffff828bfff57000
(XEN) print_vtd_entries: iommu = ffff83007aefb480 bdf = 0:2:0 gmfn = f00000
(XEN) root_entry = ffff83007c06e000
(XEN) root_entry[0] = 7c18b001
(XEN) context = ffff83007c18b000
(XEN) context[10] = 101_7d1dc001
(XEN) l3 = ffff83007d1dc000
(XEN) l3_index = 3c
(XEN) l3[3c] = 0
(XEN) l3[3c] not present
(XEN) *** LOADING DOMAIN 0 ***
Thanks,
Neo
--
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: VT-d warnings on Intel DQ35JO
2008-06-05 7:30 VT-d warnings on Intel DQ35JO Neo Jia
@ 2008-06-05 7:34 ` Jean Guyader
0 siblings, 0 replies; 2+ messages in thread
From: Jean Guyader @ 2008-06-05 7:34 UTC (permalink / raw)
To: Neo Jia; +Cc: xen-devel, Han, Weidong
Neo Jia wrote:
> hi,
>
> This is what I get on the Intel DQ35JO. Is it critical?
>
> (XEN) Brought up 2 CPUs
> (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found
> (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found
> (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found
> (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not found
> (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found
> (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found
> (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found
> (XEN) [VT-D]iommu.c:1708: Interrupt Remapping hardware not found
> (XEN) I/O virtualisation enabled
> (XEN) I/O virtualisation for PV guests disabled
> (XEN) [VT-D]iommu.c:764: iommu_page_fault: iommu->reg = ffff828bfff57000
> (XEN) [VT-D]iommu.c:733: iommu_fault_status: Fault Overflow
> (XEN) [VT-D]iommu.c:720: iommu_fault:DMA Write: 0:2.0 addr f00000000
> REASON 5 iommu->reg = ffff828bfff57000
> (XEN) print_vtd_entries: iommu = ffff83007aefb480 bdf = 0:2:0 gmfn = f00000
> (XEN) root_entry = ffff83007c06e000
> (XEN) root_entry[0] = 7c18b001
> (XEN) context = ffff83007c18b000
> (XEN) context[10] = 101_7d1dc001
> (XEN) l3 = ffff83007d1dc000
> (XEN) l3_index = 3c
> (XEN) l3[3c] = 0
> (XEN) l3[3c] not present
> (XEN) *** LOADING DOMAIN 0 ***
>
I had almost the same error with this same motherboard, you should
upgrade your bios.
--
Jean Guyader
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-06-05 7:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-05 7:30 VT-d warnings on Intel DQ35JO Neo Jia
2008-06-05 7:34 ` Jean Guyader
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.